1. Essential browser storage

These items are used to make Nixie Studio work:

• Authentication storage managed by Supabase so signed-in sessions can be resumed.
• nixie:user-settings:v1 for editor preferences, shortcuts, persisted tool options, and shell layout state such as open sidebar sections and their order.
• IndexedDB project persistence managed by the Nixie editor and Yjs so in-progress project state can be recovered locally before or between syncs.
• nixie:last-opened-project:v1 for recent-project shortcuts and re-entry flows.
• nixie:last-opened-hub-page:v1 for returning to the last used launcher page (such as Projects, Workspaces, or Settings).
• nixie:clipboard:v1 for clipboard payload fallback when browser clipboard access is limited.
• nixie:assets-browser:search-history:v1 for recent searches in the asset browser.
• nixie:assets-browser:directory:v1:<project-id> for restoring the last opened asset browser folder per project.

2. Analytics

Nixie Studio does not currently use optional third-party analytics cookies on these routes.

First-party activation measurement uses nixie:activation:anonymous-id:v1, nixie:activation:attribution:v1, and nixie:activation:exposure-recorded:v1 to count an initial Studio exposure once and preserve its acquisition source through sign-in. It records a small set of product milestones in Supabase, but does not record project content or general click activity. Where local law requires prior consent, these analytics items are not created until you choose Allow Analytics.

The essential nixie_analytics_consent_v1 cookie remembers the analytics mode or your explicit choice. You can turn analytics off at any time under Settings → Account → Privacy. Turning analytics off removes the three analytics storage items above from that browser and stops new activation events.

If third-party analytics is introduced in the future, this page and the Privacy Policy will be updated before that tracking is enabled.

3. How to clear stored data

You can clear browser storage directly through your browser settings if you want to remove locally stored items from your device. Doing so may sign you out and remove unsaved local preferences, cached editor state, or locally recovered project content.

4. More details

Some browser-local storage is essential to authentication, offline recovery, editor continuity, and collaboration quality. Removing it may reset parts of your local experience without deleting server-side account or project data.