Privacy & cookies
Cookies we set
We only use cookies required to keep the site working - none of them track you across other sites, and none are used for advertising.
| Cookie | Purpose | Expires |
|---|---|---|
| next-auth.session-token | Keeps you signed in | 30 days |
| next-auth.csrf-token | Protects sign-in forms from cross-site request forgery | Session |
| next-auth.callback-url | Remembers where to send you back after signing in | Session |
| __Host-cla64_guest | Only if you start a free session without an account: links those sessions to your browser, so you can return to them and add them to an account you create. Cleared once you do. | 7 days |
All of them are strictly necessary for the site to work - under GDPR/ePrivacy that category doesn't require consent, only disclosure. We'll add a consent banner here if that ever changes.
Weekly challenges
If you close a weekly-challenge banner, your browser remembers that in its local storage (only the challenge's id), so it stays closed for that challenge. Nothing else is stored, and it never leaves your browser.
Your challenge session, its score and its report are private to you, with one exception. After a challenge, each entrant sees their own place in it - only their own, never how many entered. If at least three entrants score 75 or more, the top three are published on a podium on the challenge page, open to everyone: their name (the name on their account, never their email; an entrant number if they set none or turned their name off in their challenge report), place, language, score and its four parts, and a short summary of how they worked. No code and nothing from their chat is shown, and once a podium entrant deletes their account, the summary is no longer shown. Any other challenge session is public only if you share it: sharing creates a link that shows your name and your score, that session's full report once the challenge closes, and isn't listed by search engines. Turning the link off makes the session private again. By starting a challenge you agree that we use that session - your chat, code and activity in it - to score it, place it and improve the challenges; the challenge page says so before you start. We send at most one challenge email, and only when you ask: the challenge link.
Usage and performance statistics
To see which pages people use and how fast they load, the site records page views, clicks on its main buttons, how far the home page is scrolled, page-load timings and JavaScript errors. This is our own code on our own server - no third-party analytics or advertising service sees it, and no cookies are set for it.
Within a single browser tab we keep a random visit id and how you arrived (the link's campaign tags and the referring site) in your browser's session storage, which is deleted when you close the tab. To count unique visitors without identifying you, the server combines your IP address and browser type with a random value that changes every day and stores only the resulting hash - never the IP address itself. The daily value is deleted afterwards, so the hash can't be traced back to you or linked across days.
If you're signed in, these events are linked to your account, and when you sign up we save how that visit arrived (e.g. which campaign) on your account. We use all of this only as statistics to improve the site.
Showing your local prices
To show the homepage prices in your currency, our server looks up the country your IP address is in, using the free DB-IP Lite country database (IP geolocation by DB-IP). The lookup happens on the request and only the country is kept for that page view - we don't store your IP address for this. If the lookup isn't available, we use your browser's language setting instead.
Free sessions without an account
To limit how many free sessions can be started from one place, starting one without an account stores a keyed hash of your IP address (for IPv6, of your network prefix) - never the address itself - and deletes that hash after 24 hours. We do this only to prevent abuse of free sessions, which is our legitimate interest in offering them at all; the hash isn't used for anything else.
The session itself (your code and chat) is kept like any practice session. If you sign up, it's added to your new account and treated exactly like your other practice sessions from then on.
What we store
If you sign up, we store your email, name, and (for email/password accounts) a hashed password. Signing in with Google or GitHub shares only your name and email with us, never your password.