Cookie policy

Last updated 16 September 2026.

1. Short version

This site uses cookies only to sign you in and keep you signed in. There is no analytics, no advertising and no third-party tracking of any kind.

Because every cookie here is strictly necessary to provide the service you asked for, none of them require your consent, and you will not see a consent banner. If that ever changes, you will be asked before any optional cookie is set.

2. Cookies we set

Session cookie — keeps you signed in between page loads. It holds a random session identifier, never your password. It is marked HttpOnly, so scripts cannot read it, and Secure, so it is only sent over HTTPS. It expires 30 days after your last visit, or immediately when you sign out.

Sign-in cookies — set only while you are signing in through Discord or Google. They carry the one-time values that prove the reply came back from the provider you were sent to, which is what stops someone else from finishing a sign-in in your name. They are deleted as soon as the sign-in completes.

3. What we store in your browser

The game remembers the callsign you last typed, so you do not retype it every session. It is kept in local storage on your own device, is never sent to us, and clearing your browser data removes it.

4. What we do not do

We do not use analytics, advertising or social network cookies. We do not build profiles of you, and we do not share data with advertisers or data brokers.

The site loads no third-party scripts at all. Its content security policy forbids them, so even a mistake on our side cannot introduce a tracker without a deliberate code change.

5. Declining cookies

You can block or delete cookies in your browser settings. Blocking the session cookie means you cannot stay signed in, and signing in is required to play a match, so most of the site will stop working. The rest of the pages remain readable.

Signing out deletes the session cookie immediately.

6. Changes

If we ever add a cookie that is not strictly necessary, this page will be updated and you will be asked for consent before it is set. Consent will be as easy to refuse as to give, and as easy to withdraw later.

The operating entity is named in the company details before public launch. Until then this document applies as the rules of a closed test.