Cookie policy

1. Cookies and browser storage

Cookies are small values stored by your browser and sent with matching requests. Local storage stays in a browser profile until removed or overwritten; session storage is scoped to a tab session. Browser settings, private browsing and session restoration can affect how long these values remain.

2. Essential cookies and requested preferences

These keep sign-in secure, remember requested settings and support the interface. Rejecting optional cookies does not remove them.

• better-auth.session_token: keeps you signed in for up to 365 days; activity can renew expiry once a day. A session-only sign-in does not set this persistent lifetime. Production auth cookies may have a __Secure- prefix.
• better-auth.state: checks the sign-in redirect for security; expires after 5 minutes.
• better-auth.last_used_login_method: remembers your last sign-in method for 30 days. This preference may also be stored in your account.
• locale: remembers your chosen interface language for 365 days.
• theme (local storage): remembers your appearance preference, with no automatic expiry.
• auth-storage and auth:just-logged-in (session storage): support account state and sign-in feedback within a tab; the feedback marker is removed when used.
• dubbe_surface_tg: a session cookie marking the Telegram webview so the interface and payment navigation behave correctly; contains no account identifier.
• The interface also stores operational preferences, such as dismissed notification prompts and billing notices, project-list display hints and pending Telegram account-link state. Persistent local values have no automatic browser expiry; tab-scoped values use session storage.

3. Optional analytics and recordings

With your permission, PostHog collects page and product events and can associate them with your signed-in account. Web analytics can include heatmaps and session recordings; session recording is disabled in the Telegram webview. Sentry can collect browser error reports, performance traces and replay data. Browser collection by both providers is controlled by your optional choice. This does not switch off backend operational logging needed to run and protect the service.

PostHog uses ph_PROJECT_KEY_posthog cookies and browser storage for analytics identifiers and state; PROJECT_KEY represents the analytics project key. Its cookie lifetime is up to 180 days and can be renewed; local storage has no automatic browser expiry, but our consent controls remove optional analytics identifiers on rejection or consent expiry. Other SDK session and replay state can be temporary. Browser-storage lifetimes do not determine how long providers retain data already received.

4. What Accept and Reject do

Accept optional cookies enables optional browser analytics and recordings. Reject optional cookies keeps them off and removes optional analytics identifiers managed by our consent controls, without removing essential sign-in or requested preferences. Without a valid saved choice, optional browser collection stays off. If saving your choice fails, optional collection stays off.

Your choice is stored in local storage as dubbe:cookie-consent:v1, containing accepted or rejected and an expiry time. It expires after 180 days. It is not a consent cookie, and it applies to this browser profile rather than every device or account.

5. Change or withdraw your choice

Use Cookie settings on this page or in the footer to reopen the controls. Opening settings does not change an existing choice. Select Reject optional cookies to withdraw permission for future optional browser collection, or Accept optional cookies to enable it. Withdrawal does not delete data already sent; contact us about data requests.

6. Browser controls and deletion

You can block or delete cookies in your browser and clear site data, including local and session storage. Deleting cookies alone may leave local storage, including your consent choice, intact. Clearing site data can sign you out, reset language or appearance preferences and remove your saved choice. Essential-cookie blocking can prevent sign-in. Settings and deletion in one browser do not change another browser or device.

7. Third-party services

Analytics sent through our own domain is forwarded to PostHog; a first-party URL does not mean there is no external recipient. Sentry receives optional browser diagnostics. Google sign-in, Telegram and payment services Payme and Click may apply their own cookies or storage when you use their services; our controls do not manage storage on their domains. The provider names link to their policies. See our privacy policy for broader processing information.

8. Policy updates and contact

We update this page when these practices change and revise the date above. For questions about storage, consent or personal data, email [email protected]. Our privacy policy explains broader personal-data processing.