REALLY BAKED GAME PRIVACY POLICY

This policy describes the data used by the Really Baked Galaga game and optional competition enrollment.

DATA COLLECTED DURING PLAY

• TOKER TAG (4–8 characters), stored locally and with submitted leaderboard scores.
• Device UUID, generated on first visit and used for sessions, score submissions, and rate limiting.
• Score, wave reached, Wave 25 completion flag, submission timestamp, and competition prize-eligibility metadata.
• Session tokens and rate-limit records used to operate and protect the leaderboard.

OPTIONAL COMPETITION ENROLLMENT

Competition registration collects your email address and TOKER TAG only when you choose to enroll. Your email is stored locally as rb_player_email and in the competition registration database. Verification status is stored server-side. After verification, the raw registration email is cleared from the registration record and a one-way hash is retained for deduplication.

Email is used for verification, competition administration, and contacting potential winners. It is never displayed publicly. Competition registration and verification do not constitute consent to marketing or promotional communications. Optional marketing consent is separate, unchecked by default, and used only when you explicitly select it.

LOCAL DEVICE DATA

Sound preference, best score, age confirmation, last-run data, cached leaderboard results, pending score submissions, TOKER TAG, device UUID, competition email, and verification state may be stored in your browser's localStorage.

DATA NOT COLLECTED DURING NORMAL PLAY

• Email address, unless you optionally enroll in the competition.
• Full name or mailing/shipping address; these are reserved for a separately implemented potential-winner claim flow.
• Date of birth; the age gate stores only your affirmation.
• IP address in application records (Cloudflare processes network data in transit under its own policy).
• Device model, OS version, browser type, or geolocation.

CONTACT

support@reallybaked.us