Who we are
CricketNow is a product of ULU Studio Ltd, company number 17259257, registered in England and Wales at Swan Building, 20 Swan Street, Manchester M4 5JW, and registered with the Information Commissioner's Office under number 00015215224. ULU Studio Ltd is the data controller for the personal information described here. Questions about this policy go to support@cricketnow.app. Safeguarding concerns go to safeguarding@cricketnow.app, or see Safeguarding.
This policy covers the CricketNow web app at cricketnow.app, the CricketNow mobile app, the CricketNow WhatsApp number, and this website.
Information we collect
Account details. Your name, email address, date of birth, profile details, uploaded profile images, notification preferences, and the security information needed to keep your account safe, such as password hashes and sign-in history.
Your cricket. Matches, innings, goals, reflections, highlights, equipment and profile details you log, and anything you import from your own Play-Cricket export. Imported records carry source identifiers and provenance so you and anyone you share with can see where a record came from.
Club information. If you join a club on CricketNow, the club's organisers see the membership details you give the club, such as your availability, team, fees and emergency contact. When club tools open, clubs will also record fixtures, selection and fee collection.
Guardian and junior details. A guardian who manages a junior profile gives us their own details and the junior's name and date of birth. We do not collect medical conditions or allergies.
WhatsApp. If you link WhatsApp, we store your phone number and the messages you send to the CricketNow number so we can log the match or answer the question they contain.
Payments. If you buy a subscription or pay a club through CricketNow, payment is handled by Stripe. We never see or store your full card number. We keep Stripe's customer and subscription identifiers, what was paid, and when.
Support and waitlist. Support tickets and their attachments, and the email address and country you give on the waitlist.
Technical data. IP address, device and browser type, app version, crash reports and diagnostic logs.
How we use information, and why we are allowed to
To run the service you signed up for (performance of a contract): providing your account, storing and showing your cricket, guardian oversight of junior accounts, club membership, notifications, subscriptions and support.
To keep the service safe and working (our legitimate interests): security, fraud prevention, rate limiting, audit logs, diagnostics, crash reporting and understanding how the product is used, always balanced against your privacy and never for advertising.
Where you have agreed (consent): linking WhatsApp, the optional participation insight below, and analytics cookies. You can withdraw consent at any time in Settings.
Where the law requires it (legal obligation): keeping payment records for tax purposes and responding to lawful requests.
We do not sell personal information and we do not use advertising or cross-site tracking.
Aggregated participation insight (optional). If you opt in, at sign-up or later in Settings, we may include your cricket in aggregated, anonymised statistics about participation (for example how many people played, how often, and where) that we share with governing bodies and leagues to help grow the game. We never share your name, your contact details or your individual record this way, and we never include junior accounts. This is off by default and you can switch it off at any time in Settings.
WhatsApp and the assistant
Messages to the CricketNow WhatsApp number travel through Meta's WhatsApp Business platform, which is subject to Meta's own terms. When you text a match in, or ask the assistant a question in the app or on WhatsApp, the text is sent to the AI provider we have selected, to be understood. That is one of OpenAI, Anthropic or Google, and the notice shown before you first use the assistant names which; if we change provider, we ask you again before anything is sent to the new one. The provider processes it on our behalf under its API terms. OpenAI and Anthropic do not train on it under those terms, and nor does Google on its paid Gemini API, which is the only way we use Gemini. The assistant can make mistakes; anything it logs appears in your record for you to check and correct.
While we are improving the assistant, we keep a copy of the messages you send it so we can see what it cannot answer yet. The notice shown before you first use it says when we do, and asks you again before we start. Kept messages are erased with your account, 30 days after you delete it (see How long we keep information).
Analytics and cookies
CricketNow uses cookies that are essential to sign you in and keep your session secure. These need no consent.
The web app also uses PostHog, hosted in the EU, to understand how the product is used. For adult accounts this includes session replay with every input and text field masked. Junior accounts are never included in analytics of any kind. If you would rather not be included, email support@cricketnow.app and we will exclude your account.
This website sets no cookies. Waitlist sign-ups and button clicks are sent to our own servers only.
Junior privacy
Players under 13 cannot self-register. Under-13 profiles must be created and managed by a parent or guardian. Players aged 13 to 17 can use protected junior accounts with additional privacy restrictions. Guardian-managed settings control who can view or follow protected profiles, and public sharing is restricted for under-18 accounts.
We design junior accounts to meet the ICO's Age Appropriate Design Code: private by default, no analytics, no public discovery, and no feature that nudges a young player towards sharing more.
Sharing and visibility
Matches, reflections and profile details are private unless you publish them or make them visible through your privacy settings. Public profile information, published feed items and shared passport links may be visible to other CricketNow users or public viewers depending on your settings. Club organisers see what you give the club, and nothing else.
Who we share information with
We share information only with the providers we need to run the service: hosting and database providers in the UK (DigitalOcean), an email delivery service (Brevo), crash reporting (Sentry, hosted in the EU) and analytics (PostHog, hosted in the EU), our payment processor (Stripe), the WhatsApp platform (Meta) and the AI provider behind the assistant (OpenAI, Anthropic or Google, whichever the assistant's notice names), and the app stores that distribute the mobile app. Each processes information on our instructions and for no other purpose.
Some of these providers are outside the UK. Where they are, we use the safeguards UK law requires for sending data abroad. We may also share information where the law requires it, or to protect a child or the safety of any person.
How long we keep information
We keep your account and your cricket for as long as your account is open. If you delete your account, it is disabled immediately and permanently purged 30 days later. The grace period is so an accidental or malicious deletion can be reversed by contacting support. After the purge, personal details are removed or anonymised; the small amount we must keep for legal, security or safeguarding reasons is kept only as long as that reason lasts. Payment records are kept for six years for tax purposes. Security and audit logs, which record who did what to an account, are kept for twelve months and then deleted.
Your rights and choices
You can update account, notification and privacy settings in CricketNow. You can download a copy of your account data from Settings, and request account deletion from Settings.
Under UK data protection law you also have the right to ask us for a copy of your information, to correct it, to delete it, to restrict or object to how we use it, and to receive it in a portable form. Email support@cricketnow.app and we will respond within one month. If you are unhappy with how we handle your information you can complain to the Information Commissioner's Office at ico.org.uk.
Security
Data is encrypted in transit and at rest, passwords are stored as hashes, access is limited to the people who need it, and every administrative action is logged. No service is perfectly secure, and if a breach affects you we will tell you and the ICO as the law requires.
Changes
When this policy changes in a way that matters, we will tell you by email or in the app before the change takes effect. The date at the top is the date of the current version.