Legal
App Privacy Policy
The CricStats mobile app has no accounts and no advertising. It does one thing the
website cannot: it can send you a notification when a player you follow is close to
a landmark. That single feature is the only reason it holds anything about you at
all, and this page sets out exactly what that is.
Last revised
Applies to the CricStats mobile app (com.cricketverse.app)
The short version
There is no sign-up, no email address, no password and no advertising network. If you
never follow a player or a team, the app sends us nothing about you at all. If you do
follow someone and leave alerts on, we store one thing: an anonymous notification
token issued by your phone, and the list of players and teams you asked to be told
about. Turning alerts off deletes it. We do not sell or rent any of it.
1. What this policy covers
This page applies to the CricStats mobile app for Android and iOS,
distributed as com.cricketverse.app. The website at
cricstats.in is covered separately by the
site privacy policy, and the two are not
interchangeable — the app can hold something the website never does, which is why it
has its own page.
CricStats is an independent, fan-run cricket statistics project. It is not affiliated
with, endorsed by, or operated by the ICC, the BCCI, any national cricket board, any
franchise league or any team. In this policy "we" and "us" mean CricStats; "you"
means anyone using the app.
2. What the app collects
There is no registration, no login and no profile. Browsing scores, players, stats
and records sends us nothing beyond the ordinary web request described in
section 7.
One feature changes that. When you follow a player or a team and leave alerts
switched on, the app registers with us so we can reach you when the app is closed.
At that point, and only then, we store:
-
A notification token. A long random string issued by the push
service for your installation of the app. It is not your phone number, your
advertising ID, or any identifier you can be looked up by elsewhere. It is
explained in full in section 3.
-
Which platform you are on. The literal text "ios" or "android",
so the notification is delivered through the right service.
-
Who you follow. The names of the players and teams you chose,
because a notification about a landmark is meaningless unless we know whose
landmarks you asked for.
-
Your alert preferences. Which kinds of alert you switched on or
off.
-
Two timestamps. When the installation first registered and when
it last contacted us, so installations that have been deleted can be cleaned up.
We also keep a short record of which alerts have already been sent to your token.
Its only purpose is to stop the same notification arriving twice.
3. Notifications and your device token
To send a notification to a phone, every app needs a token from the operating system.
The CricStats app uses the Expo push service, which issues a token of the form
ExponentPushToken[…] for your particular installation.
Two things are worth being clear about, because a token of this kind is treated as a
device identifier under Google Play's rules and we would rather over-explain than
under-explain:
-
It identifies an installation, not a person. It carries no name,
email or phone number, it is not shared with the website, and it cannot be used
to look you up in any other service.
-
Because it is stable while the app stays installed, the list of players you
follow is attached to it. That pairing is the one piece of information the app
holds that could reasonably be described as being about you, and we use it for
nothing except deciding which notifications to send you.
Deleting the app, or turning alerts off inside it, ends this. See
section 9.
4. What stays on your phone
Some of what the app remembers never leaves your device and is never sent to us:
- cs-following
- The players and teams you follow, and whether you have been through the first-run screen. Held on your device so the app opens on your cricket rather than everyone's. A copy is sent to us only if alerts are on, as described above.
- cs-alerts
- Which alerts you have already seen or been notified about, so the app does not show you the same thing repeatedly. This list is capped and never leaves your phone.
Clearing the app's storage, or uninstalling it, removes all of this.
5. What we never collect
- No name, email address, password or account of any kind.
- No location. The app never asks for it and cannot read it.
- No contacts, photos, calendar, microphone or camera.
- No advertising identifier, and no advertising network — the app carries no ads.
-
No analytics, attribution or crash-reporting SDK. There is no third-party
measurement code in the app at all, which is unusual and deliberate.
-
No payment details. Nothing in the app is for sale and there are no in-app
purchases.
6. Who else sees it
We do not sell, rent or trade anything the app holds, and we do not share it for
anyone else's marketing. The only parties that necessarily see anything are the ones
that carry the notification to your phone:
-
Expo — receives the token and the text of a notification in
order to deliver it.
-
Apple (APNs) and Google (FCM) — the operating-system services
that perform the final delivery. This step is not optional for any app on either
platform.
-
Our hosting and database provider — stores the records described
above on our behalf.
Unlike the website, the app loads its typefaces from within the app itself, so it
makes no request to Google Fonts or any other font host.
We may also disclose information where we are legally required to, or where it is
necessary to investigate abuse of the service.
7. Server logs
The app fetches its cricket data from our servers, and like any web server ours
records the technical details of each request: the IP address it came from, the
request made, and the date and time. These exist so the service can be kept working
and defended against scrapers and abnormal request rates. We do not build behavioural
profiles from them and we do not try to work out who you are from them.
8. How long we keep it
- Notification registration
- For as long as alerts are switched on. Registrations that stop responding — which is what an uninstalled app looks like from our side — are removed during routine cleanup.
- Record of alerts already sent
- Kept only as long as it is needed to avoid sending you a duplicate.
- Server logs
- Kept for a short operational period and then discarded.
9. Turning it off and deleting your data
You are in control of the only thing we hold, and you do not need to contact us to
remove it:
-
Turn alerts off in the app. Open More → Alerts and
switch notifications off. The app tells our server to stop, and the registration
is disabled.
-
Unfollow everyone. With nothing followed there is nothing to
notify you about.
-
Uninstall the app. Everything held on your device goes with it,
and the registration on our side stops working and is cleaned up.
-
Ask us. Write to
cricstats.in@gmail.com and we will
delete the registration for your installation. Because there is no account,
please send the request from the device concerned or tell us enough to identify
the registration.
Depending on where you live you may have rights to access, correct, or object to the
handling of information about you. Given how little the app holds, the practical
answer to most such requests is deletion, which the steps above achieve immediately.
10. Google Play Data safety
For anyone comparing this page with the app's Data safety declaration on Google Play,
this is the same information stated in Google's categories:
- Device or other IDs
- Collected. The notification token, only when alerts are on. Used for app functionality — sending the notifications you asked for. Not shared for advertising. You can delete it from inside the app.
- App activity
- Collected. The list of players and teams you follow, and your alert preferences, only when alerts are on. Used for app functionality. Not shared for advertising.
- Location, personal info, financial info, messages, photos, contacts, files
- Not collected.
- Data encrypted in transit
- Yes.
- Data deletion
- Yes — see section 9.
11. Children
The app is a cricket statistics reference and is not directed at children. It has no
social features, no messaging, no user-generated content and no advertising. We do
not knowingly collect information from children. If you believe a child's information
has reached us, write to us and we will remove it.
12. Security
Traffic between the app and our servers is encrypted in transit. The records
described here are held on managed database infrastructure with restricted access.
No system is perfect, and we would rather say so plainly than claim otherwise; what
we can say is that the amount of information at stake has been kept deliberately
small, because the safest record is the one that was never collected.
13. Changes to this policy
If the app starts doing something this page does not describe, this page is updated
before that version ships, and the revision date at the top changes with it. We will
not quietly widen what is collected and leave the policy behind.