Privacy Policy

3.1 Account and authentication

The Game uses Supabase Auth. You can play anonymously (a random account ID, no e-mail), register with e-mail and password, or sign in with Google or Apple. If you upgrade a guest account, the e-mail address is attached to your existing account ID so your progress is preserved.

Data: account ID, e-mail address (registered accounts only), password hash, OAuth provider identity (Google/Apple account reference), session tokens, sign-in timestamps.

Legal basis: Art. 6(1)(b) GDPR (performance of the contract — providing your account and saved progress). Retention: until account deletion.

3.2 Game progress and gameplay data

All game state is stored server-side: collected snakes, breeding history, resources (DNA, energy), game sessions (score, duration, DNA earned), achievements, streaks, mastery, records, battle pass and season progress, and economy transactions.

Legal basis: Art. 6(1)(b) GDPR. Retention: until account deletion.

3.3 Public profile, leaderboards and Chronicle

Your public identity in the Game is a self-chosen handle (or an automatically derived placeholder such as "handler-1234"). Leaderboards and your public Chronicle page show your handle, scores, clan tag, titles, badges, avatar and mastery — never your e-mail address or account ID. Handle changes are recorded in an internal audit log.

Legal basis: Art. 6(1)(b) GDPR (leaderboards and public profiles are a core feature of the Game). If you prefer not to be recognisable, choose a handle that does not identify you, or keep the generated placeholder.

3.4 Clans

Clan names, tags and descriptions are user-generated content visible to other players, together with the member list (handles) and clan activity (duels, research, ratings).

Legal basis: Art. 6(1)(b) GDPR. Retention: until deletion.

3.5 Discord integration (optional)

If you actively link your Discord account, we receive your Discord user ID and username via Discord OAuth (scopes: identify, guilds.join, role_connections.write), can add you to our Discord server and assign roles, and push your in-game handle and mastery as "Linked Roles" metadata. Clans can connect a Discord channel; in that case in-game events (duel results, level-ups, member joins, season champions) are posted there with your handle and clan name. OAuth tokens are stored encrypted (AES-256-GCM) and are deleted — and revoked at Discord — when you unlink; stale links are purged after 30 days.

Legal basis: Art. 6(1)(a) GDPR (consent, given by linking). You can withdraw it at any time by unlinking. Discord Inc. is an independent controller for its own platform — see Discord's privacy policy.

3.6 Analytics (PostHog) — only with your consent

If (and only if) you enable the "Analytics" category in the cookie banner, we use PostHog, hosted in the EU (eu.i.posthog.com), to understand how the Game is used. We use a curated event set (page views, gameplay, economy, purchases, engagement and social events) with autocapture and session recording disabled. Its device ID, analytics session, and person properties remain in page memory only and disappear when the page closes; browser storage retains only your analytics opt-in or opt-out choice. After sign-in, transmitted events are linked to your account ID. Revoking consent stops all capture.

Legal basis: Art. 6(1)(a) GDPR and §165(3) TKG 2021 (consent). Manage it any time via Settings → Privacy.

3.6a Attribution (where you came from) — only with your consent

If (and only if) you enable the "Marketing" category in the cookie banner, we record which channel brought you to the Game: the campaign labels contained in the link you followed (utm_source, utm_medium, utm_campaign, utm_content, utm_term) and the host name of the referring site — never the full referring address. It is stored in your browser's session storage for the current tab only and attached, as a channel label, to your analytics profile if you later create an account. We operate no advertising network, buy no advertising, and place no third-party advertising tags or advertising identifiers. With the category off, nothing is stored and your visit is counted as "direct".

Legal basis: Art. 6(1)(a) GDPR and §165(3) TKG 2021 (consent).

3.7 Error tracking (Sentry)

To keep the Game stable we send error reports (stack traces, affected route, browser/OS context) to Sentry. Transmission of personal data is disabled by default (no IP addresses attached) and we do not use session replay.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in detecting and fixing errors).

3.8 AI features (“The Analyst”)

The Analyst generates short narrative summaries of your game performance. The input sent to our AI provider (OpenAI) is a fact sheet of aggregate game statistics only — runs, DNA, extraction rate, League mastery. No handle, e-mail address, account ID or free-text content is transmitted. Generated insights are cached in our database and visible only to you (or your clan, for clan insights). The Analyst involves no automated decision-making with legal or similarly significant effects (Art. 22 GDPR).

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in providing game features); the underlying gameplay data is processed under Art. 6(1)(b).

3.9 E-mail

Transactional e-mail (verification, password reset) is sent via our e-mail provider Resend. The weekly "Analyst digest" (your game stats and narration) is strictly opt-in in Settings and can be disabled there at any time.

The "Dispatch" is a separate opt-in list for occasional product news and the results of the weekly hunt. It uses double opt-in: we store your address with a "pending" status and send exactly one confirmation e-mail. If you do not click the link in it, the address is never used for anything else and never receives another message. We store the address, its status, the timestamps, and a coarse channel label (see 3.6a); we never store the confirmation or unsubscribe token itself, only a hash of it. Every Dispatch message carries a one-click unsubscribe link, and the list is never used for advertising.

Legal basis: Art. 6(1)(b) GDPR for transactional mail; Art. 6(1)(a) (consent) for the digest and the Dispatch. Retention: until you unsubscribe. An entry that is never confirmed stays permanently unusable — it can never receive a Dispatch message — and any address can be erased on request via the contact address above.

3.10 Purchases (Stripe)

Purchases are processed by Stripe via Stripe Checkout. Stripe collects your e-mail, billing and payment card details directly — this data never reaches our servers. We store only the Stripe session and payment-intent IDs, the product, price and purchase status, linked to your account.

Legal basis: Art. 6(1)(b) GDPR (contract) and Art. 6(1)(c) (statutory retention duties). Retention: purchase records are kept for 7 years in line with Austrian tax law (§132 BAO), in anonymized form if you delete your account.

3.11 Contact form and support

If you contact us, we process the details you provide (name if given, e-mail address, category, message) to handle your request, including privacy inquiries and content reports.

Legal basis: Art. 6(1)(b) GDPR (contractual/pre-contractual communication) or Art. 6(1)(f) (responding to inquiries); Art. 6(1)(c) where handling the request is legally required. Retention: 24 months after resolution, longer where a legal obligation or dispute requires it.

3.12 Age verification

At registration we ask for your birth year and month to enforce our minimum age of 14. We do not store either value — only a salted hash and the verification result, which expires after 7 days.

Legal basis: Art. 6(1)(c) GDPR in conjunction with Art. 8 GDPR and §4(4) DSG.