Cookies Declaration

Effective date: August 21, 2026

This Cookies Declaration explains how OutScore uses cookies and similar technologies (localStorage, sessionStorage, and browser databases). It is part of our Privacy Policy. We use these technologies to run the service — sign-in, security, performance, and basic first-party usage measurement — not to run advertising networks.

1. What we mean by cookies and similar technologies

A cookie is a small text file stored on your device by a website. OutScore also uses browser storage that is not a cookie, such as localStorage, sessionStorage, and IndexedDB. Browsers treat these similarly for privacy purposes, so we describe them together.

We do not currently use a third-party advertising or retargeting pixel, and we do not load Google Analytics in the application. A measurement ID may exist in configuration for possible future Firebase Analytics; it is not used to send advertising events today.

2. Strictly necessary storage

These items are required for OutScore to work as a signed-in or live-scoring product. Blocking them may prevent login, MFA, or tournament pages from functioning.

  • Firebase Authentication persistence (browser local persistence / IndexedDB or localStorage): keeps you signed in across visits until you sign out. Set by Google Firebase when you log in.
  • Firestore persistent cache (IndexedDB): stores recent tournament data on your device so pages load faster and can work more reliably. Set by the Firebase SDK.
  • outscore_menu_user (first-party cookie, about 7 days, SameSite=Lax): caches display information for the account menu (name, email, photo URL, and permission-related fields) so the header can render quickly. It is cleared when you sign out.
  • Captain link tokens (sessionStorage, keys beginning with os-captain-link:): remember a captain-access token for the current browser tab session so a captain does not lose access when moving between pages. Cleared when the tab or browser session ends.
  • Scorekeeper and schedule caches (localStorage): store recent settings, teams, players, or game events for a tournament so scorekeeper and schedule views load faster. These stay until you clear site data.
  • outscore_cookie_consent (first-party localStorage): remembers whether you opted out of visit logging so we do not ask on every page load. Strictly necessary to honour your choice.

3. Analytics and measurement (first-party)

When you visit the marketing homepage (and selected promo landing pages), OutScore may record a visit in our own database: time, referring site, browser user agent, platform, and a mobile/desktop hint. This is ordinary first-party traffic measurement, not a cookie placed on your device, and it does not follow you around the web. It runs unless you opt out.

When you use a tournament, we may record usage events (for example logins or page visits) including a timestamp, tournament id, event type, and, if you are signed in, your user id. These records stay on our systems so we can operate and improve OutScore. They are not advertising cookies.

You can turn this visit logging off with the control on this page. Essential cookies that make the app work are not part of that opt-out.

4. Third-party cookies

When you subscribe or manage billing, you are sent to Stripe Checkout or the Stripe Customer Portal (hosted by Stripe). Stripe may set its own cookies on stripe.com domains to process payment, prevent fraud, and keep that checkout session working. Those cookies are governed by Stripe’s documentation and privacy policy. We do not read your full card number.

Google / Firebase may set cookies or storage required for authentication and infrastructure when you use sign-in and data sync. See Google’s privacy documentation for Firebase.

5. How long they last

Session storage lasts until you close the tab or browser. The account-menu cookie lasts up to seven days or until you sign out. Authentication and Firestore caches last until you sign out or clear site data for www.out-score.com. Stripe cookie lifetimes are set by Stripe.

6. How to control cookies and storage

Most browsers let you block or delete cookies and site data. If you block all cookies or storage, you will likely be unable to stay signed in or use scorekeeper tools reliably.

You can sign out to clear the account-menu cookie and end the Firebase session. Clearing cookies for this site in your browser settings removes first-party cookies and, depending on the browser, related site storage.

On your first visit we show a small notice that we use essential cookies, with a link to this page. That notice is not a request for advertising or tracking cookies — we do not use those. Visit counts in our database are described on this page and stay on unless you use the control below to ask us not to log visits.

7. Contact

Questions about cookies or this declaration: Info@out-score.com. See also the Privacy Policy at https://www.out-score.com/privacy.

Terms of ServicePrivacy PolicyCookies