Privacy Policy
Effective date: 7 August 2026 · Last updated: 4 November 2026
This policy describes how the App actually handles data. It has not been reviewed by a solicitor — worth doing before relying on it for a store submission.
This policy explains what information Gully Cricket ("the App", "we", "us") collects, why, how it is stored and shared, and what rights you have over it. It applies to the mobile app, this website, and the services behind them.
It is written to describe what the App actually does. If something here doesn't match the App's behaviour, that's a fault in this document — please tell us.
1. Who we are
| Data controller | We Ingenious |
|---|---|
| Based in | United Kingdom |
| Contact | [email protected] |
We are the "controller" of your personal data under the UK GDPR and the Data Protection Act 2018 — meaning we decide what data is collected and why. We have not appointed a Data Protection Officer, as we are not required to.
2. What we collect
We collect only what the App needs to work. Only if you allow it, we use Firebase Analytics to understand how the App is used — how many people finish setting up a match, which features are reached, where people give up. It is off until you say yes: the App asks once, and you can change your answer at any time in Settings → App Permissions → Usage data (turning it off also clears what is held on your device). These are counts of actions, not records of you: no advertising SDKs, no ad networks, no cross-app tracking, no Mixpanel, no Amplitude, no Meta SDK. We do not sell your data to anyone, in any jurisdiction, and never have.
| Data | Why | Stored off your device? |
|---|---|---|
| Email address, and a password (hashed by Firebase — we never see it) | Account creation, sign-in, recovery | Yes |
| Google account details, if you use "Sign in with Google" | Alternative sign-in | Yes |
| Display name, Cricket ID (@handle), permanent numeric CricID | Your identity across matches; how friends find you. If you change your Cricket ID, the earlier one stays linked to you — your earlier matches are recorded under it — so nobody else can choose it, and you can switch back to it | Yes |
| Date of birth, gender (optional) | Your profile | Yes — in a restricted record only you can read |
| Phone number (optional) | Lets friends who already have your number find you. It is never a way to sign in. We text it a code first to check it is yours | Yes — in a restricted record only you can read. Friend search stores only a scrambled (hashed) form of it |
| Phone check records — the one-use request for each code, a record that a code was used, and daily counts of codes sent | Making sure one code checks one number once, limiting how many codes are sent, and stopping abuse | Yes — deleted after 30 days |
| Profile photo (optional) | Personalising your profile and team sheets | Yes |
| Location — a one-time fix, converted to a place name on your device (optional) | Filling in place names for you: your city and country on your profile, and the town of a new ground you name in match setup (shown there, and you can clear it) | Only the resulting place name (e.g. "Leeds, UK"). Raw GPS coordinates are never stored. No background or continuous tracking. |
| Contacts — the name, phone number and email of the contacts you pick (optional) | Finding friends who already use the App | Each number you pick is looked up on our server in a scrambled (hashed) form, never as the number itself. The contacts you add are saved to your own private friends list, readable only by you; a friend you put in a saved team keeps their number in that team, which is also yours alone. Your full address book is never uploaded. |
| Match data — scores, ball-by-ball history, player names, statistics | The core function of the App | Yes — see Section 5 on visibility |
| Push notification token | Match invites, scoring handoff requests, results | Yes — deleted when you sign out |
| Crash reports — error, stack trace, app version, device model, OS version, screen | Diagnosing and fixing crashes | Yes — tied to a non-reversible identifier, not your account ID. Disabled in development builds. |
| Bug reports and feedback you send us — the name you type, your message, and the app version, device model and OS version; plus a crash report or recent log entries if you choose to attach them | Investigating and fixing what you report | Yes — stored with your account ID, and also emailed to us through a third party (see Section 4) |
| Biometric unlock preference | Optional app lock | No. Fingerprint and face matching happen entirely within your device's operating system; we receive only a yes/no result and never any biometric data. |
Phone numbers are never used to sign in. Mobile networks give unused numbers to new customers, so a text code could let a stranger into your account. You sign in with Google or an email address instead. If you add a phone number to your profile, we text it a code to check it is yours. That check runs in a separate Google Firebase project which cannot open any account; once the code is confirmed, our server saves the number on your profile.
If someone else later checks a number that is on your profile — for example, because your network gave your old number to them — the number is removed from your profile and you are told in the App. Nothing else about your account changes, and they are never shown who you are. We keep a record of the move (which accounts, a scrambled form of the number, and when) for 2 years, so a mistake can be investigated.
3. Our lawful basis for using it
Under UK GDPR we must have a lawful basis for each purpose. Ours are:
| Purpose | Lawful basis |
|---|---|
| Creating your account and providing scoring, teams, and scorecards | Contract — necessary to deliver the service you asked for |
| Optional profile details, contacts access, location, notifications | Consent — you choose these, and can withdraw at any time |
| Keeping shared match records complete after an account is deleted, including who created, scored and recorded each match (Section 9) | Legitimate interests — other players rely on those records, and on knowing who recorded what if a result is questioned; what we keep is minimal and no longer leads to an account |
| Checking phone numbers, limiting text codes, and recording when a number moves between accounts | Legitimate interests — preventing abuse of the text-code service and keeping friend search accurate, using the minimum data (a scrambled form of the number wherever the number itself is not needed) |
| Crash diagnostics, security, and preventing abuse | Legitimate interests — keeping the App working and secure, balanced against your privacy (the data is minimal and pseudonymised) |
| Responding to lawful requests | Legal obligation |
Where we rely on consent, withdrawing it is straightforward: revoke the permission in your device settings, or clear the optional field in your profile. Withdrawing consent doesn't affect processing already carried out.
We do not carry out automated decision-making or profiling that produces legal or similarly significant effects.
4. Who we share it with
We do not sell your personal data, and we do not share it with advertisers or data brokers. Data is shared only with the infrastructure providers that run the App on our behalf ("processors"), who may act only on our instructions:
| Provider | What they handle |
|---|---|
| Google Firebase | Authentication, Firestore database, Cloud Storage, Cloud Messaging, Crashlytics, App Check, Cloud Functions, and Identity Platform — which sends the text code that checks a phone number |
| Supabase | Long-term archive of historical ball-by-ball match data, moved out of the live database once a match is complete |
| EmailJS | Delivering the bug reports and feedback you submit in the App to our support inbox. The name and message you type pass through, and are retained in that provider's own sending history as well as in our inbox |
| Cloudflare | Serving this website |
We may also disclose information where required by law, or to protect the rights, safety, or property of our users or the public.
5. Match data is shared by design
This is the most important thing to understand about the App, so we'll be plain about it.
Cricket scoring is inherently a shared record. A match involves batters, bowlers, a scorer, and spectators. Match data — including player names, scores, and statistics — is visible to everyone taking part in that match, and to anyone the scorer shares the scorecard or a live-score link with. Shared scorecards can be viewed without signing in.
In practice:
- Your name and playing statistics in a match are visible to other participants and to anyone given the scorecard.
- Your contact details are not part of that shared record — phone number, email, and date of birth stay in a restricted profile record only you can read.
- Your profile photo is visible to other signed-in users, not to the general public.
6. Information about other people
The App lets you enter details about other people — teammates' and opponents' names, and how they performed in a match you're scoring. If you do that, you're responsible for having a proper reason to, such as being the designated scorer for a real match they're playing in.
If someone has recorded information about you and you'd like it corrected or removed, contact us at [email protected]. You have the same rights over that data as anyone else, whether or not you have an account.
7. Where your data is stored
Our infrastructure providers operate globally, so your data may be stored or processed outside the United Kingdom, including in the United States.
Where data leaves the UK or EEA, it is protected by the safeguards required under UK GDPR — the UK International Data Transfer Agreement or Addendum, or the EU Standard Contractual Clauses, as incorporated into our providers' data processing terms. You can request more detail using the contact address above.
8. How long we keep it
| Data | Retention |
|---|---|
| Account, profile, and identity records | Until 30 days after you delete your account (see Section 9) |
| A guest account (one with no email or Google sign-in) | Kept while it is used. If it is not opened for 12 months it is switched off, and deleted 30 days later. Matches it scored stay, so the other players keep their scorecards. |
| Friends list, saved teams, scheduled matches | Until you delete them, or 30 days after you delete your account |
| Push notification token | Cleared when you sign out |
| Ball-by-ball match detail | Held in the live database, then moved to long-term archive storage once the match is complete |
| Match records and scorecards | Retained after account deletion, with your Cricket ID and an internal account code on them — see Section 9 |
| Crash reports | Per Firebase Crashlytics' standard retention (up to 90 days) |
| Crash details and logs attached to a bug report | 90 days, then removed automatically — unless we are still investigating that report |
| Bug reports and feedback you send us | 12 months, then deleted automatically (the copy that passes through EmailJS is subject to that provider's own retention) |
| Phone check records (one-use code requests, used checks, daily counts) | 30 days, then deleted automatically |
| Administrative audit log — for example, a change to an administrator's role, or a phone number moving between accounts | 2 years, then deleted automatically |
9. Deleting your account
You can delete your account at any time in the App: tap your photo on Home, then Delete account at the foot of Settings (confirming your password, if your account has one). Your account is switched off immediately and hidden from other users, and permanently deleted 30 days later. Until then you can recover it by creating an account again with the same email address, or continuing with the same Google account — the App then offers your old account back: choose Get my old account back; you may instead choose to start a new account, and the old one is still deleted on schedule. To make recovery possible we keep the email address of a deleted account for those 30 days, in a record no other user can see; it is removed with the account. A guest account has no email address or Google account, so it cannot be recovered, and is also deleted after 30 days. A phone number on a deleted account stops being findable at once; if someone else checks that number in the meantime, it is theirs, and recovering the account does not take it back. If you no longer have the App, email us and we'll complete the deletion within 30 days. Full instructions are on the Data Deletion page.
Deleted after the 30 days: your profile and contact details, login credentials, profile photo, friends list, saved teams, scheduled matches, notifications, career statistics, your entries in other users' friends lists, and the link from your Cricket ID and CricID to your account. Your Cricket ID is never given to anyone else: the match records kept under it stay yours alone.
Retained: matches you scored or played in are not deleted, because they are shared records other participants rely on for their own scorecards and statistics — a cricket match doesn't belong to one player alone. They are kept as they were recorded on the day, which means they still include:
- the player record you were linked to: the name shown on it, your Cricket ID, and an internal account code (a random string, not your name, email or phone number) that linked it to your account;
- that same code where a match records who created it, who scored it or handed over scoring, who recorded each delivery (with a code for the device used), who approved a rain revision, and who was on a team sheet.
After deletion that code no longer leads to an account, and your contact details, photo and login are not kept with it. You can ask us to remove your Cricket ID and account code from these records — email us, and we will, unless we need them to deal with a dispute about a match. If you want a specific match record removed altogether, contact us and we'll consider it (for example where you were the only participant, or where everyone involved agrees).
10. Your rights
Under UK GDPR you have the right to:
- Access — get a copy of the personal data we hold about you
- Rectification — have inaccurate data corrected
- Erasure — have your data deleted (subject to Section 9 on shared match records)
- Restriction — ask us to limit how we use your data
- Portability — receive your data in a machine-readable format, or have it sent to another provider
- Object — object to processing based on legitimate interests
- Withdraw consent — at any time, where consent is the basis
To exercise any of these, email [email protected]. We'll respond within one month. There's no charge, unless a request is manifestly unfounded or excessive.
Complaints: if you're unhappy with how we've handled your data, you can complain to the UK's Information Commissioner's Office — ico.org.uk/make-a-complaint, or 0303 123 1113. We'd appreciate the chance to put things right first.
11. If you're outside the UK
European Economic Area
We apply the same standards under the EU GDPR. You may complain to your national supervisory authority.
California
Under the CCPA/CPRA you may request access to, deletion of, or correction of your personal information, and you have the right not to be discriminated against for exercising those rights. We do not sell or share personal information as those terms are defined under California law, and have not done so in the preceding 12 months.
India
Under the Digital Personal Data Protection Act 2023 you may access, correct, and erase your personal data, nominate someone to exercise your rights on your behalf, and raise a grievance using the contact address above.
Everywhere else
We apply the rights described in Section 10 to all users, wherever you live. Contact us and we'll help.
12. Security
Data is encrypted in transit (HTTPS/TLS) and at rest by our infrastructure providers. Access to the database is governed by server-side security rules determining who can read and write each record — only you can edit your own profile. A match's score is changed only by its scorer while it is played; once finished, by the person who created it (for 7 days) or the scorer who finished it (for 24 hours), and by our Platform Admins to correct mistakes. Passwords are handled entirely by Firebase Authentication; we never store or see them.
No system is perfectly secure. If you believe you've found a vulnerability, please email us directly rather than disclosing it publicly, and we'll fix it.
13. Children
The App is not directed at children under 13, and we do not knowingly collect personal data from them. If you believe a child under 13 has provided us data, contact us and we'll delete it.
Date of birth is an optional profile field and is not currently used to verify age.
14. Changes to this policy
We may update this policy. Material changes will be reflected in the "Last updated" date above, and the App will ask you to accept the updated version before you continue.
15. Contact
Questions about this policy, or to exercise any right described above: [email protected]