Cookie Policy
This page explains how FootballStatus uses cookies and similar storage, what analytics information we collect when you consent, and how you can change your choices at any time.
Summary
We use first-party cookies and similar local storage to keep core features working and, only with your consent, to support preferences, analytics, and advertising.
What we store
- A first-party consent record stores your selected categories, the consent version, and when you made your choice.
- Necessary storage supports account/session security and core site functionality.
- If you allow analytics, we store a random first-party analytics session ID to group consented events.
What analytics can collect
- Event names such as preview views, paywall displays, checkout starts, portal opens, and confirmed checkout completions.
- Context fields like surface, source, mode, action, and small boolean flags such as authentication or premium status.
- We do not store email addresses, match IDs, Stripe IDs, or IP addresses in analytics events.
Cookie Categories We Use
Cookie categories on FootballStatus are:
- Necessary: required for core functionality such as security, session handling, and account access.
- Preferences: remember settings that improve usability and display behavior.
- Analytics: help us understand traffic and performance so we can improve the service.
- Advertising: used for Google AdSense ad delivery, measurement, and related controls.
Necessary cookies are always active. Preferences, analytics, and advertising are optional and depend on your consent choices.
Analytics on FootballStatus
When you allow the Analytics category, FootballStatus sends consent-aware product analytics events to our own backend so we can understand feature usage and improve the service.
What we collect for analytics
- A random first-party analytics session ID (`fs_analytics_session`) used to group events from the same browser after consent.
- Event names related to product usage, including prediction previews, paywall views, CTA clicks, checkout starts, confirmed checkout completions, and billing portal opens.
- Small context fields such as `surface`, `source`, `mode`, `action`, and booleans like `isAuthenticated`, `isPremium`, `hasCreditsAvailable`, and `trialEligible`.
- If you are signed in, events can be associated server-side with your authenticated account ID from Supabase cookies. The client cannot send another user ID.
What we do not collect in analytics
- No email addresses.
- No match identifiers.
- No Stripe identifiers.
- No IP addresses stored in analytics events.
Analytics remains a strict no-op until you consent. If you revoke analytics later, the persisted analytics session ID is cleared. When our consent policy changes, we may ask you to review your choices again.
Google AdSense and Advertising Cookies
FootballStatus uses Google AdSense for ads. Advertising cookies or similar identifiers can be used for ad delivery, frequency control, fraud prevention, and ad performance measurement.
Personalized and non-personalized ad behavior depends on your advertising consent and applicable regional requirements.
If you do not consent to the Advertising category, we block ad script loading by default.
How to Change Cookie Settings
Use the Manage cookies action in the consent banner to review and set your granular choices.
You can also reopen preferences anytime from the Cookie settings link in the footer or from the Manage cookies action on this page.
You can also manage or delete cookies in your browser settings. Browser behavior may vary by vendor and version.
Changing browser settings may impact how some features work, especially account/session-related functionality.