scoreCF

1. Introduction

This Privacy Policy explains how Innings Studio (“we,” “us,” or “our”), operating via inningsstudio.com, collects, uses, and shares information when you use the scoreCF mobile application (“scoreCF,” “App”) on Android or iOS. scoreCF is listed on Google Play under the store title “LiveScore & Prediction” and was previously published as My11Stats — this Policy applies to the App under either name. Questions: hello.inningsstudio@gmail.com.

2. Information we collect

No account required. scoreCF is built to browse cricket and football schedules, fixtures, live scores, stats and AI-assisted predictions served from our backends. The App does not have a sign-in or account system of any kind, and we do not intend to collect your name or email through normal use.

Automatic diagnostics and analytics (Android). When you open the App on Android, your device communicates with Firebase components that may automatically process:

• Crash reports: Firebase Crashlytics collects crash stacks and debug context (for example anonymized identifiers and metadata about the failing session) so we can fix bugs.
• Analytics: Firebase Analytics gathers aggregated usage counts and in-app navigation events (such as which match, list or screen you opened) so we can improve usability. This collection is switched off in development/debug builds of the App.

Performance and configuration (Android and iOS). Firebase Performance Monitoring measures app speed and reliability, and Firebase Remote Config delivers feature and configuration flags (for example enabling football coverage, update prompts, and advertising settings described below) — both may process basic device and app-version signals.

Match and content requests (Android and iOS). The App retrieves match-centric documents (fixtures, live scores, scorecards, standings, news) via Firebase Firestore and Firebase Realtime Database. Typical automatic data includes request metadata your device transmits (network addresses, timestamps, HTTPS headers) handled by Google according to Firebase’s documentation.

Advertising (Android currently). scoreCF displays advertising served by Google AdMob (the Google Mobile Ads SDK), including banner, interstitial, rewarded-video and native ad formats. To select and measure ads — including personalized ads where permitted by your device settings and region — AdMob and its partners may process device identifiers such as the Android Advertising ID (the App requests the AD_ID permission on Android 13+ for this purpose), general device information, and in-app usage signals. Advertising is not currently active on the iOS build of the App; if that changes, we will update this Policy and request iOS App Tracking Transparency consent where required before doing so.

Push notifications (Android currently). The App may request permission to send you notifications (for example match or score alerts). On Android this uses the system runtime notification permission; Firebase Cloud Messaging assigns your device a registration token, managed by Google, to route these alerts — the App does not read, store or transmit that raw token beyond logging its length for diagnostics, and devices are grouped only into a single shared alerts topic rather than targeted individually.

Network status (Android). The Android build requests network-connectivity visibility so we can avoid unnecessary retries when offline. This does not reveal contact lists or private files by itself.

Media loaded from URLs. Player, team and news imagery is often loaded from URLs provided in backend data; those hosts may observe your IP address when your device downloads images.

The App does not request access to your camera, microphone, contacts, precise location, or photo library, and has no such permissions declared on either platform.

3. How we use information

We use the above only to operate, secure and troubleshoot the App, select and measure advertising, improve features, comply with agreements, and meet legal obligations. We do not use this information to message you commercially unless we add an optional contact flow in the App and revise this Policy.

4. Sharing

Processors that may receive subsets of diagnostics, advertising or incidental network metadata:

We may also disclose information if compelled by lawful process or to defend our legal rights when permitted by law.

5. Your controls and regional rights

You can opt out of personalized advertising or reset your advertising identifier from your device settings (on Android: Settings → Privacy → Ads). You can also revoke the App’s notification permission at any time from your device’s app settings. Android and iOS additionally let you disable ad-related tracking resets or analytics collection where platforms expose such toggles for Firebase/Google services. Reach out via hello.inningsstudio@gmail.com for subject-rights inquiries (access, deletion, portability) where regulations grant them — we will verify identity when required before acting.

6. Children

scoreCF serves a general sports audience and is not directed to children under 13 (or the applicable minimum age in your region). We do not knowingly collect personal information from children, and we do not knowingly serve child-directed advertising through the App. Parents or guardians who believe a child has provided information may contact us to request its removal.

7. Retention and security

Firebase retains crash logs, analytics and configuration data according to dashboards we configure and Firebase defaults; Google AdMob retains advertising-related data according to its own policies, which we do not control. Requests to our backends are logically separated from unrelated projects. HTTPS is enforced for applicable endpoints.

8. International transfers

Servers connected to Firebase, Google AdMob and other third-party hosts may reside outside your home country (including regions Google selects for redundancy or ad delivery). Google offers standard contractual safeguards in many regions; consult Google’s Firebase and AdMob documentation for specifics.

9. Changes

We update this Privacy Policy when features or regulators require it and refresh the Effective date posted here. Material changes affecting collection — including any change to where or how advertising is served — will include an in-app alert or revised store disclosures when required.