CricApex
CricApex — Privacy Policy
Effective date: 30 September 2026
Applies to: the CricApex Android application, published as com.syedabdulkareem.cricapex, version 4.0 and later.
Published by: Syed Abdul Kareem
1. The short version
CricApex is a cricket scoring app. You need a CricApex account to use it. It is offline-first: once you are signed in, you can score entire matches with no internet connection, and CricApex backs up your cricket data to your account whenever you are online, so you can restore it on a new phone.
A few things are visible to other people: your public cricketer card (§5.2b), a match you choose to share live (§5.2c), and what you share when you connect with someone (§4.4).
- We do not show ads.
- We do not use analytics, tracking, advertising or crash-reporting software.
- We do not sell, rent or trade your data.
- We do not track you, profile you, or use your data to train anything.
- We do not collect your location, contacts, calendar, microphone or camera.
2. Who we are and how to contact us
CricApex is developed by an independent developer.
- Publisher: Syed Abdul Kareem
- Contact email: support@cricapex.com
- Website: https://cricapex.com
Please use the contact email for any privacy question, request or complaint.
3. Creating an account
An account is required. When you first open CricApex you are asked to create an account or sign in, and the app cannot be used without one. (Watching a match that someone has shared live does not need an account — see §5.2c.)
The only way to create or sign in to a CricApex account is with an email address and a password. CricApex does not currently offer Google sign-in, phone sign-in, or any other sign-in method.
Sign-in is handled by Google Firebase Authentication. When you register, your email address and password go directly to Firebase, which stores the password in hashed form. CricApex never sees, receives or stores your password.
4. What information CricApex holds
4.1 Your account and profile
| Data | Why | Required? |
|---|---|---|
| Email address | To create, sign in to and recover your account | Required |
| Password | To secure your account (held and hashed by Firebase) | Required |
| Display name | To identify you in the app and on scorecards | Required |
| CricApex ID (handle) | A short public identifier generated from your name, so other users can find you and you can share it as a link | Generated |
| Profile photo or avatar | To personalise your profile | Optional |
| Phone number | Kept on your own profile for your reference only. Never published to other users. | Optional |
4.2 The cricket data you create
- Teams — name, short name, colour, optional logo
- Players — name, role, batting and bowling style, optional photo, optional jersey number, optional phone number
- Matches — ball-by-ball records, scores, dismissals, extras, overs, results and Player of the Match
- Tournaments, career statistics, leaderboards, badges and season summaries
- App settings — theme, haptics, sound
- A record of matches you have deleted, so a deletion is not undone by a later sync
4.3 Information about other people
CricApex lets you add other players — including their name, photo and phone number — so you can score matches with them.
If you add another person's details, you are responsible for having their permission. Please add only information you are entitled to share. You can edit or delete any player in the app at any time.
4.4 Connections — please read this
CricApex lets you find other signed-in users by CricApex ID or name and send them a connection request. A connection is two-way: it exists only if both of you agree.
- Sending a request shares some of your details with that person. When you tap Connect, the other person receives your display name, CricApex ID and profile photo (if you have one), and can accept or decline. If they decline, the request is simply deleted; you are not told.
- When a request is accepted, a connection record is stored in the cloud for each of you (the other person's name, CricApex ID, photo and the date you connected). Each app also adds the other person's public cricketer card (§5.2b) to its player list, so their name and career statistics appear alongside your team.
- Connected people can see when the other is sharing a match live (§5.2c), and can open it.
- Removing a connection ends it for both of you. Your record and your copy of their card go straight away; the other person's app removes theirs the next time it checks.
4.5 What CricApex does not collect
CricApex does not collect your location, contacts, calendar, microphone, camera stream, device identifiers, advertising ID, or any usage analytics.
Photos are chosen by you through Android's own file picker. The app has no access to your photo library beyond the single file you pick, and requests no media permission.
App permissions. The installed app declares the following:
| Permission | Used by CricApex? |
|---|---|
INTERNET | Yes — for sign-in, cloud backup and live sharing |
USE_BIOMETRIC, USE_FINGERPRINT | No. These are added automatically by a Google sign-in library included in the app. CricApex contains no fingerprint or face-unlock feature and never asks for one. They do not give the app access to your biometric data. |
DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION | A standard internal Android permission added by the system libraries. It grants no access to your data. |
5. Where your information is stored
5.1 On your device
All your cricket data is stored on your device in the app's private storage, and is also backed up to your account in the cloud (§5.2a).
5.2 In the cloud
CricApex stores information with Google Firebase Realtime Database, in Google's asia-southeast1 (Singapore) region. It is kept in the following places, and nowhere else:
a) Your private backup — visible only to you Your profile, teams, players, matches, tournaments, settings and deletion records. Stored under your own account and readable only by your signed-in account. We have confirmed that one user's private backup cannot be read by another user.
b) Your public cricketer card — visible to every signed-in CricApex user So teammates can find you, CricApex publishes a small profile card containing exactly:
your CricApex ID, display name, profile photo or avatar, playing role, batting style, bowling style, and your career statistics
plus an internal identifier for your account and the time the card was last updated.
Who can see it: any person signed in to CricApex. It is not published to the general public or to anyone without an account.
Your email address and phone number are never included in this card, and neither are your matches. Please treat everything in the card as visible to all CricApex users. If you would rather not appear at all, you can delete your account (§8); CricApex cannot be used without one.
c) A live match snapshot — only if you choose to share a match live Live sharing is off by default and starts only when you tap to start it. While running, a snapshot of that match — team names, player names, scores, overs and ball-by-ball events, with an internal identifier for your account so that only you can change it — is published under a short watch code and can be read by anyone who has that code, with or without an account. Tapping Stop Sharing removes the snapshot straight away, and signing out stops it too. When a match finishes, its final scorecard stays viewable for about two hours after the last update, so people following it can see the result. After that the viewer stops showing it, and the snapshot is deleted the next time your app tidies up (for example when you next open it or sign out).
d) Your connections — visible only to the two people involved Connection requests you send or receive, and your accepted connections, as described in §4.4.
e) Your LIVE status — visible only to your connections While you are sharing a match live, a small record saying which match (its watch code and when it was last updated). Only people you are connected with, in both directions, can read it. It is removed when the broadcast stops.
f) The CricApex ID list — visible to signed-in users A list that links each CricApex ID to the internal identifier of the account that owns it, so that no two accounts share an ID and people can find you by yours. Your entry is released when you delete your account.
g) A deleted-account record — only after you delete your account When an account is deleted, CricApex keeps a record containing only that account's internal identifier and the time of deletion. It stops a phone that is still signed in to the deleted account from re-creating any of its data. It contains no name, email address or cricket data, no other user can read it, and it is kept indefinitely for this purpose.
6. Who your information is shared with
CricApex uses one third-party processor:
Google Firebase (Google LLC / Google Ireland Limited) provides the Authentication and Realtime Database services described above, as our service provider. Google's handling of this data is governed by its own terms: https://firebase.google.com/support/privacy
The app also loads the Firebase software library from Google's gstatic.com servers at startup. Apart from that library, Firebase's sign-in and database services, and our website cricapex.com (which shows a shared live match), CricApex contacts no other servers.
Other CricApex users see only what §4.4 and §5.2 describe. We do not share your data with anyone else. We do not sell it. We never transfer it for advertising purposes.
Anything you deliberately export or send yourself — a PDF scorecard, a share image, a live watch link — leaves the app at your direction and is then governed by whatever service you send it to.
7. How long information is kept
Your account, cloud backup, public card, connections and CricApex ID are kept for as long as your account exists. A shared live match is kept as described in §5.2c. The deleted-account record (§5.2g) is kept indefinitely. Data on your device stays until you delete it, sign out, clear the app's storage, or uninstall the app.
CricApex keeps no separate copy of your data outside the storage described in §5.
8. Deleting your account and data
You can delete your account inside the app: More → Settings → Account → Delete Account. You will be asked to confirm with your password.
When you confirm, CricApex:
- stops any live match you are sharing (including one started on another phone) and removes your LIVE status, and confirms both are gone;
- removes your connections and connection requests, including other people's records of their connection with you, and confirms they are gone;
- releases your CricApex ID;
- deletes your public cricketer card, and confirms it is gone;
- deletes your private cloud backup, and confirms it is gone;
- writes the deleted-account record (§5.2g);
- deletes your sign-in account from Firebase Authentication; and
- clears your cricket data from that device and signs you out.
Each cloud step is checked before the next one runs. If a step cannot be completed, CricApex stops there and deletes nothing further; you can still sign in, and trying again safely finishes the job. Deletion is immediate and cannot be undone.
What is not removed by this process
- A small amount of local app data remains on your device — your app settings and internal bookkeeping. It contains no account details. Safety copies of your cricket data also stay on the phone if CricApex ever made one: before a restore from a backup file, or of damaged data it set aside to protect it. Uninstalling the app removes everything.
- Data on other people's devices. If a teammate scored a match with you or added you as a player, that copy is part of their records, and we cannot delete another person's data. If you were connected, their app removes your card by itself once it sees your account is gone. The exception is a match they recorded that you played in: your name stays on that scorecard.
- The deleted-account record (§5.2g).
- Content you already exported or sent — PDFs, images and links you shared elsewhere.
- Provider backups and logs. Google may retain deleted data briefly in routine backups and logs under its own retention schedule.
Full instructions, including how to request deletion if you can no longer sign in, are here: https://cricapex.com/account-deletion
9. Security
- Communication with Firebase uses HTTPS/TLS encryption in transit.
- Data stored in Firebase is encrypted at rest by Google.
- Database security rules restrict your private backup to your own signed-in account. We have confirmed by testing that another user cannot read it.
- Passwords are handled and hashed by Firebase Authentication. We never see them.
No system is perfectly secure. Please use a strong, unique password and keep your device locked.
10. Your rights
You can see your data (it is all visible in the app), correct it, delete it (§8), export it (PDF scorecards and share images), and have CricApex stop holding it in the cloud by deleting your account (§8).
Depending on where you live — for example the EEA or UK under the GDPR, or India under the Digital Personal Data Protection Act — you may have further rights, including data portability and the right to complain to your data-protection authority. Contact us using the email in §2 and we will respond within 30 days.
11. Children
CricApex is a general-audience sports app and is not directed to children under 13. We do not knowingly collect personal information from a child under 13. If you believe a child has provided us with personal information, contact us and we will delete it.
Younger players' names may appear because an adult scorer added them to a team. If you add a child's details, please do so only with their parent's or guardian's permission, and consider leaving out their photo and phone number.
12. International transfers
Cloud data is stored in Google's Singapore (asia-southeast1) region. If you use CricApex from another country, your data is transferred to and stored there. Google maintains safeguards for such transfers as described in its own privacy documentation.
13. Changes to this policy
If we change this policy we will update the effective date at the top and publish the new version at this address. Where a change is significant, we will also say so in the app.
This version corrects the previous one (10 September 2026) to match how the app works today: an account is required; connecting is a two-way request that shares your name, CricApex ID and photo with the other person; connections can see when you are sharing a match live; and it lists every cloud record, including the CricApex ID list and the deleted-account record.
14. Contact
Email: support@cricapex.com
Publisher: Syed Abdul Kareem
Postal address: 57/198-10, Shastri Nagar, Akkayapalli, Kadapa (516003), Y.S.R Kadapa District, Andhra Pradesh, India