Idle Loop Gaming ("we", "us", "our") publishes Idle Cricket Club (the "Game"). This policy explains what data the Game collects, why, and who it is shared with. It covers the Game only.
If Idle Loop Gaming later publishes a studio-wide policy at idleloopgaming.com covering multiple titles, that page supersedes this document for this Game only once it explicitly names Idle Cricket Club and this document is updated to point to it. Until then, this document is the authoritative policy for the Game and is what is linked from the Game's Settings screen and store listings.
Summary
- The Game has no account system and no login—there is no username, password, or profile to create.
- Your club, squad, and progress are saved locally on your device. In addition, the Game automatically creates an anonymous, unlinked identity through Firebase Authentication for every install and periodically backs your save up to our Firestore database under that anonymous identity. This is not a login and does not currently let you restore that backup onto a different device.
- We use Firebase Analytics and Firebase Crashlytics (Google) to understand feature usage and diagnose crashes.
- In-app purchases are processed by Apple App Store / Google Play and managed through RevenueCat, which we use to validate receipts and track entitlements (for example, Manager Plus, Remove Ads, and Club Pass) across reinstalls on the same store account.
- The Game reads a small, static, non-personalised configuration file from a remote server at startup. It contains game-balance values only; nothing you enter is sent as part of that request.
- We use Google AdMob for banner advertising, currently being tested with a subset of players. We do not sell your data.
Data we collect and why
1. Gameplay data (device-local, plus an anonymous cloud backup)
Your club name, squad, facilities, season progress, purchases, and settings are saved to your device's local storage first. Using the in-app "Reset local save" option permanently erases the local copy. See "Cloud backup" below for the separate, anonymous backup copy we additionally keep.
2. Cloud backup—Firebase Authentication and Firestore (Google)
The Game automatically signs you in to an anonymous Firebase identity on first launch. This happens silently, with no username, password, email, or sign-in screen involved, and is not a user account in the normal sense. Your gameplay save (the same data described in section 1) is then periodically backed up to our Firestore database, tied only to that anonymous identity.
This exists as a safety net if the app is uninstalled or the device is lost. It does notcurrently let you restore your save on a different device or after an Android reinstall, since the anonymous identity itself is device-bound on Android. It does persist across an iOS reinstall through the device's Keychain. We do not currently offer a Google or Apple sign-in option to link this backup to a portable account. Each player's backup is stored separately and is readable and writable only by that player's own anonymous identity.
3. Analytics—Firebase Analytics (Google)
We use Firebase Analytics to understand how the Game is used in aggregate: which screens are opened, which features are used, and general engagement and retention trends. This is identified by a Google-generated, app-specific installation/analytics identifier—not by your name, email, or any account, since the Game has none. See Google's Firebase privacy and security documentation for how Google processes this data on our behalf.
4. Crash and stability reporting—Firebase Crashlytics (Google)
If the Game crashes or encounters certain errors, Crashlytics automatically collects a crash report (stack trace, device model, OS version, and app version) to help us fix the issue. This may include your device's IP address as part of standard network transmission, and a Crashlytics-generated installation identifier. It does not include your gameplay save data or anything you have typed.
5. Purchases—Apple/Google and RevenueCat
If you make an in-app purchase, the transaction itself is handled entirely by the Apple App Store or Google Play—we never see or store your payment details (card numbers, billing address, and so on). We use RevenueCatto validate purchase receipts with Apple/Google and keep track of which entitlements (for example, Manager Plus, Remove Ads, an active Club Pass, or an unlimited-match pass) belong to your store account, so they can be restored if you reinstall or switch devices while keeping the same App Store/Google Play account. RevenueCat receives a store-generated purchase receipt and an app-specific user identifier—not your name, email, or payment details. See RevenueCat's privacy policy for how it processes this data on our behalf.
6. Remote configuration
At startup, the Game fetches a small static JSON file from a remote server to pick up balance/config tuning (for example, offer parameters). This is a read-only fetch of a public file—no personal or gameplay data is sent as part of that request.
7. Advertising—Google AdMob
The Game uses Google AdMobfor banner advertising. This is currently being rolled out gradually as an A/B test, so it may or may not be active for you depending on your device and a randomly assigned test group. A remote kill switch can also disable it entirely at any time. When a banner ad is shown, AdMob may process advertising/device identifiers to select and measure ads, under Google's AdMob data disclosure. We do not control what AdMob itself collects for ad delivery and measurement beyond integrating its SDK as documented there.
Separately, "watch an ad" prompts you may see elsewhere in the Game are rewarded ads. The same AdMob SDK is integrated and technically capable of showing these, but every rewarded placement is currently switched off in production. Those prompts still run a simulated reward flow with no ad vendor involved for now. If we turn on real rewarded ads, this section will be updated first.
Who we share data with
We share the data described above only with the service providers named above, each acting as a data processor for the specific purpose listed:
- Google (Firebase Authentication, Firestore, Firebase Analytics, Firebase Crashlytics, and AdMob)
- RevenueCat (purchase and entitlement management)
- Apple / Google, as the store operators processing your purchase
We do not sell your data, and we do not share it with data brokers or for third-party advertising purposes.
Children's privacy
The Game is intended for a general audience and is not directed at children under 13 (or the equivalent minimum age in your region). We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us using the details below and we will address it.
Your choices
- Restore purchases:available from the Game's Settings screen.
- Delete your local data:use "Reset local save" in Settings, or uninstall the Game—either permanently erases your on-device save.
- Delete your cloud backup: because it is tied to an anonymous identity with no login, there is no in-app control for this yet. Follow our data-deletion instructions to request removal.
- Analytics/crash data:this is tied to an app-install identifier, not an account, so there is no login-based dashboard to manage it from. Contact us at the address below for a deletion or access request and we will act on it via Firebase's tooling.
- Purchase history: your purchase/receipt history is retained by Apple/Google and RevenueCat under their own retention policies. Contact RevenueCat or the relevant store for a copy or deletion of that record.
Data retention
Firebase Analytics and Crashlytics events are retained under Google's default Firebase retention settings. Your Firestore cloud backup is retained until you request deletion or your anonymous identity is removed. RevenueCat retains purchase and entitlement records for as long as needed to support purchase restoration and support requests.
Security
We rely on the security practices of Google (Firebase and AdMob), RevenueCat, and Apple/Google (App Store/Google Play) for the data those services process on our behalf. Firestore access is restricted so each player's cloud backup is only readable and writable by that player's own anonymous identity. Local save data is protected by your device's own OS-level app sandboxing.
Changes to this policy
We may update this policy as the Game changes (for example, if we add an advertising SDK or a cloud-save feature). We will update the effective date above when we do. Material changes affecting active players will be reflected here ahead of the change going live.
Contact us
Questions, privacy requests, or concerns: support@idleloopgaming.com.