Privacy Policy

CCStats ("we", "us") is a stats platform for cricket clubs. This page explains what personal data we collect, why, and what rights you have over it. If anything here isn't clear, email tomwylie6@gmail.com and we'll sort it out.

Who processes what

There are two kinds of personal data on CCStats, and they work differently:

• Your account & billing details (email, password, payment info) — here, CCStats is the data controller. We decide how this is used, and this policy is written from that position.
• Player names and match stats that a club enters or imports — here, the club is the data controller and CCStats is a data processor acting on their instructions. If you're a player and want stats about you changed or removed, the fastest route is asking your club's admin — we'll also action any request sent to us directly.

What we collect

• Account info — email address and password (stored as a one-way hash we can never read back), handled entirely by our authentication provider, Supabase.
• Club data you enter — club name, colours, badge image, and any player names, roles, and match performances a club's admin adds, either by hand or via PlayHQ import.
• Billing info — plan, billing period, and subscription status. Card details are entered directly into Stripe's own checkout — we never see or store your card number.
• Migration requests — if you tick the "I have old stats I'd like migrated" box at signup, whatever you type into that box, so we can follow up.
• Session cookies — used only to keep you logged in. We don't use analytics or advertising cookies.

Why we process it

• To run the service you've signed up for — this is processing under contract.
• To take payment and manage your subscription, via Stripe.
• To respond to support or data-migration requests you send us.
• To keep the service secure and working as intended — our legitimate interest in running a functioning product.

Who we share it with

We use a small number of processors to run CCStats, and don't sell or share your data beyond them:

• Supabase — database, authentication, and file storage (club badges, sponsor logos).
• Vercel — hosting for the website itself.
• Stripe — payment processing and subscription billing.
• PlayHQ — when a club chooses to import a scorecard, we fetch that game's public data from PlayHQ's own site.

Where it's stored

Our database and file storage are hosted in the UK (London). We don't transfer your data outside the UK/EU.

How long we keep it

We keep club and account data for as long as your subscription is active. If a subscription lapses, your club's public page is hidden but the data itself isn't deleted, so nothing is lost if you renew later. If you'd like your club's data permanently deleted instead, email us and we'll do it.

Your rights

Under UK GDPR, you can ask us to:

• Give you a copy of the personal data we hold about you.
• Correct anything that's inaccurate.
• Delete your data (subject to what we need to keep for legal/billing reasons).
• Restrict or object to how we're using it.
• Move it to another provider.

Email tomwylie6@gmail.com for any of these. You can also complain to the Information Commissioner's Office if you think we've got something wrong.

Junior players

Some clubs track junior sides. Clubs are responsible for having a proper basis to publish any player's data, including under-18s, and for handling any request to remove a young player's stats from their page. Get in touch with us directly if a club isn't responsive and we'll help.

Changes to this policy

If this policy changes in a meaningful way, we'll update the date at the top of this page.