1. What we set
Nothing. The marketing site sets no cookies. It used to set one functional cookie (odds_city) to remember which city's content you were viewing; the city layer was removed and the cookie with it. A stale odds_city value from an earlier visit is not read. The native apps use one strictly necessary, first-party cookie to keep you signed in. It carries a login refresh token between the app and our backend, and we use it only for that purpose, not for tracking or advertising. If you sign in with Google, Google may set its own cookies during that sign-in, under Google's privacy policy.
2. What we do NOT set
No Google Analytics (_ga, _gid, _gat_*). No Meta / Facebook Pixel (_fbp, fr). No Mixpanel, Amplitude, PostHog, Segment, Heap, or other product-analytics cookies. No Vercel Analytics or Speed Insights cookies. No advertising or retargeting cookies (Google Ads, Meta Ads, LinkedIn, X, TikTok). No A/B testing or session-replay tools (Statsig, FullStory, Hotjar, LogRocket).
3. Why we don't show a consent banner
We set no cookies, so there is nothing to consent to. Even when we did, the single cookie was strictly necessary for the site to function, and strictly-necessary cookies are exempt from prior-consent requirements under the EU ePrivacy Directive (Art. 5(3)) and similar US state laws. If we ever add any non-essential cookie or tracking technology, we will (a) update this page and the privacy policy, (b) add a compliant consent banner with reject-all parity, and (c) gate the new cookie behind affirmative consent for EU / UK / EEA traffic before it can be set.
4. Local storage and similar technologies
The marketing site does not use localStorage, sessionStorage, IndexedDB, or service workers for tracking. The Next.js framework may use them transiently for routing and HMR. The staff-only /admin area keeps its session token and UI preferences in localStorage; it is only set for signed-in staff. The native apps store auth tokens in iOS Keychain and Android EncryptedSharedPreferences, and store a stable per-install UUID and your notification preferences in UserDefaults / SharedPreferences. None of these are accessible to third parties.
5. Managing cookies
There is nothing to manage — the site sets no cookies. Any leftover odds_city value from an earlier visit can be cleared through your browser's cookie controls; nothing on the site reads it.
6. Contact
Questions: privacy@oddsrunning.com. See also the full privacy policy.