Cookie Policy

Last updated: 26 August 2026

This Cookie Policy explains what cookies are, what types we use on this website, and how you can control them. Mobile apps (iOS/Android) do not use browser cookies, but may use similar identifiers described below.

1. What Are Cookies

Cookies are small text files stored on your device when you visit a website. They allow the site to recognise your browser and remember certain information. Similar technologies also exist (localStorage, sessionStorage, device identifiers) that work in a comparable way but are not classic browser cookies.

2. Cookies We Use on the Website

2.1 Strictly Necessary Cookies

Essential for the website to function. They do not require your consent and cannot be disabled.

Security tokens — protect against common web attacks
Preference storage — remembers basic display settings

Legal basis: legitimate interest and performance of contract (GDPR Art. 6(1)(b), (f)).

2.2 Analytics and Marketing Cookies

We currently do NOT use analytics, advertising or marketing tracking cookies on the website. If this changes, we will update this policy and ask for your consent first.

3. Identifiers in the Mobile App

The iOS and Android apps do not use browser cookies, but store or use:

Supabase session token — kept on your device to keep you signed in. Legal basis: performance of contract.
RevenueCat app user ID — an identifier used to manage your subscription entitlement across devices.
Firebase Cloud Messaging registration token — an identifier for your installation, used to deliver push notifications for watchlist alerts. Legal basis: performance of contract.
Anonymous session token — when you use the App as a guest, a session token for an anonymous account is kept on your device in place of a signed-in session.
Sentry event identifiers — random identifiers attached to crash reports, in builds where crash reporting is enabled.
Local preferences — theme, accent colour and similar UI settings, stored only on your device.

We do not collect the IDFA (iOS) or GAID (Android) advertising identifiers. The app shows no ads and performs no cross-app tracking; on iOS, no App Tracking Transparency prompt is needed because no tracking occurs. If this ever changes, we will request your explicit permission first.

4. Third-Party Cookies

Our main third-party providers and their policies:

Supabase — authentication and backend: supabase.com/privacy
RevenueCat — subscription management: revenuecat.com/privacy
Google (Firebase Cloud Messaging) — push notification delivery: firebase.google.com/support/privacy
Apple / Google — if you purchase through their stores, their own policies apply.

We do not control third-party cookies or identifiers. Please consult their policies for details.

5. Identifier Lifespan

Website session storage: deleted when you close your browser
Supabase auth token: refreshed automatically while you stay signed in; removed on sign-out
Firebase notification token: rotated by the operating system as needed; removed when you delete your account, and invalidated when you uninstall the app
Local UI preferences: until you clear the app's data or uninstall

6. How to Control Cookies and Identifiers

Browser settings: you can block or delete cookies from your browser settings (Chrome, Firefox, Safari, Edge).
In the app: signing out removes your session token; deleting your account removes your server-side data (see the Privacy Policy).
Device settings: uninstalling the app removes all locally stored preferences and tokens.

7. Contact

Email: contact@chessnewlife.com