Transparency centre · Zodiac beta
Cookies and device storage
Necessary storage, saved content and optional statistics you can refuse.
Contents14 sections
1. What storage means in Zodiac
This page covers cookies, localStorage, IndexedDB and Service Worker caching. A technology may store or access device information even when it is not called a cookie. The inventory describes inspected code and does not prove that infrastructure cannot introduce cookies under other conditions. No advertising or third-party analytics SDKs were identified in the inspected version. AI/voice service requests are separate data flows described in Privacy.
2. Storage inventory
localStorage “zodiac.guest.v1”: selected profile, access credentials and reading cache, until sign-out/clearing or deletion through the application. “zodiac.language.v1”: Romanian/English, until changed or browser clearing. “zodiac.appearance.v1” and “zodiac.appearance-config.v1”: theme, animation and interface configuration, until changed/cleared. “zodiac.privacy.v1”: statistics choice, version and expiry associated with local identity, without a password or access token in this record. “zodiac.playback-preference.v1”: playback speed and account-preference synchronisation. “zodiac.morning-seen.v1:<profile>”: last greeting-display date to avoid repeating the pop-up. sessionStorage “zodiac.astral-refresh.v1” and “zodiac.astral-human-request.v1”: idempotency keys and links to the current request, until workflow/session clearing. IndexedDB “zodiac.private-content.v1”: saved readings/audio (maximum 180 readings and approximately 50 MB audio per profile); “zodiac.astral-cache.v1”: continuity catalog/replies with a 60-result limit. There is no general TTL for all these data; they are managed through content features and browser clearing. Service Worker “zodiac-shell-*” cache: public application files updated by version; authenticated API requests are excluded. This is not a general deletion deadline for all copies. sessionStorage “zodiac.privacy.pending.v1.<account>” or “zodiac.privacy.pending.v1.anonymous” retains an unconfirmed choice, version and attempt reference so that refusal remains respected if local saving fails and the tab reloads. It is removed following a successful explicit save for the same identity or browser-session closing/clearing; it is not a traffic analytics identifier.
3. Necessary functions and preferences
Storage for authentication, security, requested settings and saved content supports the features you use. The statistics choice is retained to honour refusal or acceptance. Refusing statistics does not automatically delete these data or block the application. The banner is not a justification for all processing. Before publication, each mechanism’s qualification for strictly necessary exceptions must be validated against its actual purpose and the current version of Romanian Law 506/2004, Article 4(5)-(6).
4. Optional statistics
If you accept, the application records active visits, opened sections, morning-message display and listening starts/progress/completions. Events are linked to the account/profile and administrators may see aggregates; they are not described as anonymous. This flow does not record your microphone or voice. Browser code and the server stop recording without a valid choice. Statistics are not enabled merely because you browse or accept terms. Administrators may still see records required for operation, such as questions and costs, which have different purposes.
5. Choosing and withdrawing
The banner offers refusal and acceptance with equal accessibility, and settings allow later changes. Refusal is the default and does not limit readings or playback. The technical choice expires after 180 days or when the statistics notice version changes. Existing account choices sync with the server; a refusal from another device is not automatically replaced by stale local acceptance. If saving or networking fails, statistics stay off on the device. An unsynced refusal must be retried online to apply on other devices. Withdrawal stops future events and does not automatically delete retained history; you can separately request its deletion.
6. Clearing, PWA and shared devices
You can use profile export/deletion and browser settings for local data. Clearing only the browser does not delete the server account and may remove guest access. Uninstalling the PWA icon may leave browser data. Exported files or audio downloaded outside the application remain under your control. On a shared device, avoid saving credentials/private materials and sign out after use. Contact the operator if you need deletion beyond local controls.
7. Administration and infrastructure
A technical administration area has a “__Host-remote-dev” session mechanism with HttpOnly, Secure, SameSite=Strict attributes and a cookie lifetime of up to 8 hours. This module’s interface is currently hidden; ordinary user browsing does not activate it. Cookie duration does not establish automatic erasure of all server session records. Additional infrastructure cookies or metadata depend on actual configuration and need separate verification.
8. Checks before publication
To confirm: cookies introduced by actual Cloudflare configuration across all flows, justification for necessary storage and consent-record duration. The 180/90-day periods are provisional technical choices requiring approval. New trackers must be inventoried, explained and blocked before appropriate consent; this document does not authorise their installation.
9. Sound and campaign-statistics storage
The localStorage preference “zodiac.sound.v1” retains your click-chime/music choices until changed or browser clearing. Both initially stay off; sound starts only after your action. The click chime and fallback ambience are generated locally; approved tracks are original files served by this site, described in section 10. Separately, only after statistics acceptance, sessionStorage “zodiac.traffic.anonymous.v1” holds a consent token expiring within 24 hours; after offline withdrawal it may remain solely to sync refusal when online. “zodiac.traffic.session.v1” identifies the tab for visit grouping, and “zodiac.traffic.campaign.v1” holds a campaign key expiring within 24 hours. These optional records are not created before a choice and are cleared on withdrawal except for temporary refusal reconciliation; they may disappear when the browser session closes. Authenticated visits also require server-verified account consent. The single Cookies and preferences panel offers Accept all, Necessary only and statistics settings; sound preferences remain separate controls at the top of the application. Using the application does not imply consent.
10. Invitation links and music selection
Only after statistics consent, sessionStorage “zodiac.traffic.referral.v1” may retain a valid invitation key for up to 24 hours to report visits. Refusal/withdrawal clears this optional attribution. A key in the URL does not accept an account association; that choice is separate at signup. localStorage “zodiac.music.selection.v1” stores selected track identifiers only, as a requested local preference. Three original instrumental tracks were generated through ElevenLabs and are served as files from this site after administrator approval. Their playback sends no listener information to ElevenLabs. The click chime and fallback ambience are generated locally. Music is initially off, starts through a user gesture and can be stopped in the top bar. The selection is not an analytics identifier.
11. Source category in the browser session
Only after current statistics consent, sessionStorage “zodiac.traffic.source.v1” retains the source category and expiry for up to 24 hours. It does not retain the referring address, hostname, search terms or browsing history. Closing the browser session or clearing storage may remove it earlier. Refusal, consent withdrawal and identity reset clear this optional preference. The application remains usable when storage is unavailable. The opaque “zodiac.traffic.anonymous.v1” consent proof described in section 9 may be sent during creation of a new primary profile only while current and statistics are accepted; the server checks version, expiry and single use. It is not an account password and does not automatically accept a referral. No new source-category key is created before a choice or after refusal. Existing consent to an older version must be renewed for this expanded statistics scope. On loading a new page, a new external referrer replaces the previous category, and missing referrer information is marked unavailable. Only an explicit continuation from the same site may retain the prior category and remaining expiry. Repeated calls within the same page do not extend that deadline.
12. Entry measurement only after consent
The beta screen uses functional state to avoid unnecessary repeated display; this is not statistics consent. Before current consent, no entry identifier, technical snapshot or statistics queue is created. After consent, this screen’s events and identifiers stay in a bounded page-memory queue for at most 30 minutes and no more than 6 delivery attempts. No new persistent key stores this report’s queue. Retries reuse identifiers to avoid duplicate counting. Closing/reloading the page loses the queue; withdrawal or identity change clears it and delivery is not guaranteed. Existing anonymous consent proof and session keys are created only in the consented flow described above. After current consent, the property-name inventory and added screen/connection fields use the same queue and retention limits; they are not inspected before consent or after refusal/withdrawal. An older choice must be renewed for the new details in version 2026-10-11.5. The banner offers acceptance, refusal and settings inside the entry screen too; Continue stays separate and does not enable collection.
13. Session details and network service
Version 2026-10-11.5 requires a new choice before additional details or sending an IP to ipapi.is. Without current consent, these snapshots are not collected and the provider is not called. At the first valid observation of the loaded page a snapshot may include inner/outer window dimensions and position, scroll, visualViewport, document visibility/loading state and dimensions, display mode, pointer/hover/theme/motion preferences and reported timezone. Nonstandard fields such as cpuClass or connection estimates are included only where exposed; they do not reliably identify a phone or processor. We do not read page text, request high-entropy hints or arbitrarily enumerate all API values. No ipapi.is tracking cookies or provider script are added to your browser. Communication is server-to-server. The keyed cache lasts at most 7 days and observation metadata at most 90 days. Administrator report preferences are protected operational server configuration, not new visitor tracking data. Refusal or withdrawal keeps core application features available.
14. Server evidence and local presentation
The limited server HTTP security evidence described in Privacy does not use cookies or JavaScript APIs for identification and does not depend on optional statistics choice. It is not used for campaigns or conversions. Refusing cookies still stops usage analytics, browser snapshots and ipapi.is calls. For interface presentation, zodiac-ui-familiarity-v1 locally keeps a counter capped at 3 uses, the main profile and last-use time; its sole purpose is showing a discreet invitation after familiarity with the app. It expires after 90 days, is removed on logout and is never sent to the server. The in-memory response cache is isolated by account, profile, language, context and day; revalidation creates no new analytics without consent.
Have a question?
For questions about the application or your data, write to us.
Sources and checks
Sources and checks
Sources explain the reviewed framework; they do not certify project settings or contracts. The legal framework was consulted on 8 October 2026; MDN technical sources on browser referrers on 10 October 2026. Romanian legal consolidation, applicability and final approval must be rechecked. Cloudflare/MDN metadata sources, GDPR Articles 5 and 7 and EDPB Guidelines 05/2020 on consent were also rechecked on 10 October 2026. Availability in this project account is separate from provider documentation. The ipapi.is API documentation, privacy policy and public DPA were consulted on 10 October 2026; provider statements and the account contract are distinct evidence.
- Company identity / Identitatea firmei
- GDPR — ANSPDCP (Arts. 5–9, 12–22, 25, 28, 30, 32–35, 44–49)
- EDPB — Data subject rights / Drepturi
- European Commission — Information for individuals
- Legea 506/2004, art. 4 — forma actuală de reverificat / recheck current version
- AI Act — Article 50 (applicability review required)
- OpenRouter — provider logging
- ElevenLabs — privacy
- Cloudflare — customer DPA
- MDN — browser referrer availability / Proveniența disponibilă în browser
- Cloudflare — trusted request metadata
- Cloudflare — conditional bot-management signals
- MDN — Screen colorDepth/pixelDepth
- MDN — basic userAgentData availability
- GDPR — EUR-Lex, Articles 5 and 7
- EDPB — Guidelines 05/2020 on consent
- MDN — Referrer-Policy
- ipapi.is — API documentation
- ipapi.is — Data Processing Agreement / Germany endpoint
- ipapi.is — Privacy policy (provider statements)