Cookie Policy
1. Scope
This Cookie Policy explains how Liberty Bells (the "Service") uses local browser storage and similar technologies. It supplements our Terms of Service and Privacy Policy.
2. What We Use
The Service uses the following browser storage mechanisms:
2.1 localStorage (essential)
We use the browser's built-in localStorage facility to persist your gameplay state and preferences across sessions. The keys we set are prefixed with ll- (for "Liberty Bells") and currently include the following:
ll-profile— your callsign and selected avatarll-cubes,ll-wins,ll-battles— gameplay totalsll-deck— your current twelve-card deck compositionll-unlocked,ll-new-unlocks— your unlocked card collection and unseen-unlock indicatorsll-cards-played,ll-masteries— per-card play counts and mastery progressionll-campaign-level,ll-campaign-done,ll-campaign-best— campaign progressll-daily-ch,ll-streak-days,ll-streak-last— daily challenge and play streak datall-puzzle-solved,ll-puzzle-streak,ll-puzzles-at-unlock— daily puzzle progressll-wins-at-unlock— counter for card-unlock progressionll-muted— your audio preferencell-onboarded— whether you have completed first-time tutorialsll-daily-collapsed— UI preference for the daily challenges panelll-cookies— your acknowledgement of this Cookie Policyll-terms— your acceptance of our Terms of Servicell-geo— cached country code from geographic enforcementll-auth-mode— whether you chose wallet or guest playll-token— your session token (JWT), if you connect a walletll-wallet— the public address of the wallet you connected
These items are all considered strictly necessary for the Service to function and to comply with our Terms of Service. The Service cannot operate without them.
2.1a Wallet sessions & server sync
If you choose to connect a Solana wallet, your session token and public wallet address are stored locally (above), and your game progression is sent to and stored on the Liberty Studios game server (see the Privacy Policy). If you play as a guest instead, no data leaves your browser. Connecting a wallet is optional.
2.2 sessionStorage
Ephemeral data used during a single browser session (such as in-flight gameplay state) may be stored in sessionStorage and is automatically cleared when you close the tab.
2.3 HTTP cookies
The Service itself does not set any HTTP cookies. Our hosting and DDoS-protection providers may set their own technical cookies for connection routing, security, and abuse mitigation; these are operational in nature and do not track behavior.
3. What We Do NOT Use
- No third-party advertising cookies. The Service does not display advertising.
- No cross-site tracking. We do not embed pixels, beacons, or scripts from advertising networks or data brokers.
- No behavioral profiling. We do not build profiles of your interests, browsing history, or off-Service activity.
4. Managing Your Local Data
Because the items we store are strictly necessary, the Service cannot operate without them. If you do not want this data on your device, please discontinue use of the Service.
You may clear all data at any time using one of the following:
- The in-game Settings (⚙) → RESET ALL PROGRESS control, which deletes every
ll-key the Service has set; - Your browser's standard "clear site data" controls, which delete all local storage for this origin.
5. Acknowledgement
On your first visit, a small banner displays to acknowledge that the Service uses local storage. Dismissing the banner records a single ll-cookies flag so it does not reappear on subsequent visits. Dismissing the banner is not your "consent" to any tracking — we don't track. It is merely your acknowledgement that you understand we save gameplay state in your browser.
6. Changes
If we add a new local-storage key, we will update this Policy. Material additions will be communicated through the in-game interface at least seven (7) days prior to taking effect.
7. Contact
Inquiries about this Cookie Policy should be sent through the official channels described in Section 23 of the Terms of Service.