Cookie and storage notice
Last updated Nov 8, 2026 · Version 2026-11-08
FairRally uses only the cookies it needs to sign you in and remember your theme. There are no advertising, analytics or tracking cookies, and no third-party cookies. Because every cookie here is essential, there is no cookie banner.
The cookies we set
- Sign-in session (
sb-...-auth-token, sometimes split into parts ending.0,.1): keeps you signed in. It holds your sign-in tokens. Set by our sign-in provider's code on our own domain. It lasts up to 400 days but is refreshed or cleared as you use the app, and removed when you sign out. The app's own scripts can read it, because live scores need it to connect. - Google sign-in check (
sb-...-auth-token-code-verifier): a one-time security code used while you sign in with Google. It is used up when you come back from Google. - Where you were heading (
post_auth_next): remembers a page inside FairRally, such as an invite link, while you sign in. It holds a page address only, and lasts at most one day. It is removed once used. - Theme (
theme): remembers light, dark or system so the page shows the right colours straight away. It lasts one year. It holds no personal data.
The post_auth_next and theme cookies cannot be read by scripts in the page. The live site is served only over HTTPS, so cookies travel encrypted.
Other storage
- FairRally does not use local storage, session storage or other browser databases.
- Fonts are served from our own site, so loading a page does not contact Google Fonts.
- When you press "Continue with Google", you go to Google's own sign-in page. Google may set its own cookies there, under Google's policies.
Your choices
You can delete cookies in your browser settings at any time. If you block or delete the sign-in cookies, you will be signed out and will need to sign in again.
See also: Privacy policy.