Privacy and data controls for 1for49 players

1for49 uses a split privacy model: on-chain gameplay is public, off-chain service data is controlled, and reveal helper data stays device-local by default.

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

We never collect wallet secrets

Seed phrases and private keys are never requested or stored by 1for49.

On-chain game activity is public

Wallet addresses and round transactions are visible on Solana explorers.

Reveal secrets stay device-local

Commit/reveal helper secrets are stored in browser Dexie on your device.

You control local cleanup

Local browser data can be cleared anytime; this does not alter finalized chain data.

Three-layer model

Where your data lives and who can see it

This table separates public chain data, service data, and device-local data.

Layer	Typical data	Who can see it	Retention	Delete control
On-chain public ledger	Wallet address, round entry tx, reveal tx, claim tx, game account state.	Anyone (public blockchain).	Permanent under blockchain finality.	Not deletable by 1for49 or support.
Off-chain service data	Support messages, diagnostics, app telemetry, session metadata.	1for49 operations + contracted processors.	Target periods apply by category (see retention table below).	Eligible requests can be handled through support.
Device-local browser data	Commit/reveal helper secrets, round ticket cache, UI preferences.	Your current browser/device profile.	Until cleared by user or browser cleanup.	Clear in browser controls or in-game local-data tools when available.

Game action mapping

What each action exposes

Place Picks, Reveal Picks, and Claim Reward have different privacy surfaces.

Place Picks

On-chain (public)

Commit transaction metadata.
Entry account updates for your wallet and round.

Device / service (limited visibility)

Local draft inputs and optional helper cache.
Support diagnostics if you submit a support request.

Picks are committed on-chain first; plaintext reveal details are not exposed at commit time.

Reveal Picks

On-chain (public)

Reveal transaction metadata.
Revealed values used for settlement and winner logic.

Device / service (limited visibility)

Device-local secret retrieval from Dexie/local storage.
Optional local round history cache for UX speed.

If local reveal helper data is lost before reveal, recovery may not be possible.

Claim Reward

On-chain (public)

Claim transaction metadata.
Claim status updates and token transfer records.

Device / service (limited visibility)

Tx intent/status cache for continuity across refresh/reopen.
Operational logs for reliability and abuse defense.

Claim eligibility is enforced by on-chain state; off-chain UI does not override final chain outcomes.

Local data controls

Device-only storage and cleanup

Reveal helper data is local-first. Keep backup habits if you rely on device-local reveal helpers.

Use game-page local data tools when available for export/import/purge workflows.
Browser storage clear removes local cache and local reveal helpers.
Clearing local reveal helpers before reveal can make a pending reveal impossible.

Important: clearing local secrets does not reverse any finalized chain transaction.

Quick actions

Privacy help and controls

Use these paths to manage local data and submit privacy requests.

Open Game Console Cookie controls Privacy support contact@currinfo.com

Processors

Third-party service categories

We disclose processor categories and purpose so data handling is inspectable.

RPC and chain infrastructure

Broadcast and read Solana transactions/accounts.

Data: Public wallet addresses, tx signatures, account lookups.

Wallet adapter integrations

Connect wallet providers and sign user-approved actions.

Data: Wallet public key and user-approved signing payloads.

Telemetry and diagnostics

Performance monitoring, reliability, and incident response.

Data: Operational logs, non-secret client diagnostics, request metadata.

Support delivery

Resolve user requests and privacy inquiries.

Data: Submitted support content and contact details you provide.

Retention periods

Target retention by data class

These are target periods; legal or security obligations can require longer retention.

Operational telemetry logs

Target: up to 30 days

May be extended for active incident investigation.

Security and abuse records

Target: up to 180 days

May be retained longer when required by law or enforcement actions.

Support tickets and contact records

Target: up to 24 months

Used for request continuity, compliance, and audit traceability.

Device-local reveal/helper data

Until user clears local storage

Removing it can make unrevealed entries unrecoverable.

On-chain records

Permanent

Immutable ledger data is outside app-side deletion controls.

Rights and security

Requests, identity checks, and protections

Request access, correction, or deletion of eligible off-chain data through support.
Clear browser storage to remove local app preferences and local helper artifacts.
Use hardware wallets and review every signature request before approving.
Privacy requests may require wallet/address ownership verification.

Policy change log

What changed in this policy

Version 3.0

2026-03-21

Added explicit 3-layer data model (on-chain, off-chain, and device-local).
Added action-by-action privacy mapping for Place Picks, Reveal Picks, and Claim Reward.
Added explicit retention target periods and processor categories.

Version 2.0

2026-03-11

Refocused policy language to 1for49 game workflow and Solana finality.