Last updated: 2026-06-01
decksity uses cookies and similar browser storage entries required to keep users signed in, protect portal and live-session access, and remember interface preferences.
Some cookies are set directly by decksity, while authentication cookies may be set by Supabase, the authentication provider used by the application.
| Cookie | Type | Purpose | Retention |
|---|---|---|---|
| theme | Preferences | Stores the selected light or dark theme. | 1 year |
| decksity-locale | Preferences | Stores the selected application language. | 1 year |
| sb-<project-ref>-auth-token* | Authentication | Maintains the authenticated session for a signed-in user and allows token refresh. | Until sign-out or Supabase session expiry. |
| sb-<project-ref>-auth-token-code-verifier | Authentication | Temporary PKCE verifier used during magic-link sign-in flows. | Short-lived; removed after sign-in completes or the flow expires. |
| decksity.live | Security | Authorises guest access to an active live session for a specific DJ. | 24 hours |
| portal_session_<short_code> | Security | Maintains access to a client portal or contract flow for a specific short code. | 14 days |
| portal_fp | Security | Stores a random identifier used to protect the portal access flow and limit abuse. | 30 days |
decksity does not enable optional analytics or marketing cookies in the code currently shipped in this repository.
Necessary authentication and security cookies are required for sign-in, portal access, and live-session protection. Blocking them may prevent key parts of the service from working correctly.
Preference cookies can be cleared in the browser at any time. Clearing them resets theme, language, and interface preferences.
This policy is updated when the list of cookies, providers, or product behaviour changes.