Privacy Policy
Effective date: 6 August 2026
This document is a plain-language template, not legal advice. It was drafted from the app's actual data-collection code and SDKs, but has not been reviewed by a lawyer. Have it checked against GDPR/CCPA/local requirements before relying on it for a store submission.
Gully Cricket Scorer ("the App", "we", "us") is a scoring app for informal street and gully cricket. This policy explains what data the App collects, why, and what choices you have. It applies to the App and this website.
1. Who this applies to
Anyone who downloads, installs, or uses Gully Cricket Scorer, or who is added as a player/team member by another user of the App.
2. Data we collect
We only collect what the App needs to function. Nothing is collected for advertising, and we do not run any advertising or analytics SDK beyond the crash-diagnostics tool listed below.
| Data type | What it's for | Sent off your device? |
|---|---|---|
| Email address & password | Account creation and sign-in (Firebase Authentication) | Yes |
| Google account (name, email, profile photo) | Optional "Sign in with Google" (Android only) | Yes |
| Phone number, name, date of birth, gender, country | Your player profile | Yes — stored in an owner-only, access-restricted profile record |
| Profile photo | Personalising your profile and team sheets | Yes |
| Contacts (name & phone number, read-only) | Finding friends who already use the App, so you can add them to a team | Read on-device to match against existing users; not bulk-uploaded or retained as a contact list |
| Location (one-shot, coarse or precise) | Tagging the venue of a match you create | Yes — stored as a venue name/description, not continuous or background tracking |
| Match, team, and player data (scores, ball-by-ball history, scorecards) | Core scoring functionality and shared scorecards | Yes |
| Push notification token (FCM) | Sending you match/scoring notifications | Yes — cleared when you sign out |
| Crash logs, stack traces, device model & OS version | Diagnosing crashes and stability issues (Firebase Crashlytics) | Yes — disabled during development/debug builds |
| Biometric unlock flag (Face ID / fingerprint) | Optional local app-lock | No — stays on your device only |
3. Who we share data with
We do not sell your data or share it with advertisers. The only third parties involved are the infrastructure providers that run the App on our behalf, acting as data processors:
- Google Firebase (Authentication, Firestore database, Cloud Messaging, Crashlytics) — hosts your account and app data.
- Google Sign-In — only if you choose to sign in with a Google account (Android).
Other users of the App can see data you choose to share with them — e.g. teammates and opponents can see match scorecards you're part of, and friends you add can see your profile.
4. Retention
We keep your data for as long as your account is active. One exception worth calling out clearly: match records you've scored or been part of are retained even after you delete your account, so that other players in that match keep an accurate shared scorecard. Your personal profile, login credentials, and identity links are removed on deletion — see Section 6.
5. Your choices
- Contacts and location are only requested when you use a feature that needs them, and the OS will ask your permission first. You can decline and keep using the rest of the App.
- Data export: email dsrigyan.app@gmail.com from your registered address to request a copy of your data.
- Account deletion: see the Data Deletion page for the in-app flow and the no-app-access alternative.
6. Deleting your account
You can delete your account at any time from Profile → Account Settings inside the App. This permanently removes your profile, private data, and identity links. Full step-by-step instructions, and what's retained, are on the Data Deletion page.
7. Children's privacy
Gully Cricket Scorer is not directed at children under 13, and we do not knowingly collect data from children under 13. If you believe a child has provided us data, contact us and we'll remove it.
8. Security
Sensitive profile fields (phone, date of birth, etc.) are stored in access-restricted records that only you can read. We use industry-standard transport encryption (HTTPS/TLS) for all data in transit.
9. Changes to this policy
If we make material changes, we'll update the effective date above and, where required, notify you in the App.
10. Contact us
Questions about this policy or your data: dsrigyan.app@gmail.com