Cookie Policy
Cookies, browser storage, analytics, referrals, and sign-in technologies used by GetRender.
Cookies, browser storage, analytics, referrals, and sign-in technologies used by GetRender.
Last updated: October 2, 2026
GetRender uses cookies and other browser technologies to operate accounts, remember certain settings, preserve form drafts, measure service usage, and help prevent abuse. Cookies are small records stored by a browser. Local storage, session storage, and IndexedDB can hold identifiers, preferences, or draft files without being cookies. Device fingerprinting can derive an identifier from browser and device characteristics.
This policy complements our Privacy Policy. Merely visiting the site or reading this policy does not mean you have agreed to optional tracking. The legal requirements for consent depend on the technology, purpose, and applicable law; describing a technology here does not exempt it from those requirements.
| Category | Examples and purpose | Duration or lifecycle |
|---|---|---|
| Authentication | Session and authentication cookies maintain sign-in and protect account flows. | A normal account session is configured for up to 7 days and may renew during use; short-lived verification and session-cache records have shorter lifetimes. |
| Security and abuse prevention | A registration/sign-in device fingerprint and the registration_fingerprint cookie help identify duplicate-account and promotional-credit abuse. | The cookie is configured for up to 7 days; related browser session storage normally lasts for the tab session. Server-side security records have a separate retention lifecycle. |
| Time-zone preferences | timezone supports local dates; auth_timezone passes time-zone context during sign-in. | Up to 1 year and 30 minutes respectively; they may be refreshed by use. |
| Visits and referrals | visitor_attribution_id, referral_code, and local identifiers such as __visitor_id associate visits, referral links, and campaign sources with later activity. | These cookies are configured for up to 30 days; local storage persists until cleared or replaced. Signing out can rotate a visitor identifier. |
| Analytics and diagnostics | When configured, PostHog processes page views, product events, errors, and browser identifiers to understand usage and reliability. Visits may be linked to an account after sign-in. | SDK cookies and local storage follow the active provider configuration and may persist across visits. |
| Form drafts | IndexedDB may preserve unfinished form values and selected files so sign-in does not discard them. | Drafts have a 24-hour application expiry; removal occurs when cleanup runs or when the draft is cleared. Closing a tab alone may not delete them. |
These are application settings, not a promise that every browser or third-party service uses exactly the same cookie names or expiry. Browser restrictions, renewed sessions, configuration changes, and provider behavior can affect storage. A browser-side expiry does not by itself delete associated server records.
Cloudflare may use security technologies when protecting the site. If you choose Google sign-in, a payment provider, or another third-party service, that provider may set or read its own cookies and process information under its own policy. Available integrations differ by feature and payment method.
We record referral and campaign information, including advertising click identifiers when supplied in a visit URL. This is not a statement that every visit loads an advertising, retargeting, or social-media pixel. The Privacy Policy explains recipients and how visit information may be associated with an account.
Use your browser's privacy settings to inspect, delete, or restrict cookies and site data. Local storage and IndexedDB may need to be cleared separately. Deleting stored drafts can remove unsent work and selected files; download or save anything you need first. Blocking necessary sign-in or security storage may prevent some features from working.
You can also manage Google and payment-provider permissions through those services. Browser cookie blocking does not necessarily stop all network requests, server logging, or device identification. The current website does not provide a dedicated on-site cookie preference center; contact us with questions or to exercise applicable privacy rights. Any consent mechanism required by applicable law is a separate requirement and cannot be replaced by this notice.
We will update this policy as the technologies or their purposes change. For questions, contact support@getrender.ai or our contact page. For requests concerning personal data rather than only browser storage, see the rights and contact sections of our Privacy Policy.