EFFECTIVE AUGUST 23, 2026

Privacy policy

Blind Exit can be played without an account. Signed-out game progress and personal statistics stay in local storage on the device.

Data we process

• Account data. Username, password hash, account identifier, session records, and account creation time. We never store the plaintext password.
• Game data. Daily scores, round scores, prediction coordinates, completion times, leaderboard rank, streak, and group memberships.
• Purchase data. Entitlement status and transaction identifiers from Stripe, Apple, Google Play, or RevenueCat. Payment providers process card and store-payment details; Blind Exit does not receive full card numbers.
• Visit data. A random first-party cookie lets us count daily visitors and page views. The server stores only a keyed hash that changes each day, plus first- and last-seen times and a view count. Blind Exit does not use this identifier for cross-site tracking.
• Security data. Short-lived, keyed hashes derived from an IP address and username for login and registration rate limits. Raw IP addresses are not stored in the application database by this mechanism, though infrastructure providers may keep access logs.

Why we process it

We use this data to authenticate accounts, preserve one daily score, calculate daily and weekly rankings, operate private groups, grant purchased access, prevent abuse, and diagnose failures. We do not sell personal data, run behavioral advertising, or use game predictions to build advertising profiles.

Service providers

Vercel hosts the web application and API. Supabase provides PostgreSQL and social sign-in. Stripe processes web payments. Apple and Google process native purchases, with RevenueCat synchronizing native entitlements. Each provider processes data under its own terms and privacy policy.

Retention and deletion

Account, leaderboard, group, and purchase records remain while the account is active or while they are needed for transaction, fraud, tax, dispute, and legal records. Pseudonymous visit rows are retained for up to 400 days. Expired sessions and rate-limit records may be deleted automatically. A deletion request removes the account and associated game and group-membership records, except records that must be retained by law or to resolve a payment dispute.

Security and transfers

Sessions use random tokens, passwords use scrypt hashes, production traffic requires HTTPS, and the production database uses encrypted storage and TLS connections. No security method eliminates all risk. Providers may process data in countries other than the user’s country, subject to their transfer safeguards and applicable law.

Your choices and rights

You can play signed out, avoid joining groups, sign out to revoke the active device session, and request account access or deletion. Privacy rights vary by location and may include access, correction, deletion, portability, restriction, or objection.

Children

Blind Exit is not directed to children under 13, or the higher minimum age required for independent consent where the user lives. Do not create an account if local law requires parental consent and that consent has not been provided.

Contact

For a privacy request, use the developer contact shown on the App Store, Google Play, or website distribution page from which Blind Exit was obtained. The publisher may verify account ownership before acting on a request.