Cookie and storage policy

Browser storage controls for 1for49 players

This page explains what local browser artifacts are used, why they exist, what breaks if removed, and how one-entry lottery flow can be affected if reveal-helper data is lost.

Effective date: 2026-03-21Version: 3.0Privacy policy Terms

No ad-tech tracking cookies

1for49 does not use third-party behavioral advertising cookies or cross-site ad profiling cookies.

On-chain records are separate

Browser storage controls only affect local app state. Finalized chain entries and claims remain public on Solana.

Reveal helpers stay local

Commit/reveal helper secrets are stored in IndexedDB (Dexie) on your current browser profile.

You can clear data anytime

You control local storage, session storage, and IndexedDB cleanup from browser settings or in-app local tools.

Storage inventory

Exact browser keys and databases used by the app

Inventory is implementation-aligned and may evolve with migrations.

Key / store	Type	Purpose	Retention	If removed
detrustpay.solana.cluster	localStorage	Remember selected Solana cluster.	Until changed or cleared.	Cluster resets to environment/default; explorer links and reads may point to another cluster.
detrustpay.settings	localStorage	Store UI preferences (time format, language, display behavior).	Until changed or cleared.	UI settings return to defaults.
auth_tokens / auth_token (legacy)	localStorage	Store app auth/session token for protected support surfaces when used.	Until sign-out, overwrite, token expiry, or clear.	You are signed out from those off-chain protected surfaces.
onefor49:home:focus_game_id	sessionStorage	Persist selected game focus in homepage terminal during tab session.	Tab/session lifetime.	Homepage focus resets after reload/new session.
onefor49 (IndexedDB) / roundTickets	IndexedDB (Dexie)	Store local ticket summary by wallet/game/round for fast UX continuity.	Until user clears local DB.	You lose local view history cache, but chain truth remains available.
onefor49 (IndexedDB) / commitSecrets	IndexedDB (Dexie)	Store local reveal helper materials needed for Reveal Picks.	Until reveal, purge, or local DB clear.	Pending reveal may become impossible if secret is removed before reveal period ends.
onefor49 (IndexedDB) / txIntents + queryCache	IndexedDB (Dexie)	Persist tx status continuity and local-first cached snapshots.	Until replaced/expired by app flow or DB clear.	No loss of on-chain data, but pending-action continuity and instant UI state degrade.
onefor49-commit-secrets / secrets (legacy)	IndexedDB (legacy)	Compatibility store; rows migrate lazily into scoped onefor49 DB.	Until migrated or cleared.	Older unrevealed rows may not auto-migrate if removed before first read.

If disabled

What can break when storage is blocked or cleared

Keep this in mind before cleaning site data during active rounds.

Blocking all local storage

Cluster selection, preferences, and local continuity features cannot persist between reloads.

Clearing local secrets before Reveal

You can lose the ability to reveal pending picks for that round and may forfeit reward eligibility.

Clearing IndexedDB transaction history

Pending/confirmed tx intents no longer appear in local queue after refresh; chain data remains verifiable.

One-entry warning

Loss of local reveal data can permanently block rewards

One-entry mode has strict periods. Browser cleanup during active rounds can create irreversible outcomes.

One wallet has one active entry path per game/round.
If you place picks and local reveal helper data is lost before reveal, reward path can be permanently lost.
Clearing storage does not undo committed transactions and does not reopen missed stage periods.

Browser actions

Manage cookies and storage per browser

Use browser-native controls to inspect or clear local data.

Chrome / Edge

Open Site settings -> Cookies and site data.
Choose allow/block behavior for this site.
Use Storage -> Clear data to remove localStorage, sessionStorage, and IndexedDB.

Clear data removes local reveal helpers and ticket cache for this browser profile.

Firefox

Open Page Info -> Permissions or Settings -> Privacy & Security.
Manage cookies/site data for the current site.
Clear offline website data to remove IndexedDB/local storage artifacts.

Blocking storage can prevent local continuity and reveal helper retrieval.

Safari

Open Safari Settings -> Privacy -> Manage Website Data.
Search for this site and remove selected data.
Use cross-site tracking and cookie controls as desired.

Site data removal signs out off-chain sessions and clears local workflow state.

Retention periods

How long local artifacts can remain

Browser retention differs from immutable on-chain record retention.

sessionStorage focus key

Current tab/session only

Automatically cleared when tab/session closes.

localStorage preferences and cluster

Until user clears or key is replaced

Used for UX continuity, not on-chain finality.

Dexie onefor49 local DB

Until user purge/clear

Contains local-first game cache, tx intents, and reveal helper material.

Legacy IndexedDB compatibility stores

Temporary during migration paths

Legacy rows may be read and migrated into current scoped DB.

On-chain round records

Permanent blockchain retention

Not affected by cookie or browser data removal.

Consent and boundaries

Storage usage model for lottery gameplay

The app uses strictly necessary and functional storage classes to provide gameplay continuity.

Core gameplay requires strictly necessary browser storage for safe app operation and local continuity.
Functional storage helps preserve UI settings and game focus state between views.
1for49 does not use storage for third-party behavioral advertising profiles.
If optional analytics or diagnostics behavior changes, policy and legal pages will be updated first.

Policy changelog

What changed in this cookie policy

Version history is aligned with legal-page updates.

Version 3.0Effective 2026-03-21

Added concrete browser storage inventory with real keys and Dexie stores.
Added one-entry reveal-loss warning and disable/clear impact matrix.
Added browser-specific cleanup guidance and retention period table.

Version 2.0Effective 2026-03-11

Refocused cookie policy language to 1for49 game lifecycle and storage boundaries.