Privacy Policy

This Privacy Policy explains what information Cricket Hub ("we", "us") handles when you use this website or the Cricket Hub Android app, why we handle it, who processes it, and the choices and rights you have. It applies to both the website and the app.

Who we are

Cricket Hub is an independent cricket information service — live scores, scorecards, fixtures, statistics, rankings and news — published as this website, with an Android app built from the same code. It is operated by an independent operator, who is the data controller for the information described in this policy. The operator's legal name and business address are available on request, and the contact routes in the "Contact and requests" section below are the working method for privacy questions, access requests and deletion requests: the contact form reaches the operator directly and is monitored for those requests.

Information we handle

• Account information. If you create an account, we handle the email address and name associated with your sign-in and your account role. If you sign in with Google, the provider passes us the basic profile details needed to create the account. Passwords are handled by our application platform's authentication service; we do not see or store your password.
• Your preferences and saved items. Teams, players and series you follow, articles you save, match reminders you set, and notification preferences — each stored against your account.
• Your display preferences. Theme and selected time zone are stored on your device (see "Storage on your device"), and a time zone you choose while signed in is also saved on your account so it follows you to other devices.
• Contact submissions. When you use our contact form we store the name, email address, enquiry category and message you submit so we can review and respond.
• Deletion requests. If you ask us to delete your account, we record a request with your email address, the verification method, a per-category deletion log and its status, so the request can be carried out and evidenced.
• Technical and security information. Like any hosted service, our hosting platform processes standard request information — IP address, browser or app version, requested page, timestamps and error details — to deliver pages, keep the service secure and diagnose faults.

Analytics

The app records two product events through our application platform's own analytics, which the platform processes on our behalf rather than through a third-party analytics service:

• match_page_viewed, when a Match Centre page is opened.
• article_read, when a news article is opened.

Each event carries the internal match or article identifier and is processed together with the context of the request — including the Cricket Hub account you are signed in with. These events are therefore not anonymous, and we do not treat the absence of a name in the event fields as anonymity. We use them to understand which pages and competitions are read.

A Google Analytics 4 integration is built into the app but stays inactive unless a measurement id is configured for the build and a consent mechanism has published a decision for that visitor; a refusal or a withdrawal keeps it inactive. In the configuration deployed now it is inactive, so no request is made to Google Analytics from your browser. If it is enabled later, this policy will say so; it would then send page views, event names and, for signed-in users, a user identifier to Google.

Advertising

Cricket Hub is designed to support itself through advertising served by Google AdSense. In the configuration currently deployed, the advertising library is not loaded: it is fetched only once a consent mechanism has published a decision for that visitor, so no advertising cookies are set and no advertising request is made from this site or from the app. A build setting is not accepted as consent, and a refusal or a later withdrawal keeps it off. (An earlier release loaded the AdSense library on every page regardless of consent; that is no longer the case.)

When advertising is enabled, Google may use cookies or similar technologies and device identifiers, and may process the page address and your IP address, to serve and measure advertising — including where no advertisement is visible. We do not control what Google collects in that process; Google's own privacy policy governs it. Non-personalised advertising is not treated as an exemption from consent, because the advertising library itself sets identifiers and processes request information.

Cookies and storage on your device

Our Cookie Policy lists each category. In summary, the browser or app stores:

• an authentication token, so you stay signed in;
• your theme, your chosen time zone and your recent searches;
• short-lived session state — the tab you came from and scroll position — so returning to a tab restores your view.

Cookies and similar technologies set by Google for advertising and, where configured, analytics are described in the Cookie Policy. You can clear or block them through your browser or device settings; blocking the authentication token signs you out.

Why we handle it, and who processes it

• To provide the service — running your account, saving your preferences and reminders, showing match and player pages.
• To respond to you — reviewing and answering contact submissions and deletion requests.
• To keep it working and secure — monitoring errors and traffic, preventing abuse.
• Advertising — supporting the service through advertising served by Google. This is switched off in the configuration deployed now, because no consent mechanism is in place.

Information is processed by:

