Privacy Notice

Who runs SnakeBit

SnakeBit operates the game and is responsible for deciding how the player data described here is used. Privacy questions and requests can be sent to ramymoussally@gmail.com.

Data the game handles

• Device and essential site data: browser session credentials, consent choices, onboarding progress, control and audio settings, theme choices, local best scores, cached career information, and pending submissions. Most of this stays in browser storage until it is cleared.
• Player identity: a random account identifier, arcade initials, a four-character public player code, an optional public display name, and—only if a player chooses Save Player or Restore Player—an email address and verification records.
• Gameplay and competition: scores, mode, theme, control method, run statistics, Daily Run attempts and input replays used to verify results, Live VS room membership and verified results, career totals, rival records, and optional Podium Watch preferences and alerts.
• Technical operations: IP address, browser/device details, request times, and error or security information may be processed in ordinary hosting, authentication, and network logs.
• Optional product analytics: only after explicit opt-in, SnakeBit may send page visits and coarse game events to Google Analytics 4, including mode, control method, theme, broad score/duration bands, and broad error categories. Google also receives normal device and network information and may set analytics cookies.

Why data is used

SnakeBit uses essential data to provide and secure the game, restore a player when requested, synchronize preferences and career statistics, operate public leaderboards and Daily/VS competition, verify results, prevent duplicate or abusive submissions, deliver opted-in Podium Watch alerts, diagnose failures, and protect the service.

Optional analytics is used only to understand traffic, onboarding, mode popularity, run completion, VS funnel performance, broad engagement patterns, and technical failures so the game can be improved. It is not used for advertising or ad personalization.

The legal grounds are providing the game features a player requests, SnakeBit's legitimate interests in operating a safe and reliable competitive service, compliance with legal obligations where applicable, and consent for Google Analytics. Consent can be refused or withdrawn without losing access to the game.

What other players can see

Leaderboard and player-card surfaces may publicly show arcade initials, player code, optional display name, scores, rank, selected theme/control category, Daily results, and related public competition statistics. Email addresses and internal account identifiers are not public. Live VS opponents receive the identity and match information needed to run the room.

Arcade Announcer

The Arcade Announcer uses reusable message templates generated in batches with Google's Gemini service. Gemini does not receive an individual player's identity, email, or career history. SnakeBit selects a template and inserts that player's statistics inside the browser; Supabase records limited message-impression history to reduce repetition.

Service providers and transfers

SnakeBit uses Supabase for authentication, database, realtime, and server functions; Contabo-hosted infrastructure to serve the game; and Google Analytics only for opted-in analytics. Google Cloud and Gemini are used to generate general announcer templates, not to profile individual players. These providers process data under their own security and data-processing terms and may process it outside the player's country. Where required, contractual and other lawful transfer safeguards are used.

SnakeBit does not sell personal data. Data may also be disclosed when required by law or when reasonably necessary to protect players, the service, or legal rights.

How long data is kept

• Browser data remains until the player clears site data, changes a setting, or the game replaces an obsolete value.
• Player identity, career, leaderboard, Daily, and verified VS records are generally kept while the service operates or until a valid deletion request is completed, because they preserve player history and competitive integrity.
• After account deletion, public competitive records may be retained without the account link—including score and the public arcade identity shown when the result was earned—where needed to preserve fair historical standings.
• Temporary room, pending-event, and operational records are removed or expired when no longer needed. Security records may be kept longer when required to investigate abuse or comply with law.
• Before product analytics is enabled, GA4 user-level and event-level retention will be set to two months with reset-on-new-activity disabled. Standard aggregated GA4 reports may remain available longer.

Player choices and rights

Analytics is off by default. It can be enabled or disabled at any time under Player & Info → Player → Share anonymous play analytics. Disabling it stops future collection and removes accessible SnakeBit GA cookies from that browser; it does not automatically erase earlier aggregate reporting.

Depending on local law, a player may ask for access, correction, deletion, restriction, objection, or a portable copy of personal data, and may withdraw consent. Send the request to ramymoussally@gmail.com with enough information to locate and verify the player account. A player may also complain to their local data-protection authority.

Children

SnakeBit is not directed to children under 13, and SnakeBit does not knowingly request personal information from them. A parent or guardian who believes a child has provided personal information should contact SnakeBit so it can be reviewed and deleted where appropriate.

Notice changes

This notice may be updated when the game or its data practices change. Material changes will be dated here and, when appropriate, announced in the game. A changed contact email will be reflected on this page.