Cookie and Browser Storage Policy

1. Your choices

Essential only declines optional presence analytics. Allow analytics enables it. You can reopen the choices below without creating an account. Core authentication, security, payment, consent records and preferences or drafts needed for features you request do not depend on analytics consent.

The consent cookie is shared across Blury subdomains for one year; local storage is separate for each origin. Withdrawal stops the current page’s analytics and removes its presence identifiers. Reload other open Blury pages after changing your choice so they re-read the shared cookie; clear site data on each Blury origin to remove previously stored local copies. Changing analytics consent does not erase already received server records, which follow the privacy retention policy.

2. Essential and requested-function storage

• Sign-in: better-auth.session_token (normally prefixed __Secure- on HTTPS) keeps a host session, normally up to seven days with renewal during use. better-auth.session_data is a session cache with a five-minute lifetime. A session-only better-auth.dont_remember preference can affect persistence. Credential cookies are host-only.
• Security and sign-in steps: Better Auth state, verification and two_factor cookies complete authentication. A pending two-factor cookie normally lasts ten minutes; a requested trusted-device cookie can last up to 30 days. Other one-time sign-in cookies expire with their short-lived flow. The __Host-blury.session-scope cookie accompanies host-session scoping.
• Navigation hint: __Secure-blury.signed_in, shared across Blury subdomains, normally lasts up to seven days. It changes signed-in navigation and is not an authentication credential.
• Requested draft handoff: __Secure-blury.pendingHandoff and __Host-blury.pendingDraftToken help carry a prompt into the product securely, with a one-hour lifetime. They are set for that requested flow.
• Consent: blury.analytics-consent stores “granted” or “denied” for one year across Blury subdomains. Clearing it causes the site to ask again; it does not mean consent was granted.
• Appearance: blury.theme.shared remembers your selected appearance across subdomains for one year; blury.theme in local storage is a browser fallback. The default follows your system theme. Local preferences remain until replaced or cleared.
• Workspace continuity: account-specific Blury local-storage entries cache chats, documents, activity results, Style, Memory-related settings, profile, selected tools, usage display, pending requests and interface preferences. Some can contain full writing and account identifiers. Most have no browser-enforced expiry and persist until replaced, removed by the app or cleared by you. They are not all removed just because a session ends.
• Deletion status: session storage can hold a deletion-status credential so a signed-out tab can follow its requested erasure job. Treat it as private; clear the tab’s site data when no longer needed.

Cookie names may have secure prefixes or numbered chunks and may change with security-library updates. Server-side expiry or revocation can end access before a cookie disappears. Blocking essential storage can break sign-in, purchases or recovery of unsaved work.