Cookies & Local Storage
CREW ATLAS currently uses only storage needed for accounts and the collector features you choose. We do not use advertising cookies, marketing pixels or cross-site tracking.
Last updated: 2 August 2026
1. What these technologies are
Cookies are small values stored by a browser and sent with relevant web requests. Local storage keeps data inside the browser without sending it automatically with each request. Similar technologies are subject to transparency and, in some jurisdictions, consent rules.
2. Strictly necessary authentication cookies
Supabase Auth sets first-party session values when you create an account, sign in, confirm an email, reset a password or refresh a session. Their exact names can vary by project and may be split into several cookie values.
| Provider | Purpose | Duration |
|---|---|---|
| Supabase Auth | Keep you signed in, securely refresh the session and protect authenticated MY ATLAS pages. | Session-based or until the authentication token expires, refreshes or you sign out. |
These values are necessary for the account service you request. Blocking them prevents sign-in and cloud synchronisation, although public routes and some device-only features may still work.
3. CREW ATLAS local storage
The following versioned keys may be stored on your device:
| Key | What it does |
|---|---|
| crew-atlas:v1:profile | Caches your Passport and collector-profile preferences on this device. |
| crew-atlas:v1:cardStates | Caches printing-level Have, Want and Watch choices. |
| crew-atlas:v1:syncMetadata | Prevents the wrong browser cache from being merged into an account and records successful sync times. |
| crew-atlas:v1:pendingDeletes | Keeps an account-bound record of card-state removals that still need to reach the cloud, preventing deleted markings from returning after an offline session. |
| crew-atlas:v1:digestSignups | Obsolete preview-only Digest entry. The current version removes this local value and never treats it as email consent. |
| crew-atlas:v1:analytics | Legacy device-side test log. The current version does not write this key and removes an existing log during normal use. |
Older crewlist: keys may be read once for migration and then removed. Local data remains until you clear browser site data or CREW ATLAS replaces it during normal use.
Browser data is device-specific. During a completed account-deletion process, session and site-data cleanup happens in your browser on the confirming device, not on the deletion server. CREW ATLAS cannot clear another browser or device remotely, so you must clear CREW ATLAS site data separately on every device you used.
4. Privacy-focused Web Analytics
CREW ATLAS uses Vercel Web Analytics for aggregated traffic statistics. According to Vercel, Web Analytics does not use cookies and does not associate page views with an identified person or IP address. A request-derived hash supports a temporary visitor session and is discarded after 24 hours.
Data points may include timestamp, page path, dynamic route, referrer, filtered query parameters, approximate geolocation, device type, operating system and browser version. We do not send your email, display name, card states or collector profile as custom analytics properties.
5. Why there is no consent banner
At present, CREW ATLAS does not activate non-essential cookie-based analytics, advertising or cross-site tracking. Authentication storage is necessary for signed-in features, and collector local storage implements choices expressly requested by the user. Vercel Web Analytics is cookieless.
Based on this current technical setup, we provide this notice without displaying a consent banner that has no optional categories to manage. If non-essential technologies are added, CREW ATLAS will introduce the required consent controls before activating them where the law requires it.
6. Your controls
- Sign out to end the active account session.
- Clear cookies and site data in your browser to remove local CREW ATLAS storage.
- Use the management link in a Digest email to change character preferences or unsubscribe. Digest consent is stored server-side, not in a browser cookie.
- Use browser privacy settings or extensions to limit storage and requests.
- Remember that clearing site data can remove unsynced Passport and card-state information stored only on that device.
For more detail on personal-data handling, see the Privacy Policy.