Privacy Policy

Effective: November 2026

Information We Collect

When you sign in with GitHub, we receive and store your GitHub user ID, username (login), and avatar URL. If GitHub provides them, we also store your name and email, along with the OAuth tokens received during sign-in.

If you create snakes, we store the name and URL you provide. Game history — including moves and outcomes — is stored for each game played.

For signed-in web and API-token requests, we store your account ID and the UTC date of activity.

We keep operational logs, traces, and product analytics in an observability system we run ourselves and in PostHog (US cloud), our analytics processor. This data can include account identifiers, usernames, email addresses, snake names and URLs, IP addresses, browser user agents, request URLs and referrers, game data, and message contents.

Credentials, including passwords, tokens, secret URL parameters, authorization headers, and cookie headers, are removed before data goes to PostHog.

This data has no fixed deletion date, and deleting your account does not remove what was already recorded.

Play.battlesnake.com Migration Data

If you had an account on the old play.battlesnake.com, we imported your email, username, display name, profile fields (pronouns, country, backstory), and historical Play points totals as migration records. Points are not used to unlock customizations in Battlesnake. Your play password was imported in hashed form only — it is never stored in plaintext, and it is checked only to verify a claim. When you claim your account, your play snakes and customization unlocks are merged into your Battlesnake account.

How We Use Your Information

We use your information to:

  • Authenticate you and manage your session.
  • Display your profile and snakes.
  • Run games and store game results.
  • Maintain leaderboards and tournament results.
  • Compute aggregate usage statistics, such as daily, weekly, and monthly active accounts, to operate and improve Battlesnake. We may publish these statistics in aggregate form; published statistics never identify individual accounts.
  • Operate, debug, and improve Battlesnake using the technical logs described above.
  • Analyze product events and server telemetry using PostHog.
  • Send transactional email (via Mailgun) when your play account is claimed, as a security notice.
  • Notify you by email if your snake is removed from leaderboard matchmaking because its server keeps failing.

We do not send marketing emails. We do not show advertisements. We do not sell your data. We share it only with the service providers that run Battlesnake on our behalf — Mailgun for transactional email, Google Cloud for hosting and storage, TypeSafe for automated moderation of snake names, tournament names and descriptions, saved game titles, and snake shouts, the providers that host our observability system, and PostHog (US cloud) for analytics. We also post new sign-ups, Play account claims, and newly registered snakes to the Battlesnake community Discord, and those posts include GitHub usernames, Play usernames, and snake names.

Data Storage

Battlesnake is hosted on Google Cloud. Game data from the legacy Battlesnake Engine may be archived to Google Cloud Storage. Technical logs are stored with the providers that host our observability system and with PostHog (US cloud). PostHog product events and boot manifests have no fixed deletion date unless a verified project retention setting says otherwise. Google Cloud also keeps server and load balancer logs for a short time, which can contain account identifiers, usernames, email addresses, snake names and URLs, IP addresses, browser user agents, request URLs and referrers, game data, and message contents.

Cookies

Battlesnake uses a single functional session cookie (HttpOnly, Secure, SameSite=Lax) to keep you logged in. We do not use tracking cookies, analytics cookies, or advertising cookies.

Contact

Questions about privacy? Reach us on the Battlesnake Discord.