Cookie Notice
1. What these technologies are
Cookies are small values stored by a website. Local storage and session storage are similar browser technologies. Authentication providers may also use tokens to keep a user signed in and protect a session. “Cookies” below includes these technologies unless a distinction matters.
2. Current categories
| Category | Purpose | Consent position |
|---|---|---|
| Strictly necessary | Authentication, account security, session continuity, language and requested privacy settings. | Used where necessary to provide a requested service; no advertising use. |
| Local prototype/archive state | Stores draft answers, demo configuration, selected persona/age and other data locally in this browser. | Clearly disclosed in the interface; users can clear it through product/browser controls. |
| Preferences | Remembers optional display, language or accessibility choices. | Consent or user request as applicable. |
| Analytics | Not currently intended. Future audience measurement must be listed here before activation. | Prior consent where required; respect withdrawal and browser signals where law applies. |
| Advertising/social tracking | Not currently used. | Will not be introduced without updated notice and legally required opt-in/opt-out controls. |
3. Required production inventory
Before launch, publish the exact name, provider, domain, purpose, data collected and duration of every cookie, local-storage key, SDK and pixel. The inventory must include the authentication/database provider, content delivery network, hosting, payment service, embedded media, support tools and any analytics.
The current prototype includes local keys for application state and the Demo Studio, and can receive authentication storage from Supabase. Some pages currently load third-party code or fonts; production should self-host where practical or document the resulting requests and transfers.
4. Your controls
You can clear website data through browser settings. Doing so may sign you out and delete locally stored, unsynchronised prototype material. A production consent control must allow people to refuse or later withdraw non-essential technologies as easily as accepting them; refusal must not block core service unless the technology is genuinely necessary.
Where applicable, we will honour legally recognised opt-out signals such as Global Privacy Control for sale/sharing. Do Not Track has no uniform legal meaning; our final production response will be stated here.
5. Contact
Questions or consent withdrawal requests: [PRIVACY EMAIL / COOKIE SETTINGS LINK].