Legal
Privacy policy
Last updated 19 November 2026
This policy explains how BadmintonBooker (“we”, “us”) handles personal information when you use badmintonbooker.com.
Studio Tom (Thomas Al-Hariri) runs BadmintonBooker and is the data controller. For privacy questions or data-subject requests, email hello@studiotom.co.uk.
This page is a practical notice for a small UK side project, not formal legal advice. If you need certainty for your own situation, speak to a solicitor.
What we collect
- Usage data: how the site is used (pages viewed, searches, basic browser and device info, and typically IP address as received by our analytics processors). See below and our cookie policy.
- Venue / gym requests: if you ask us to add a venue, we store the details you submit (such as gym name, booking URL, and optionally your name and email) so we can follow up. We keep these while they are useful for that follow-up; there is no automated purge job today.
- Correction emails: if you email us about a mistake or ask us to change or remove a venue, we keep your email so we can act on it and keep a record.
- Share polls: when you create or vote on a poll, we store vote choices, an optional display name, a random voter token on your device, and the request IP address (used for rate-limiting abuse). Polls expire after about 14 days and are then removed by a scheduled purge.
- Location search: if you type a place into the location box, that text is sent to Geoapify to suggest places. It goes in the web address, so it may show up for a short time in our hosting provider’s request logs.
- Use my location: your browser asks first. We round your position to about 100 metres and send it to Geoapify once to get your area’s name (like “Near Tolworth”). It isn’t sent with your search or saved in our database, but your browser keeps it on your device (in local storage and the page’s history) so it’s there next time. We don’t use your location for advertising.
- Preferences on your device: things like theme, selected sports, and last location (kept across visits in local storage), plus tab-scoped gym picks in session storage for the current visit.
Why we use it
- To run and improve the court-finding product
- To respond to venue requests you send us
- To power share-with-friends polls you choose to use
- To understand how the site is used via basic visit counting (Vercel, and PostHog in cookieless mode), and, when you opt in, PostHog (including session recordings) and Google Analytics
Lawful bases
In short: necessary things just work, statistics are on unless you opt out, everything else needs your OK.
Under UK GDPR we rely on: legitimate interests for running a useful site and for basic visit counting (Vercel Web Analytics and PostHog in cookieless mode); consent for cookie-based PostHog (including session recordings), Google Analytics, and cookies that are not strictly necessary; and contract / steps you ask for when you submit a venue request or use polls. Where PECR requires consent for storing or accessing information on your device, we ask before doing so, except for strictly necessary storage and for basic visit counting, which falls under the PECR statistical-purposes exception (Schedule A1, added by the Data (Use and Access) Act 2025).
You can object to anything we run on legitimate interests. For basic visit counting, switch Basic visit counting (no cookies) off in Cookie settings, or switch on Global Privacy Control or Do Not Track in your browser. We detect either and stop that counting. If you previously opted in to Analytics, that explicit choice stays until you withdraw it via Cookie settings in the footer — turning on GPC/DNT alone does not undo an opt-in. You can also email us.
Analytics
- Basic visit counting (no cookies) (on unless you switch it off): Vercel Web Analytics, plus PostHog in cookieless mode for page views and a few named product events. No analytics cookies or persistent visitor ID. A tab-only mode key keeps analytics in the correct mode on reload. There is no session recording or autocapture of page content. Neither the pages nor our server search events create a profile; visits are only grouped within a single day, never across days. We note the website you arrived from by its name only (such as google.com), plus the short source tag in the link (such as utm_source=newsletter), never the full address. Not fully anonymous: basic technical details (screen size, browser, language) are read, and your IP reaches the provider.
- Analytics (opt-in): PostHog and Google Analytics 4, including cookies, richer event data, and session recordings of the page (layout, clicks, scrolling, and visible text; typed inputs hidden). Analytics events are page views and named product events only, with no autocapture. Automatic error reports ($exception) are disabled entirely.
Outbound-click and search-failure events may include public venue slugs, so we know which venue link was tapped or which venue couldn't be checked.
Change your mind any time via in the footer, or see the cookie policy.
Error tracking
When something breaks in your browser, we note that it happened and which kind of page it happened on. (Technically: an error_boundary_caught event with the error name, a Next.js error digest, a bucketed route of /, /poll, /search, or /other, which error boundary fired, and the analytics mode — the boundary event never includes what you typed or searched for, the error message, stack trace, or any screen recording.)
When something breaks on our server, we note the kind of page it happened on. (Technically: a server_error event with the route pattern, error name, digest, and request method — no visitor ID, IP address, page address, error message, or what you searched for.)
Your searches carry a pseudonymous random search ID (search_id) so client, server, and hosting logs can be joined for debugging. It does not directly identify you, but it is joinable across those logs; analytics logs are kept around 90 days per the project's retention settings, then deleted or aggregated. Server events carry no IP address: we blank it before sending and keep GeoIP lookups off, though Vercel's edge servers necessarily see your IP and keep it under Vercel's own retention as our hosting processor. PostHog is configured to use its EU cloud host (eu.i.posthog.com).
We remember your choice for about six months (strictly necessary), plus a tab-only memory that stops analytics starting in the wrong mode while your choice loads. Object any time via in the footer, the Basic visit counting toggle, Global Privacy Control or Do Not Track, or by emailing hello@studiotom.co.uk.
Who we share data with
We use service providers to host and analyse the product, including Vercel (hosting and web analytics), Supabase (database), PostHog (product analytics; EU cloud where configured), Google (GA4, when you opt in), and Geoapify (place suggestions, and naming your area when you use your location). They only process data for us under their terms. We don’t sell your personal information.
Some providers may process data outside the UK. Where that happens we rely on appropriate safeguards such as the UK Extension to the EU-US Data Privacy Framework and/or standard contractual clauses, as offered by the provider.
How long we keep it
Venue requests are kept while useful for follow-up (manual retention; no automated deletion today). Correction emails are kept for up to 12 months, or longer if we need them for a legal claim. Poll data stays until the poll expires (about 14 days) or is closed, then a scheduled job removes it. Analytics retention follows each vendor’s project settings. Consent choices are stored for up to about six months, then we may ask again.
Your rights
You can ask for access, correction, deletion, restriction, objection, or data portability, and you can withdraw consent where we rely on it. Email hello@studiotom.co.uk. You can also complain to the Information Commissioner’s Office.
Children
The site is aimed at adults booking sports facilities. We don’t knowingly collect data from children.
Changes
We may update this page from time to time. The “last updated” date at the top will change when we do.