SIGN IN

LEGAL//privacy

Privacy Policy

LAST UPDATED OCTOBER 20, 2026

THE SHORT VERSION

  • We measure activity, not code. We never read or store your source code or commit messages.
  • Repository names and private-repository activity are never shown publicly.
  • Your profile, stats, and Graveyard entry are public. The Graveyard is permanent.
  • No ads, no third-party analytics, no tracking cookies. We do not sell your data.
  • Creem handles your payment. We never see your card.
  • Partner coupon codes and connected API keys are stored encrypted and never shown publicly.

01Who we are

This policy explains how Commit Eater ("we", "us") handles personal data when you use our website, game, GitHub App, and partner portal. We are the controller of the data described here, except payment data, which Creem handles as merchant of record (see below). For any privacy question or request, write to privacy@commiteater.com.

02What we collect

From your GitHub sign-in: your GitHub numeric user ID, username, avatar, and the email GitHub shares with us, plus the access token GitHub issues for the sign-in. Tokens stay on our servers and are never shown or shared.

From you: a contact email if GitHub did not provide one, and anything you add to your profile: display name, bio, photo choice, X and LinkedIn handles, website, and project display names.

From the GitHub App: the installation ID, the account it is installed on, the permissions granted, and its status. For each repository you select, we keep its GitHub ID, its name, whether it is private, and whether you paused it. These are never public.

Commit evidence: for each commit pushed to a selected repository, we keep the repository ID, the commit SHA, the author's GitHub ID, the commit time, and whether it counted (and why not, if it did not). We roll these up into daily totals that drive XP, hunger, streaks, and leaderboards.

What we never collect: your source code, diffs, file paths, commit messages, or branch names. Our GitHub App has read-only access and cannot change your repositories.

Game records: your run state, start and death dates, XP, level, coins and coin history, streaks, hunger, and, once the shop opens, the perks you buy.

Payment records: Creem's event ID, checkout and customer IDs, amount, currency, and status. We never see or store your card details.

Technical records: delivery IDs and minimal metadata from GitHub and Creem webhooks, and the server logs our hosting provider keeps to run and secure the Service. To limit abuse of sign-in and other sensitive actions, we keep short-lived counters keyed by a one-way hash of your IP address or email, never the address itself, and delete them within a day.

03If you use the partner portal

For people who sign in to the partner portal on behalf of a launch partner, we keep:

  • Account data: your work email, the partner you belong to, a one-way hash of your password (never the password itself), sign-in times, and failed sign-in counts used to lock the account after repeated wrong passwords.
  • Products: the product details and discounts you enter. These are shown publicly in the shop together with your company's name.
  • Coupon codes: encrypted at rest. A code is only ever shown to the player who bought it.
  • A connected billing-provider API key, if you connect one: encrypted at rest, never shown again, with only its last 4 characters kept readable so you can tell which key is connected. It is deleted as soon as you disconnect it or leave the program.
  • AI assistant tokens, if you create any: a one-way hash of each token (never the token itself), its name, permissions, last 4 characters, expiry, and when it was last used. Revoked tokens are kept as records until the partner leaves the program, when they are deleted. If you connect an AI assistant, what you send through it also goes to that assistant's provider under its own privacy policy.
  • Activity records: what was done and when (for example, an upload or a generated batch and how many codes it added, and whether it came through the portal or an AI assistant), never the codes, the key, or a token.

We use this to run the partner program and keep it secure (our contract with the partner and our legitimate interests). Your email, the codes, and the key are never public. When a partner leaves the program, its people can no longer sign in; we keep the account records and codes needed to support players who already bought a perk, and you can ask privacy@commiteater.com to delete your personal details.

04Why we use it

  • To run the game you paid for (performance of our contract with you): sign-in, counting valid commits, daily evaluation, XP, coins, death, the shop, and your profile.
  • To keep the game fair and secure (our legitimate interests): preventing abuse, enforcing one life per GitHub account, fixing errors, and auditing corrections.
  • To meet legal obligations: payment, tax, and accounting records, and answering lawful requests.
  • To contact you about your account, payment, run, or perks. We do not send marketing email, and we do not sell or rent your personal data.

