NOT OUT is an independent, fan-made cricket game. It is not affiliated with, endorsed by, or connected to the ICC or any cricket board. This page explains what data the site collects, why, and what choices you have.
If anything here is unclear, or you want to access, correct, or delete your data, email admin@not-out.co.uk.
The site is playable as a guest with no data collection beyond your device. Some features ask for more:
| Data | When | Where it's stored |
|---|---|---|
| A player name you type in | Guest play, submitting a score | Your device only (local storage), plus the Honours Board if you submit a score |
| Your Google account's display name and a unique account ID | Only if you choose to sign in with Google | Firebase Authentication (Google); attached to your Honours Board entries and Build Your Team data |
| Score, match record, format, and date | Whenever you submit a result | The public Honours Board (Firestore) — visible to every visitor |
| Team name, card collection, and campaign progress | Only if you use Build Your Team (requires sign-in) | A private record tied to your account (Firestore) — visible only to you |
| Basic usage data (pages viewed, device/browser type, approximate region) | Only if you accept analytics cookies | Google Analytics (GA4) |
| Last format played, cookie choice, a local leaderboard cache | Always, as you play | Your device only (local storage) — never sent to us |
Signing in is optional and only required for the Build Your Team mode. If you sign in, we receive your Google display name and a Firebase-issued account ID (not your Google password). This lets us verify a score or Build Your Team action really came from your account, and lets Build Your Team save your progress so it's there next time you visit. We don't request or store your email address for any of this.
Every score, series result, and pack opened is independently re-checked on our server before anything is saved — a signed-in identity only ever adds verification, it never changes what's visible about you beyond your chosen display name.
Anyone can submit a score, with or without signing in. Submitted entries — name, score, match record, format, and date — are public and visible to every visitor. If you were signed in when you submitted, your Firebase account ID is stored alongside the entry to prevent tampering; this ID is not displayed to other players and doesn't by itself reveal who you are.
This mode requires signing in so your collection can persist across visits and devices. Your team name, owned cards, and campaign progress are stored in a database record tied to your account. Firestore's access rules mean only you can read your own record — no other player or visitor can see it.
We use Google Analytics (GA4) to understand how the site is used in aggregate. In line with Google's Consent Mode, an analytics tag loads on every visit but starts in a denied state — no analytics cookies are set and nothing is linked to you personally until you actively accept. You'll see a banner on your first visit, and you can change your choice at any time via the "Cookie settings" link in the site footer.
We don't run ads and don't use any cross-site or third-party ad tracking.
The site runs on Google Firebase / Google Cloud Platform (database, authentication, and server functions) and is hosted via GitHub Pages. Google Analytics, when you've consented, is also operated by Google. We don't sell your data or share it with any advertiser.
Honours Board entries and Build Your Team collections are kept for as long as the site operates. There's currently no self-service "delete my data" button — email admin@not-out.co.uk with your player or team name (and roughly when you played) and we'll remove it.
Depending on where you live, you may have the right to access, correct, or delete the data we hold about you, and to object to how it's processed. Contact admin@not-out.co.uk for any of this. If you're in the UK or EU, you also have the right to complain to your local data protection authority (in the UK, the ICO).
NOT OUT isn't specifically directed at children, and we don't knowingly collect personal data from young children. If you believe a child has submitted personal data to the site, contact us and we'll remove it.
All traffic is served over HTTPS. Private data (like Build Your Team collections) is protected by database rules that restrict it to its owner, and every score or result is independently verified server-side before being stored. No method of storage or transmission is ever 100% secure, but we take reasonable steps to protect what we hold.
We may update this policy as the site changes. The "last updated" date at the top will reflect the latest revision — check back occasionally.