1. What these technologies are
A cookie is a small value a website stores on your device and may receive back with later requests. Local storage stays in your browser until it is cleared. Session storage normally lasts only for the current browser tab. This notice covers all three, because the distinction matters less than what the thing actually does.
Strictly necessary technologies are used to provide a service you have asked for, to secure it, or to remember a privacy choice you made. They do not require consent. Functional storage remembers a preference and improves your experience. Anything non-essential requires your consent before it is set.
Voxa sets no advertising cookies and loads no third-party analytics in the current release. Everything below is first-party and stays on your device unless the table says otherwise.
2. Full inventory
| Name | Type and duration | What it does | Category |
|---|---|---|---|
| voxa_session | First-party HttpOnly cookie; 7 days | Authenticates your signed-in session. Set with SameSite=Lax, and Secure over HTTPS. | Strictly necessary |
| voxa:cookie-choice | Local storage; until cleared | Records whether you chose Essential only or Allow analytics, so the banner respects your decision. | Strictly necessary |
| voxa:theme | Local storage; until cleared | Remembers your light or dark theme on this device. | Functional |
| voxa:view | Local storage; until cleared | Returns you to the workspace view you last selected. | Functional |
| voxa:support-assistant-seen:<account> | Local storage; until cleared | Avoids repeating the support assistant introduction for the same account on this device. | Functional |
| voxa:ai-task-creation:v1 | Local storage; removed once the drafts are saved to your workspace | Holds AI task drafts you created before they were saved to your account, so a refresh does not lose your work. | Strictly necessary |
| voxa:survey-builder:v1 | Local storage; removed once the drafts are saved to your workspace | Holds survey drafts you created before they were saved to your account. | Strictly necessary |
| voxa:participant-studies:<account> | Session storage; current tab | Temporarily preserves the loaded study list while you navigate. | Strictly necessary |
| voxa:draft-targeting | Session storage; current tab, removed on save | Preserves unsaved audience rules in the study builder. | Strictly necessary |
| voxa:project-study-context | Session storage; current tab, removed on save | Carries unsaved project context into the study builder. | Strictly necessary |
| voxa:ai-task-study-context | Session storage; current tab, removed on save | Carries a selected AI task into the study builder. | Strictly necessary |
| voxa:survey-study-context | Session storage; current tab, removed on save | Carries a selected survey into the study builder. | Strictly necessary |
3. Optional analytics
The cookie banner lets you express an analytics preference, but the current release loads no analytics provider and sets no analytics cookie. Choosing Allow analytics therefore records permission only: it does not start any tracking.
Before we connect an analytics provider we will add it to the inventory above with its cookie names, purposes and durations, complete the assessment the law requires, and make sure it loads only after a valid consent where consent is required.
4. Managing your choices
Use Manage cookie preferences at the bottom of any page to reopen the choice at any time. You can also clear site data from your browser settings.
Blocking or deleting the session cookie signs you out. Blocking strictly necessary storage may stop parts of the service working, including the study builder's protection against losing unsaved work. Clearing theme and workspace preferences does not affect your account.
Browser controls differ by product; check your browser's privacy or site-data settings. Where the law makes a universal opt-out signal such as Global Privacy Control binding on us, we honour it. See our Regional privacy addenda.
5. Changes and contact
We update this notice whenever the storage we use changes. It is written to be checkable: every entry above corresponds to something the application actually sets.