• Base44 — the application platform that hosts this app, provides authentication, stores the data described above, processes the analytics events and delivers our emails.
• Google — advertising (AdSense) and Google Analytics 4, both inactive in the configuration currently deployed; Google also distributes the Android app and provides Google Fonts used by the interface.
• Third-party sports data providers — they supply cricket data to our servers. We do not send your personal information to them, and they do not set cookies in your browser through this service.

We do not sell your personal information to data brokers. We disclose it only to the processors above, or where we are legally required to.

International transfers

Our platform and advertising providers operate globally, so information may be processed outside your country. Those providers apply their own transfer safeguards; we do not publish a specific safeguard list for this deployment yet, so none is claimed here.

How long we keep it

• Followed teams, players and series, saved articles, reminders, notification preferences and a saved time zone are removed by the deletion process when you confirm a deletion request.
• The sign-in account itself — including your name, email address and account role — stays in place until an administrator removes it on our application platform as the final step of a deletion request. That step is completed within 30 days of your confirmation.
• Contact submissions are kept while the enquiry is open and for no longer than 24 months after it is closed, so the record of how it was handled remains available.
• Deletion request records are kept as evidence that a request was carried out for no longer than 24 months after the request is completed. They are not used for any other purpose.
• Platform analytics events (the two product events above, together with the metadata our hosting platform captures with them — country, browser, operating system and device type) are kept for 30 days on the plan this app runs on. That analytics history is separate from platform logs and backups.
• Platform backups and logs are kept by our hosting platform on its own cycle and are overwritten as that cycle rolls over. Deleted personal data is not restored from a backup.

The periods above are the operator's confirmed retention decisions, and each one is the maximum period that category is kept for: personal information is not held longer than the period stated for it.

Deleting your account and your data

You can delete your Cricket Hub account from the app (Account → Danger Zone → Delete Account) or from the public account deletion page, which works without installing or opening the app. Both routes create the same tracked request, verified against your signed-in session or a one-time link sent to your email address.

Deleting your account removes your preferences and saved items, your match reminders and notification preferences, the time zone saved on your account, and contact submissions made with the verified email address. Your account profile fields — name, email address and account role — and the sign-in account itself are not removed by that confirmation: they stay in place until an administrator removes the account on our application platform, which is the final step of the request. Public cricket records — players, matches, squads, competitions, standings and statistics — are separate from your account data: they are shared editorial content that every visitor reads, not records your account created, so deleting an account does not remove them. Until the final step is confirmed the request status reads "deletion request received" rather than complete. We then attempt to send a completion message to the address on the request, and whether that message was accepted is recorded: if it could not be delivered, the request says so and an administrator reaches the person another way rather than assuming they were told.

If the verified address cannot be matched to exactly one account, no account data is deleted: the request is kept for an administrator to resolve with the requester, and the page says so rather than reporting a completed deletion. Contact-form submissions made with the verified address are still removed in that case, because ownership of the address has been proven by then.

Your rights and choices

Depending on where you live, you may have the right to access, correct or delete the information we hold about you, to object to or restrict certain processing, and to withdraw consent where processing relies on it. Use the deletion page to erase your account, and the contact form for anything else — including asking for a copy of your information. You can also manage advertising and analytics cookies through your browser or device settings.

Security

Access to stored information is limited to authorised administrators, and information is transmitted over encrypted connections (HTTPS). No online service can guarantee absolute security, so we describe only what is in place and do not claim a guarantee.

Children

Cricket Hub is a general-audience cricket information service and is not directed at children. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us and we will delete it.

Changes to this policy

We update this policy when what we do changes — including before advertising, analytics or any new data practice is enabled. The effective date at the top of this page always reflects the current version.

Contact and requests

Privacy questions, access requests and complaints can be raised through our contact form, choosing "Legal or privacy request" as the reason. Account deletion is handled through the account deletion page or the in-app Account settings. Contact submissions are visible only to authorised administrators.

Operator details and retention

The operator's legal name and business address are available on request through the contact routes above. A dedicated privacy email address is not published: the contact form is the monitored route for privacy, access and deletion requests.

Retention periods for every category of personal information are stated under "How long we keep it" above, and each is a maximum.

The implementation state of this app — including whether advertising or Google Analytics is configured for a release build, and the limits of the account-removal process — is tracked on the operator's own administration page rather than in this policy.