Privacy Policy

Last updated: 20 July 2026

This explains what personal data SnakeForTwo collects, why, and what you can do about it. We have tried to describe the service plainly and specifically.

Who is responsible

SnakeForTwo is operated by a sole trader based in the United Kingdom, who is the data controller for your personal data. The controller's full name and address are in the Contact section at the end of this policy.

We have not appointed a Data Protection Officer. Privacy questions go to the address in Contact and are answered by us.

The short version

• You can play without an account. We do not ask a guest for a name or email address, but the network still processes technical data such as an IP address.
• We use only essential cookies and browser storage. There are no advertising cookies or third-party tracking pixels.
• We have no advertising or audience analytics. Technical service telemetry is used only to operate, secure, and diagnose the game.
• We do not receive or store your full card number or security code. Stripe processes payment on our behalf when SuperSnake sales are available.
• You can ask us to delete your account at any time. An in-game self-service control will be available before public release.

What we collect

If you play as a guest

You do not need to give us your name, email address, or create an account. The service creates random room, player, and match identifiers so it can run the game, resume a disconnected seat, and save a completed result. These identifiers are not connected to an account.

For a completed match we store the match time, room and match identifiers, mode, result, duration, board size, player count, score, food counters, final snake state, and random player identifiers. The normal guest name is "guest". If a guest supplies another display name, that name is stored with the result and may qualify for the public leaderboard.

Like every internet service, Cloudflare, our server, and the network between them receive your IP address while carrying the connection. It is needed to route the connection and may be processed for security and abuse prevention. We do not copy it into account or match records. It may appear in short-lived infrastructure logs or technical telemetry as described below.

If you sign in with Google

Google tells us your email address, display name, profile-picture link, and a stable Google account identifier. We store:

When you play while signed in

We store the same match information described above, linked to your account, and a snapshot of your username. We also keep personal-best records for daily, monthly, and all-time leaderboards.

If you choose a custom username and qualify for the leaderboard, your username, rank, and score are public. The public leaderboard does not expose account ids, temporary player ids, room ids, or full match records. Full match-history endpoints are restricted to an allow-listed administrator account.

Other players in your room can see your in-game name, colour, ready/connection state, and the shared game state needed to play together.

When SuperSnake purchases are available

We are the seller of record, and Stripe processes the payment on our behalf. We do not receive or store your full card number or security code. Stripe may make limited payment-method information, such as card brand and the last four digits, visible to us.

Stripe sends us transaction events. We store:

• The amount, currency, tax information, and payment status
• Stripe identifiers for the payment, checkout session, and customer
• Which SnakeForTwo account the purchase belongs to
• The complete parsed JSON event payload

The parsed payload is kept so we can investigate a payment and rebuild derived payment or entitlement records. It can contain the buyer's name and email, purchase and tax details, and Stripe identifiers. It is not a byte-for-byte copy: PostgreSQL normalises JSON formatting when storing it.

Automatically, when you use the site

Our application produces security, error, performance, and game-operation logs, metrics, and traces. Depending on the layer that produced them, these may include an IP address, browser or request information, an account or connection id, the API operation used, and game lifecycle events. We do not use this information to advertise to you, build an advertising profile, or measure an audience for marketing.

Cookies and browser storage

After Google sign-in we set one persistent authentication cookie, currently with a 30-day sliding expiry. ASP.NET also uses a short-lived correlation cookie while the browser completes the Google sign-in redirect. Both are essential to the sign-in service and are marked secure and HTTP-only in production.

The game also uses localStorage or sessionStorage to keep a private room-seat reclaim token, your snake-colour preference, whether you dismissed the install hint, and development/diagnostic preferences where those tools are available. The room token is removed when you leave or the room is no longer valid; ordinary preferences remain until you change them or clear the site's data.

These technologies provide functions you request and do not track you between unrelated websites. We therefore do not ask for cookie consent or show a cookie banner. If we add non-essential analytics, advertising, or tracking technology, we will obtain consent first and update this policy.

Why we are allowed to use your data

Who else sees your data

Custom leaderboard usernames, ranks, and scores are public. Other players see the room and game information described above. We also use these service providers:

Some processing occurs outside the UK. We use the transfer mechanism applicable to the provider and destination, such as a UK adequacy regulation or contractual safeguards. Email us if you want more information about a particular transfer.

We do not sell your personal data.

How long we keep it

• Your live account: until you delete it or ask us to.
• Match summaries and leaderboard records: while SnakeForTwo operates them as game history. Account links and personal leaderboard rows are removed when an account is deleted as described below.
• Application logs and telemetry: a short rolling window, no more than 30 days. We do not intentionally put IP addresses into match or account records.
• Database backups: 14 days on the production server and 30 days in the restricted off-server backup folder.
• Payment records and parsed provider events: normally six years after the end of the relevant financial year, and longer only where a dispute, refund, investigation, or other legal requirement makes that necessary.
• Browser storage: as described in Cookies and browser storage above.

Deleting your account

Until the in-game deletion control is released, email [email protected] from the address on your account. The self-service control will ask you to retype your username. Deletion from the live production database is immediate and cannot be undone.

Here is what happens:

Erased from the live account system

• Your account username, email address, profile-picture link, and timestamps
• Your Google sign-in link and Google identifier
• Your personal leaderboard entries
• Your SuperSnake entitlement, if you have one

Kept, with the account link removed

• Shared match results. Your participant row stays so the other players' match history is not rewritten, but its account link is removed and its name becomes "deleted player".
• Payment rows required for accounting, refunds, disputes, and reconciliation. Their SnakeForTwo account link is removed.

Kept for the limited retention period described above

• Parsed Stripe events. These can still contain the buyer name and email supplied to Stripe. We restrict them as payment records rather than using them as an active account or marketing list.
• Short-lived logs and backups. These are not used as live account data and age out within 30 days. If a backup is restored, account deletions made after that backup was created must be reapplied before service resumes.

Deleting an account does not transfer its SuperSnake purchase to a later account.

Your rights

Depending on the circumstances, UK data protection law gives you rights to:

• Get a copy of personal data we hold about you
• Correct inaccurate data
• Ask us to delete data or restrict its use
• Object to processing based on legitimate interests
• Receive certain data in a portable format
• Withdraw consent where processing was based on consent

Email [email protected] to exercise a right. We normally respond within one month; the law allows longer for a complex request, and we will tell you if that applies.

You can complain to the UK's Information Commissioner's Office at ico.org.uk or, where applicable, the data protection regulator where you live.

Children

You must be at least 13 to create an account. Children may play as guests without giving us a name or email address, but the technical connection and game data described in this policy still applies. We do not use that data to profile a child, advertise to them, or infer their age.

If you believe a child under 13 has created an account, email [email protected] and we will delete it.

Changes

We will update this policy when our processing changes. If a change is significant, we will give notice by email where practical and by a notice on the site. The date at the top shows when this policy last changed.

Contact

The data controller is:

Oleksandra Safoniuk, trading as SnakeForTwo
33 Edna Road, Leigh, WN7 5ES, United Kingdom
[email protected]

Adapted from Basecamp's open-source policies, used under CC BY 4.0.