Devgame

Privacy policy

Last updated 21 September 2026

In short

  • A minimal audience count: page views per day, with no cookie, no address, no identifier. No advertising, no tracker, no embedded third-party content.
  • Signed out, nothing leaves your browser and no cookie is set.
  • Signed in: your email address, your progress and your runs.
  • The only cookie, if you sign in, is your session cookie.

Data controller

The controller is the site's publisher, identified in the legal notice.

Contact
TODO_PUBLISHER_EMAIL

Signed out

The game works offline. Your progress, the run in progress, a score waiting to be sent and the game clock's setting are written to your browser's local storage, under the keys devgame:meta:v1, devgame:run:v3, devgame:pending-submit:v3 and devgame:idle:v1.

Nothing is sent to the server until you sign in. Clearing the site's data erases all of it, for good: the publisher holds no copy.

Account data

You sign in through a link sent to your email address and, when the publisher has configured it, through Google. Both routes prove the same thing — that the address is yours — so both lead to the same account.

  • Account: id, name, email address, a verified-address flag, and an avatar URL when it comes from Google.
  • Sessions: a token, its expiry date, and the IP address and browser used to open the session.
  • External sign-in: your Google account identifiers and the matching OAuth tokens, only if you go through Google.
  • Verification: the sign-in tokens emailed to you, valid for fifteen minutes.

Legal basis: performing the service you asked for. The email address is required — it is what identifies the account.

Game data

Your profile: display name, level, XP, banked commits, lifetime commits, tickets delivered, unlocks and settings.

A run is stored as its seed and the ordered list of your actions, not as a score. The server replays that list to compute the score, sprints, tickets delivered and commits, along with the start and end times.

A submitted run that fails to replay is kept, marked rejected: it is the only record of what was sent.

What is public

The leaderboard shows your display name, score, sprints, tickets delivered and the date of the run. Your email address appears nowhere.

The display name is yours to choose: pick one you do not mind being public.

Audience measurement

On every page opened, the browser sends the server three values: the page (from a closed list), the language, and whether it is this tab's first page. The server adds one to a daily counter. Nothing else is sent or kept: no IP address, no browser, no identifier, and no cookie is set.

To tell a visit from a page view, a flag is written to the tab's session storage under the key devgame:visited:v1; it goes with the tab. A browser sending the Global Privacy Control signal is not counted at all. Clicks are not measured.

Bug reports

A signed-in account may report a bug: a title, a description, the page and, if given, a run's seed, attached to the account. Reports are read by the publisher and never published; they are deleted with the account.

Gameplay telemetry

When the site is online, the game sends the server the run's save — its seed, its starter profile and the list of decisions taken — when the run ends, every ten sprints, and when a run is left behind to start another. Along with it go the language, the time the tab spent on the run and the idle clock's setting. No account, no identifier, no address: nothing ties a run to a person.

The server replays the save with the game's rules and derives aggregate numbers from it — run length, tiers reached, purchases, answers to events — used to balance the game. A browser sending the Global Privacy Control signal sends nothing.

Cookies

The only cookies are authentication cookies: the session cookie, and very short-lived ones set while you sign in with Google. The language is carried by the address (/fr, /en), not by a cookie. None of them tracks you, so there is no banner to click.

Fonts are served by this site, not by a third party. No request goes out to an external service when a page loads.

Third parties

Three of them, and no more:

  • The host, which runs the machine and the database.
  • The service that delivers sign-in emails.
  • Google, only if you choose to sign in with Google.
Host
TODO_HOST_NAME
Email delivery
TODO_EMAIL_PROVIDER

Nothing is sold, rented or passed to anyone else.

Retention

Account data, the profile and the runs are kept as long as the account exists. No scheduled erasure job runs: nothing disappears after a set period.

Sessions stop being valid at their expiry date, and sign-in links after fifteen minutes.

Your rights

You have the right to access, rectify, erase and port your data, and to object to its processing.

The display name can be changed from the Profile page. For anything else — a copy of your data, deleting the account — write to the contact address: there is no self-service button yet.

Deleting the account cascades to the profile and to every run; the matching rows leave the leaderboard with them.

If you disagree with how this is handled, you can complain to the CNIL (cnil.fr).

Changes

This page can change. The date at the top is the latest version.