Cookie policy

1. What a cookie is

A cookie is a small file a website asks your browser to keep. It comes back with your next request, which is how a site remembers that you are the same person who logged in a minute ago.

Some sites use cookies to follow people between sites and build an advertising profile. We do not. What we do set is either required for the site to function, stored purely on your own device, or used to measure how this marketing site is performing - and that last kind runs on our own pages only, never on a venue's booking page.

2. What we set

Strictly necessary cookies

• Session cookie. Identifies your browsing session so a signed-in venue admin stays signed in, and so a half-finished booking form survives a page change. Expires when you close the browser or after a period of inactivity.
• CSRF token. A random value tied to your session, checked on every form submission. It is what stops another site from submitting a booking or a settings change on your behalf without you knowing.

These cannot be switched off. Without them you cannot log in and cannot submit a booking, because every submission would be rejected as untrusted. Under most consent rules, strictly necessary cookies do not require a banner, which is why you have not seen one.

Local storage, not a cookie

• Theme preference. If you switch between light and dark mode, that choice is written to your browser's local storage so the next page does not flash the wrong colour. It never leaves your device and is never sent to our servers.

Analytics

• Google Tag Manager. Our own pages load Google Tag Manager. It is a container for measurement tags rather than a tag itself, and we use it to see how people find and move through this site - which pages get read, which get skipped. Depending on what is configured inside the container, the tags it loads may set cookies on Google domains, and will receive your IP address, browser type and the pages you visit.

This runs on ReadyCourt's own marketing pages, and on the booking tracker when you open it here at readycourt.com. It is deliberately not loaded on a venue's booking page, on a venue's own custom domain, or anywhere inside a venue's admin. If you are booking a court, you are not being measured by us.

3. What we don't set

• No advertising or retargeting tags are configured
• No behavioural profiling, and no analytics of any kind on a venue's own pages
• No social media tracking pixels
• No cross-site identifiers, and nothing sold or shared with data brokers

We load two fonts from Google Fonts, which means your browser makes a request to Google's servers when a page loads. That request carries your IP address and browser type, as any request does, but sets no cookie and is not used by us for tracking.

A venue that connects its own custom domain does not gain any additional tracking, and does not inherit ours either: the analytics described above stop at our own pages. A venue's booking page sets only the strictly necessary cookies listed in section 2.

4. Your control

Every browser lets you view and delete cookies, usually under Settings then Privacy. You can block cookies entirely, but you will not be able to log in or complete a booking, because the security token has nowhere to live.

Clearing local storage resets your light or dark preference and nothing else.

5. Contact

Questions about this policy: support.readycourt@gmail.com. How we handle personal data more broadly is covered in the privacy policy.

Last updated: 25 October 2026