05What is public

Commit Eater is a public competition. Anyone can see, on your profile, the leaderboards, and the Graveyard:

  • Your GitHub username and, if you choose it, your GitHub avatar.
  • Your display name, bio, links, and project display names, if you add them.
  • Your game stats: alive or eaten, start and death dates, lifetime, streaks, level, XP, commit count, and your creature's hunger state.

Never public: repository names, repository IDs, whether any activity came from a private repository, commit details, your email, and your payment details. Project display names are names you choose and do not have to match any repository.

The Graveyard is a permanent record of the game. Your entry stays after death. If you delete your account, your public entries are anonymized rather than showing your identity.

06Who we share it with

We share data only with the providers that run the Service, and only what they need:

  • GitHub for sign-in and for delivering your push events. GitHub's own privacy statement covers your GitHub account.
  • Creem, our merchant of record, processes your payment, collects tax, and issues receipts under its own privacy policy. We send Creem an internal account reference so it can tell us your payment succeeded.
  • Creem, Stripe, Dodo Payments, RevenueCat, Lemon Squeezy, or Polar, for partners who connect them: we ask the provider to create discount codes in that partner's own account, and to read the coupon, discount, or product variants they pick. No player data is sent with those requests.
  • Vercel hosts the application, and Railway hosts our database.

We may also disclose data when the law requires it, to protect players or the Service, or to a successor if Commit Eater is transferred, in which case this policy continues to apply.

07Cookies and analytics

We use only the cookies needed to sign you in and keep you signed in securely: a session cookie and short-lived cookies that protect the GitHub sign-in flow, and, in the partner portal, a separate partner session cookie that lasts up to 7 days. We do not use advertising cookies, third-party analytics, or tracking pixels, so there is nothing to opt out of. If that changes, we will update this policy first and ask for consent where the law requires it.

08How long we keep it

  • Account, profile, and game records: for as long as your account exists. Dead runs stay in the Graveyard because it is a permanent record.
  • Commit evidence and daily totals: for the life of your run record, since leaderboards and corrections must be reproducible from them.
  • Webhook delivery records: only minimal metadata, kept for diagnosing and safely reprocessing events.
  • Payment records: as long as tax and accounting law requires.
  • Sessions: until you sign out or they expire.
  • Partner API keys: until the partner disconnects the key or leaves the program, whichever comes first.

09Disconnecting and deleting

You can pause or remove repositories in Settings, or uninstall the GitHub App on GitHub at any time. From then on we stop receiving events for those repositories. Data we already recorded stays with your run record until you delete your account.

To delete your account, write to privacy@commiteater.com from your account email. We delete your contact email, profile details, tokens, and repository list, and anonymize your public entries and remaining game history. We keep your GitHub numeric ID so the same GitHub account cannot start a second life, and we keep payment records the law requires. Deletion ends any run in progress and cannot be undone (see the Terms).

10Your rights

Depending on where you live, you may have the right to access your data, get a copy of it, correct it, delete it, restrict or object to how we use it, and complain to your local data protection authority. Write to privacy@commiteater.com and we will answer within 30 days. We may ask you to confirm you own the account before acting.

Some data cannot be changed without breaking the game's integrity, such as a recorded death or the one-life restriction. Correcting game records follows the audited process in the Terms.

11International processing

Our providers may process data in the United States and other countries outside your own. Where the law requires it, we rely on appropriate safeguards for those transfers, such as the European Commission's standard contractual clauses.

12Security

We verify every webhook signature, keep tokens and secrets server-side, keep sensitive data out of our logs, and limit our GitHub App to read-only access. No system is perfectly secure; if a breach affects your data, we will notify you as the law requires.

13Age

Commit Eater is only for people aged 18 or older. We do not knowingly collect data from anyone younger. If you think a minor has an account, contact us and we will delete it.

14Changes to this policy

If we change this policy in a way that matters, we will tell you by email or in the game before it takes effect. The date at the top shows the current version.