Cookies, all of them listed.
Every cookie and browser-storage item the platform uses, why it exists, and how to remove it.
Last updated: September 2026
1. Cookies and local storage
In shortSmall pieces of data your browser keeps so the platform can remember you. We use as few as the product allows.
Cookies are small text files a website asks your browser to store; local storage is a similar mechanism that keeps data in your browser rather than sending it with every request. Both exist so that a stateful product — staying signed in, resuming an unfinished exam — can work. This page lists every one we use, honestly and completely.
2. What we actually set
In shortSign-in state, resume flags for unfinished sittings, and experiment assignments. No advertising trackers — none, by design.
| Item | Kind | Why it exists | Lifespan |
|---|---|---|---|
Supabase auth token (sb-*) | Cookie / local storage | Keeps you signed in securely. | Until you sign out or clear it |
| Auth fallback record | Local storage | Restores your session if the primary auth check is unavailable. | Until you sign out or clear it |
| Attempt drafts and resume flags | Local storage | Lets an abandoned sitting be restored instead of lost. | Until the attempt is submitted or cleared |
| Experiment assignment | Local storage | Keeps you in the same A/B variant across visits, so the product does not flicker between experiences. | Until cleared |
| Analytics | — | Product events go to a first-party endpoint when configured. We set no advertising or cross-site tracking cookies. | — |
3. Third parties and tracking
In shortThe processors listed in our Privacy Policy do their work server-side. Your browser is not the product.
Speech-to-text, evaluation, and audio-generation calls happen from our servers, so no third-party cookies or scripts are placed in your browser for them. If we ever add an analytics tool that sets cookies, it will be added to the table above first — that is what this page is for.
4. Managing or deleting them
In shortYou control all of it: sign out, clear site data in your browser, or delete your account — each removes exactly what it should.
- Sign out removes the auth token and fallback record.
- Clear site data in your browser removes everything in the table — you will just need to sign in again, and unfinished drafts will be gone.
- Delete your account (Account page, automated) removes the server-side data these helpers point to — recordings, reports, and history.
5. Changes
In shortThis table is kept current. New storage items appear here before they ship.
When our use of cookies or local storage changes, this page is updated with a new date at the top. Questions can go to contact@svanai.com.