Cookies & device storage
Last updated: 24 October 2026 · Current web service · Revision 12
1. Current use
The current SCORESIST web release has no advertising or behavioral-analytics integration of its own and does not set advertising or analytics cookies. It uses browser storage to remember features you choose and the browser may cache files needed to display the site. Cookies and local storage are different technologies; both matter when explaining information stored on your device. A match video loads from YouTube only after you press play; section 6 explains what YouTube may store then.
2. What is stored
Language: selected_locale remembers a language you select. Selected sport: selected_primary_sport remembers your sport choice. Appearance: scoresist_appearance_v1 and related preference/pending flags remember your theme, fan selection and intensity; a signed-in account has its own copies, whose names end in the account ID. Favorites: scoresist_guest_favorites_v1 stores selected entities; scoresist_guest_match_favorites_v1 stores saved matches and their refresh/expiry information. Hints: favorites_sign_in_prompt_dismissed remembers that you closed the sign-in hint above your favorites, and fan_mode_hint_seen that the fan-mode hint was shown. Sign-in, only when you use it: sb-auth-auth-token keeps your session until you sign out or delete the account: access and refresh tokens and the account details Supabase returns, such as your email address and the name and picture link Google provided, and, right after a web sign-in, Google's short-lived access token; supabase.auth.token-code-verifier holds a one-time code for a Google sign-in; it is removed when a sign-in completes or you sign out, and replaced by the next sign-in; scoresist_auth_return_route remembers which page to open after signing in; it is valid for 10 minutes and removed when the app next opens; scoresist_nickname_prompt_dismissed_ followed by the account ID remembers that you chose "Not now" for a nickname. scoresist_notification_prefs_v1_ followed by the account ID keeps a copy of your notification choices on the device. Browser keys may include the flutter. prefix. Old selected_theme_mode preferences may be migrated. These are first-party functional settings, not advertising identifiers.
3. Purpose and duration
We use these settings to provide the remembering, favorite and sign-in features you request, rather than for audience measurement. Sign-in storage is strictly necessary to provide the sign-in you ask for (section 25(2) no. 2 TDDDG), so it does not depend on consent. Settings normally remain until you change them or clear site data; the session ends when you sign out or delete your account. Finished matches stop appearing in favorites when their expiry is known, normally one hour after completion; stored copies may remain until the next successful refresh or manual clearing. Browser-managed file caches follow your browser's retention settings. Google's sign-in pages set Google's own cookies under Google's policy.
4. Your controls
Use the language and theme menus, change your selected sport, or remove a favorite with its star control. To remove all local choices, open your browser's privacy/site settings for scoresist.com or www.scoresist.com and clear cookies and site data for the address you used. Storage can be separate for each hostname and device. Blocking storage can prevent preferences and favorites from being remembered. Signing out removes the session from this browser. Clearing browser data also signs you out there, but it does not delete your account or any correspondence already sent to support.
5. Why there is no Accept all banner now
There are no optional advertising or analytics categories to enable in this release. Storage strictly necessary to provide an expressly requested feature, such as remembering your choices or keeping you signed in, is treated separately from consent-dependent storage. The current features are limited to service delivery and remembering your choices. Match videos are click-to-load: pressing play on a video is your consent for that video only (section 25(1) TDDDG), and neither your browser nor the app requests anything from YouTube before that. Looking up your approximate country from your IP address (privacy notice, section 3) uses only the address that comes with each request; it stores nothing on your device and reads nothing from it. This notice is information, not a request to accept all future processing. If we add advertising, optional measurement or other consent-dependent technologies, we will provide the required choices before activation, including refusal and a way to change your choice. Non-personalized advertising can still require consent; it will not be enabled merely because it is called non-personalized.
6. External resources
Sports images and rendering resources may be fetched from external hosts, which receive normal network metadata. After you press play on a match video, the video loads from YouTube (www.youtube-nocookie.com), and YouTube (Google) may then place or read cookies or similar storage on your device under the Google Privacy Policy (https://policies.google.com/privacy). In the Android and iPhone apps the video plays in a web view inside the app, and what YouTube stores there can stay in the app's storage on your phone until it expires or you clear the app's data or uninstall the app. This is explained in our privacy notice. It is not a claim that third-party infrastructure receives no data. Contact support@scoresist.com with questions about device storage or privacy.