Privacy

My11Stats

Effective date: May 17, 2026 · Developer: inningsstudio.com

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 My11Stats mobile application (“My11Stats,” “App”) on Android or iOS. Questions: hello.inningsstudio@gmail.com.

2. Information we collect

Information you enter. My11Stats is built to browse cricket-related schedules, fixtures, and statistics-style content served from our backends. For core browsing, we do not require account registration, and we do not intend to collect your name or email through normal use.

Automatic diagnostics and analytics. When you open the App, your device communicates with our services and Google Firebase-related components that may automatically process:

  • Crash reports: On Android we use Firebase Crashlytics to collect crash stacks and debug context (for example anonymized identifiers and metadata about the failing session) so we can fix bugs.
  • Analytics: On Android we use Firebase Analytics to gather aggregated usage counts (such as which parts of the App are viewed) so we can improve usability. Firebase also initializes on iOS; Firebase may collect identifiers and usage events associated with Firebase services configured for the App.
  • Firestore content requests: The App retrieves match-centric documents (for example fixtures and detail payloads) via Firebase-hosted services using read operations. Typical automatic data includes request metadata your device transmits (network addresses, timestamps, HTTPS headers) handled by Google according to Firebase’s documentation.

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 or team imagery is often loaded from URLs provided in backend data; those hosts may observe your IP address when your device downloads images.

3. How we use information

We combine the above only to operate, secure, troubleshoot, prioritize features, comply with agreements, and meet legal obligations. We do not use the information described above 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/telemetry or incidental network metadata:

Recipient Role
Google Firebase / Google Cloud Crashes, analytics, Firebase data delivery infrastructure
Image / media hosts referenced in payloads Delivering thumbnails and artwork

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

Android and iOS 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

My11Stats serves a general cricket audience but is not designed to knowingly collect personal details from children under statutory minimums without parental authorization. Parents may contact us to request removal if they believe otherwise.

7. Retention and security

Firebase retains crash logs and analytics according to dashboards we configure and Firebase defaults. Requests to our backends are logically separated from unrelated projects. HTTPS is enforced for applicable endpoints.

8. International transfers

Servers connected to Firebase and third-party hosts may reside outside your home country (including regions Google selects for redundancy). Firebase offers standard contractual safeguards in many regions; consult Google Firebase 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 will include an in-app alert or revised store disclosures when required.

This document references Google Firebase Analytics, Crashlytics, Firebase Core, Firestore-backed delivery, HTTPS networking, and Android permissions based on My11Stats builds as of May 2026. If you materially change SDKs or data flows later, regenerate this Policy with counsel.