Cookies and local storage

What actually gets written

Very little, and each item has a job you can check.

The 18+ confirmation

A single flag in local storage recording that you confirmed your age, so the gate does not reappear every time you open the site. It stays on your device — it is not transmitted to us and not tied to any identity.

Session state

What keeps you connected while you are actually using the service, and signed in if you chose to sign in. Clearing it signs you out; nothing else breaks.

Preferences

Small settings you have chosen, so the site does not forget them between visits.

Why local storage rather than a cookie

A cookie is sent to the server with every request; local storage is not. For something like the age flag, which is only a note to your own browser, local storage means the information stays on your device rather than travelling to us on every page load. That is the right default for a piece of data nobody else needs.

Removing all of it

Clearing site data for this domain in your browser settings removes everything above, including the age flag — the gate will ask again next time, which is the expected result rather than a fault.

Browsers can also block storage for a site entirely. Doing that here means the age gate appears every visit and you will not stay signed in; the service otherwise works.

The one third party

Google Analytics measures which pages get used and whether the site is working. It sets its own storage on your device to tell a returning visitor from a new one, and that is the only third party with anything on this domain.

What it gives us is counts and trends — how many people opened a page, where they arrived from, whether something is broken. It is not a file on you, and it has no access to anything inside a call, because there is nothing recorded inside a call for anything to have access to.

If you would rather not be counted, Google publishes a browser add-on that opts you out of Analytics across every site that uses it: tools.google.com/dlpage/gaoptout. Blocking it changes nothing about how the service works for you — measurement is the only thing affected.

What is not here

This is the part of a cookie page actually worth reading, so it is stated plainly rather than left to inference.

• No advertising cookies, and no ad network reading anything from this domain.
• No cross-site tracking pixels following you around other sites. The measurement above counts visits here; it does not follow you elsewhere.
• Nothing recording what happens inside a call — there is nothing recorded to store.
• Nothing that ties browsing on this site to a real-world identity. Starting a match needs no account, so for most visitors there is no identity to tie it to.

If that ever changes, this page changes in the same release and the privacy policy changes with it. Questions: [email protected].