Privacy

Who handles your data

Ambroise Krzanowski, who publishes this site, is responsible for the processing described here. Contact: [email protected].

Reading the site

Reading the site needs no account. The only cookie a reader can get remembers the language they chose (see “Cookies and local storage”).

To measure its audience, without any third-party service, the site records the pages viewed, the page you came from, the device type, the browser, the screen size, the language, how much of the page you read, how long the visit lasts, the links you click and whether it is a first visit. A random identifier, kept for 13 months at most in your browser's local storage, tells visits apart; it says nothing about you, and your IP address is not recorded. These statistics stay anonymous, serve this site only and are deleted after 25 months (the publisher's legitimate interest, GDPR article 6.1.f). You can refuse this measurement below; clearing the site's data in your browser also erases the identifier.

The contact form

Your name, email address, subject and message are only used to answer you. They are kept for as long as the exchange lasts.

The mini-game

If your score makes the leaderboard, the three characters you enter as initials, the score and its date are recorded; the ten best scores are shown publicly.

Taking part: GitHub sign-in

Voting, liking, commenting and reporting go through a GitHub sign-in. The site asks GitHub for no permission: it only reads your numeric id, your username and the date your account was created. It never keeps the access token GitHub provides and asks GitHub to revoke it right after that read. You can withdraw the authorization given to the app at any time in your GitHub account settings (Settings › Applications › Authorized OAuth Apps).

The site keeps that id, that username, the GitHub account's creation date, the dates of your first and last sign-in and, where relevant, the date your account was deemed trusted or banned. It also keeps your votes, likes, reports and comments, with their language, their date and when they became visible, and your profile settings: the avatar you picked, whether your profile is public, your bio and the one awaiting review, and when you last marked your replies as read.

Public: your comments, with your GitHub username, their language and date, and the vote and like totals. Who voted or liked is never shown. Your profile stays hidden until you make it visible; once visible, its page shows your avatar, your bio, when you joined, how many comments you wrote and your published comments.

If you pick your GitHub photo as avatar, the browser of everyone who opens your public profile loads it straight from GitHub's servers (avatars.githubusercontent.com), without saying which page it comes from: GitHub then sees that person's IP address. The same goes for you in your account panel and on the “My account” page. The default avatar, a fingerprint drawn by the site, calls on no third party.

This data runs what you ask for by signing in (GDPR article 6.1.b) and is used to moderate discussions and prevent abuse, the publisher's legitimate interest (article 6.1.f).

How long

As long as your account exists. Once signed in, the “My account” page lets you download all this data as a JSON file and delete your account: that erases your votes, likes, reports, settings and comments; a comment that got replies stays as “[deleted]”, without text or author, so the discussion stays readable.

If your account had been banned, only its GitHub id, the ban date and the deletion date are kept, so the ban holds.

The site's backups keep a copy of its database, contact messages included, for up to about five weeks: whatever is erased leaves them as they are renewed.

Cookies and local storage

locale: set only if you switch language, for one year; it remembers your choice. visitor_session: set only after you sign in with GitHub, for 30 days; it keeps you signed in. oauth_state: 10 minutes during sign-in, to secure it. These cookies only serve what you ask for. No advertising or audience-measurement cookie.

Your browser's local storage also keeps your preferences, which are never sent to the site: the light or dark theme, paused animations and your best score in the mini-game.

For the audience measurement, local storage keeps _ak_vid, the visit identifier, with its creation date (_ak_vid_at), and _ak_visits, the number of your visits, which only tells whether it is a first visit: 13 months at most, then a new identifier replaces them. Session storage keeps _ak_sid, the identifier of the current visit, erased when the tab closes. _ak_vid and _ak_sid go with each page view. If you refuse the measurement, they are erased and _ak_optout remembers that choice, without ever being sent.

Who else sees this data

Nobody buys it or receives it for their own use. The site runs on the publisher's own server, in France, and goes through Cloudflare, which forwards requests and sees your IP address to do so; Cloudflare takes part in the EU-US Data Privacy Framework. To sign in, you go through GitHub, under its own privacy policy.

Your rights

You can access your data, have it corrected or erased, object to its processing, restrict its use and receive it in a readable format: the “My account” page already lets you download it and delete everything. For the rest, write to [email protected]. If the answer does not satisfy you, you can complain to the CNIL, the French data protection authority (cnil.fr).