Privacy Policy

Last updated: 25 July 2026

CrickFlow is operated by Mavixas (“we”, “us”). This policy explains how we collect, use, store, and share information when you use the CrickFlow mobile app, websites, and related services (together, the “Service”).

Information we collect

Account: Email, display name, phone number (if you use phone sign-in), and profile photo from Google Sign-In.
Profile & cricket data: Cricket ID, location (country/city), teams, players, squads, match scores, ball-by-ball events, tournaments, follows, and notification preferences you set.
Device & notifications: Firebase Cloud Messaging (FCM) token so we can send match and follow alerts you opt into.
Streaming: Camera and microphone are accessed only when you start a live stream. Stream destination settings (e.g. YouTube / custom RTMP) that you enter are stored to provide broadcasting features.
Offline data: Scoring actions may be stored temporarily on your device before syncing to our servers when you are online.

Google user data

When you sign in with Google or connect a YouTube account, CrickFlow accesses Google user data only with your consent, and only as needed for the features you use:

Google Sign-In (basic profile): email address, display name, and profile photo used to create and manage your CrickFlow account.
YouTube OAuth (optional — only if you connect YouTube for live streaming): we request permission to manage and view your YouTube account (https://www.googleapis.com/auth/youtube and https://www.googleapis.com/auth/youtube.force-ssl) so CrickFlow can create live broadcasts, obtain RTMP stream keys and watch URLs, read linked channel information, show live chat while you are broadcasting, and help you export chapter markers for your YouTube video description. We store OAuth tokens securely on our servers (Firebase / Cloud Functions) solely to perform these actions on your behalf.

We use Google user data only to provide and improve these user-facing CrickFlow features. We do not use Google user data for advertising, retargeting, credit scoring, or sale to data brokers.

How we use data

We use this information to provide scoring, scorecards, tournaments, community features, notifications, live overlays, and optional streaming. We do not sell your personal data.

Sharing, transfer, and disclosure of Google user data

We do not sell Google user data. We do not transfer or disclose Google user data to third parties for purposes unrelated to operating CrickFlow. Specifically:

Google / YouTube: When you connect YouTube and start a stream, API requests are sent to Google/YouTube so your live broadcast can be created and managed on your channel. Google processes that data under Google’s own policies.
Google Firebase (our infrastructure): Account profile data and streaming credentials for project crickflow-b06bc are stored and processed on Google Firebase / Cloud Functions so we can authenticate you and run streaming features. This is hosting and processing by our service provider, not a sale or marketing transfer.
Other users of CrickFlow: Cricket content you create (e.g. match scores, scorecards, public profile name) may be visible to other users as part of the Service. We do not share your Google OAuth tokens or YouTube credentials with other users.
Legal / safety / corporate events: We may disclose information if required by law, to investigate abuse or security issues, or—with your explicit prior consent—as part of a merger, acquisition, or sale of assets.

We do not transfer or disclose Google user data to advertising platforms, data brokers, or information resellers. We do not transfer or disclose Google user data to third parties for purposes other than those described in this policy.

Storage & security

Data is stored in Google Firebase (project crickflow-b06bc) with authentication and security rules. YouTube OAuth tokens are stored server-side and are not exposed to other clients. You are responsible for keeping your login credentials secure.

Third parties

Google (Authentication, Firebase, Google Sign-In, YouTube Data API)
YouTube / RTMP providers when you choose to broadcast

Their processing is governed by their own policies. We only share what is needed to operate the features you use, as described in “Sharing, transfer, and disclosure of Google user data” above.

Your choices

Control team and follow notification preferences in Settings → Notification Settings.
Delete your account in the app: Settings → Delete Account. This removes your profile, linked player record, notifications, and Firebase sign-in. Matches and teams you created may remain visible to other users until an organizer removes them.
You may contact us to request access, correction, or deletion of additional personal data where applicable.

Children

CrickFlow is not directed at children under 13. If you believe a child has provided personal data, contact us and we will take appropriate steps to remove it.

Changes

We may update this policy from time to time. The “Last updated” date at the top reflects the latest revision. Continued use of the Service after changes are posted constitutes acceptance of the updated policy.

Contact

Mavixas — CrickFlow support
Email: mavixas.ceo@gmail.com