Cookie Policy
Last updated 17 July 2026
Draft — not yet legal advice. This is a starting template describing how TrainerBook works. It must be reviewed and finalised by a qualified solicitor, and the business details completed, before it’s relied upon.
This policy explains how TrainerBook uses cookies and similar technologies. In short: we use only the cookies that are strictly necessary to run the service — no advertising or tracking cookies.
What cookies are
Cookies are small files a website stores in your browser. Some are essential for a site to work (for example, to keep you signed in); others are used for analytics or advertising.
How we use cookies
TrainerBook uses only strictly-necessary cookies, plus a couple of small functional items stored in your browser:
- Authentication — to keep you securely signed in to your account (set by our auth provider, Supabase).
- Security — Cloudflare Turnstile sets a short-lived cookie to tell humans from bots on our sign-up and login forms.
- Welcome tour — a small flag saved in your browser’s local storage (not a cookie) remembers that you have seen the first-time walkthrough, so it does not reappear on every visit. It holds no personal information and is never shared.
- Which side you were last on — if your login both coaches and trains with someone else, a small cookie remembers which of the two you used last, so returning to the home screen takes you back there. It stores only that choice, identifies nobody, and is never shared or used for tracking.
- Appearance — your light/dark theme choice, saved in local storage so the app looks the same next time you open it.
- Setup checklist — whether you have collapsed the getting-started checklist, so it stays how you left it.
- Push notifications (app only) — if you use the mobile app and allow notifications, your device’s notification token and your opt-out choice are stored on the device. The token identifies the device, not you, and is used only to deliver the reminders you have turned on; turning notifications off removes it.
Analytics
We use Vercel Web Analytics to understand how the service is used — for example, which pages and features are visited. It is privacy-friendly and cookieless: it sets no cookies, does not track you across other websites, and does not build a personal profile of you, so under PECR it does not require a consent banner. The data is aggregated and does not identify you.
What we do not use
We do not use advertising or cross-site tracking cookies, and we do not sell your data. If that changes, we will update this policy and ask for your consent where the law requires it.
Managing cookies
You can block or delete cookies in your browser settings. Note that the strictly-necessary cookies above are required for core features such as signing in — blocking them will stop those features working.
Changes
We may update this policy; the latest version is always on this page.