Cookies and Analytics Policy
Effective 17 November 2026, last updated 17 November 20261. About this policy
This policy explains the cookies, browser storage and analytics used on pavilion-cricket.com, on clubs' public Pavilion pages, and inside the signed-in Pavilion products. The Privacy Policy explains how Pavilion handles personal information more generally.
2. Cookies Pavilion sets
If you are not signed in, browsing the public website and public club pages does not set a Pavilion cookie. Pavilion sets these cookies when you sign in:
A session lasting 30 days does not guarantee 30 days of access. Your access is checked on every request, so it ends as soon as a session is signed out or a club removes you.
Signing in happens on pages provided by our sign-in provider, WorkOS, which can set its own cookies on those pages under WorkOS's own policies.
3. Analytics inside the signed-in product
PostHog loads only for a signed-in person inside the product. It records page views, an estimate of how long each page is actively in use, selected product events and how quickly pages load, using an internal ID rather than your name or email address. Session recording and automatic capture of clicks and typing are off, and query strings and IDs are removed from the addresses it records.
PostHog keeps that internal ID in a cookie and in your browser's storage on pavilion-cricket.com. We look at this information in aggregate.
4. Error reporting
Sentry receives reports of errors from the public website, and error and performance data from the signed-in product, with the same internal ID. Pavilion does not send it your name or email address, and Sentry does not set cookies for Pavilion.
5. Website analytics
Cloudflare delivers Pavilion and protects it, and runs Cloudflare Web Analytics on Pavilion's pages to count visits and measure page speed. Cloudflare Web Analytics does not use cookies.
6. Public club page counts
When a club makes its Archive+, calendar or club page public, Pavilion counts how those pages are used, for example how often player pages are opened or a fixture is added to a calendar. The counts are kept per club and per hour, and are not linked to you. Pavilion sets no cookie for them and keeps no identifier, IP address or search text with them.
7. Browser storage
Pavilion stores some preferences and working data in your browser's local storage, such as your colour theme, map and speaker choices, and unsaved work in some products. This stays on your device, and is not a cookie.
8. Maps and other services
Curator+ and some ground features load maps, aerial images and weather maps from the providers listed in the Privacy Policy. When they load in your browser, those providers receive your IP address and browser details, as with any website image.
9. Your choices
- You can block or delete cookies and browser storage in your browser settings. If you block the sign-in cookie, you cannot stay signed in to Pavilion.
- You can sign out at any time, and sign out your other sessions from your account page.
- Pavilion does not currently offer a setting to turn off analytics inside the signed-in product. Browser privacy settings and extensions can block analytics scripts, and Pavilion keeps working if they do.
10. Changes and contact
We will update this policy when the cookies, storage or analytics Pavilion uses change, and show the date of the change at the top of this page.
Questions: email [email protected] or use .