Cookies & device storage

Sign-in storage in use

• Supabase authentication cookies (project-specific sb-… names, sometimes split into numbered chunks) keep the signed-in session available to the server and browser. Authentication links can also use a temporary code-verifier cookie.
• ss_remember contains only the keep-signed-in choice, never a password or authentication token. When enabled, the preference cookie is configured for up to 400 days; when disabled it is session-only.
• With Keep me signed in off, application session cookies omit persistent expiry. Browser session-restore behaviour can vary, so use Log out on a shared device rather than relying only on closing a tab.
• Authentication token/session lifetimes are managed by the Supabase SDK and project configuration. Their precise inventory and provider settings require a release-time cookie audit; no universal login lifetime is promised.

Optional tracking and consent

The current application includes no optional analytics, advertising pixels or third-party advertising scripts, and has no marketing opt-in. It does not display a pretend Accept all banner for trackers that are not installed.

Essential sign-in storage supports the service you request. Future optional storage, marketing or advertising must be assessed separately and obtain consent where required before activation. Refusing future optional tracking must not be treated as refusal of the legal terms.

Managing your device

Choose your sign-in preference on the login screen. Log out through Profile or Account settings to end the app session on this device. You can clear site cookies in your browser; doing so can sign you out and remove remembered preferences. Browser settings may prevent sign-in from working if essential storage is blocked.

Provider infrastructure and deployment-specific tools need a further cookie/log audit before public launch. Cookie details, purposes and applicable retention must be updated if integrations change.