1. Our cookie position
IDpurge currently intends to use only strictly necessary cookies or equivalent technologies needed for authentication, session continuity, security and reliable delivery of the service.
IDpurge does not currently use advertising cookies, behavioural tracking, social-media tracking pixels or analytics cookies. We will not introduce non-essential tracking silently.
2. Strictly necessary technologies
| Category / name pattern | Purpose | Provider | Lifetime / consent |
|---|---|---|---|
| Authentication/session: sb-<project-ref>-auth-token, which may be split into numbered parts | Keep you securely signed in and maintain the authenticated session you requested. | Supabase | The installed library defaults to a maximum of 400 days from a cookie being written; it may be refreshed or removed earlier. This does not mean your session stays valid for 400 days. Strictly necessary. |
| Temporary verification: sb-<project-ref>-auth-token-code-verifier, where created | Complete a secure email authentication exchange. | Supabase | Removed during completion/cleanup of the relevant exchange; otherwise subject to cookie expiry. Strictly necessary. |
| Security/service delivery | Protect the service, route requests and provide essential infrastructure where a provider requires such technology. | Hosting/security infrastructure | Strictly necessary where genuinely essential |
The entries above describe the authentication code prepared for this beta. The production cookie inventory and effective expiry settings must be verified before public launch and after changes to authentication or hosting. A cookie's storage lifetime is separate from server-enforced session validity.
3. Why there is no marketing-cookie banner
The current service does not intentionally set non-essential cookies. Strictly necessary cookies can be used without opt-in consent where they are genuinely required to provide the service a user requested. IDpurge still explains them here for transparency.
If analytics, advertising, conversion tracking, social pixels or other non-essential storage or access technologies are added later, they must remain disabled until the required clear information and consent controls are in place.
4. Browser controls
You can configure your browser to block or delete cookies. Blocking cookies that are necessary for authentication may prevent login or cause parts of IDpurge to stop working.
5. Future changes
Cookie use must be re-audited before public launch and whenever a new analytics, advertising, support, payment or embedded third-party service is introduced. The default is to avoid non-essential tracking unless there is a clear business need and a compliant implementation.