Legal · Privacy · Google Play

Privacy Policy for CricLive

This Privacy Policy applies to the mobile application CricLive (Android package name com.cricketbroadcast), available on Google Play, and operated by TechHarbour (“we”, “us”, or “our”).

Effective date
Last updated

1. Who we are (app and developer identity)

Google Play and users should be able to match this policy to the listing for CricLive. The identifiers below are the ones associated with that listing:

Detail Value
App name (Google Play / device) CricLive
Android package name com.cricketbroadcast
Developer / publisher TechHarbour
Legal / privacy contact contact@techharbour.co
This Privacy Policy URL https://zesty-medovik-e904c3.netlify.app/
Platform Android (Google Play)

If the Google Play Console developer name for this listing is shown as TechHarbour, that is the same publisher named in this policy. Product descriptions may also refer to cricket scoring and live broadcast features; those features are part of the CricLive app identified above.

2. What the App does

CricLive helps you score cricket matches, manage teams and tournaments, sync live match data between devices, and broadcast live video with an on-screen score overlay to streaming platforms you choose (for example YouTube or Facebook Live). You enter streaming server details and stream keys in the App; we do not operate the live video destination platform.

3. Information we collect

3.1 Account and profile information

When you sign in, we collect and store:

  • Email address (email/password sign-in, or email provided by Google or Facebook sign-in)
  • Display name (if you provide one when creating an account or from your Google/Facebook profile)
  • A Firebase Authentication user identifier (UID) used to link your data in our backend

You may also set a club name and club logo, and other profile preferences stored on your device and, where you use cloud sync, in our database.

3.2 Cricket and organization data you create

When you use scoring, teams, tournaments, or broadcast features, the App processes data you enter, such as:

  • Team and tournament names
  • Player names and squad lists
  • Match details, ball-by-ball events, scores, and related statistics
  • Match codes used to connect a scorer device with a broadcaster device
  • Logo images or image URLs for teams and tournaments (optional)

This content may be stored locally on your device and, when you are signed in and connected, synchronized through Google Firebase (Firestore and Realtime Database) so other devices you authorize can read live match state.

3.3 Images you upload

If you upload team, tournament, or club logos, the image file may be sent to Cloudinary (when configured in the App) using an unsigned upload preset. Cloudinary hosts the image and returns a URL used in the App. You may instead paste a link to an image without uploading through Cloudinary.

3.4 Live streaming

When you use broadcast features, the App accesses:

  • Camera — to capture video for live streaming and preview
  • Microphone — to capture audio for live streaming

Your RTMP/RTMPS server URL, stream key, and destination platform (for example Facebook, YouTube, or custom) may be saved for a match so another authorized broadcaster can go live for that same match. That destination may be stored:

  • On your device (local cache), and
  • In our Firebase backend for that match, when you choose to save it for the match

When you go live, video and audio are encoded on your device and sent directly to the streaming service you configured (for example YouTube or Meta/Facebook). That transmission is governed by that platform's terms and privacy policy.

3.5 Device and local storage

The App uses local storage on your phone to:

  • Queue scoring updates when offline and sync when back online
  • Cache teams, matches, and catalog data
  • Remember overlay and UI preferences
  • Cache a saved stream destination for a match on that device

We do not use a dedicated third-party advertising analytics SDK in the App source code. Google Firebase and Google Play services (when you use Google Sign-In) may still process limited technical or diagnostic data as described in their own policies (see Section 5).

3.6 Permissions

The App may request Android permissions including:

Permission Purpose
Internet Sign-in, cloud sync, logo upload, streaming
Camera Live broadcast video
Record audio Live broadcast audio
Vibrate Optional feedback when scoring
Post notifications Foreground streaming / sync notifications where applicable
Foreground service (camera/microphone) Keep live capture running while broadcasting

You can deny permissions in system settings; some features will not work without them.

4. How we use information

We use the information above to:

  • Create and manage your account
  • Provide scoring, sync, and broadcast functionality for CricLive
  • Store and display your teams, tournaments, and match data
  • Enable multi-device match sharing via match codes
  • Store a stream destination for a match when you save it for broadcasting
  • Upload and display logos you choose to upload
  • Operate and improve the App and our services
  • Respond to support requests and enforce our terms
  • Comply with legal obligations

We do not sell your personal information. We do not use your data for third-party advertising in the App.

5. How we share information

We share information only as follows:

Recipient What is shared Why
Google Firebase (Authentication, Cloud Firestore, Realtime Database) Account identifiers, email, match/team/tournament data you sync, and stream destinations you save for a match Hosting, authentication, real-time sync, and shared broadcast setup
Google (Google Sign-In) Sign-in tokens and profile basics per Google's flow Optional sign-in method
Meta / Facebook (Facebook Login SDK) Sign-in tokens and profile/email per Facebook's permissions Optional sign-in; you may also stream to Facebook using credentials you provide
Cloudinary Image files you upload for logos Image hosting and delivery
Streaming platforms you choose (e.g. YouTube, Facebook Live) Encoded live video, audio, and metadata required by that platform Only when you start a live stream using your own stream key
Service providers Data necessary to run infrastructure Only if we use contractors bound by confidentiality
Legal / safety Information required by law Court orders, legal process, or to protect rights and safety

Third-party privacy policies

6. Data retention

  • Account data is kept while your account is active.
  • Match and team data in Firebase is kept until you delete it in the App (where available) or request deletion.
  • Stream destinations saved for a match remain until cleared in the App or deleted with related match data, or until you request deletion.
  • Local cache on the device persists until cleared by the App, you, or uninstallation.

We may retain certain records where required by law or for legitimate business purposes (for example dispute resolution).

7. Your choices and rights

Depending on your location, you may have rights to access, correct, delete, or export personal data, or to object to or restrict certain processing.

  • Sign out: Use Sign out in the App settings / profile screens.
  • Permissions: Change camera, microphone, and other permissions in Android Settings.
  • Stream destination: Clear a saved destination in the broadcast screen, or request deletion by email.
  • Account deletion: To request deletion of your Firebase account and associated cloud data for CricLive, email contact@techharbour.co from your account email. We will verify your request and delete or anonymize data within a reasonable period, except where we must retain data by law.

If you are in the European Economic Area (EEA), United Kingdom, or California, you may have additional rights under GDPR or CCPA/CPRA. Contact us to exercise them.

8. Security

We use industry-standard measures through Firebase (HTTPS/TLS in transit) and secure practices for account access. No method of transmission or storage is 100% secure. You are responsible for keeping your password and stream keys confidential and for who you share match codes with.

9. International transfers

Firebase and other providers may process data in countries other than yours, including the United States. Where required, we rely on appropriate safeguards (such as standard contractual clauses offered by providers).

10. Children's privacy

CricLive is not directed at children under 13 (or the minimum age in your country). We do not knowingly collect personal information from children. If you believe a child has provided us data, contact us and we will delete it.

11. Contact us

For privacy questions, data access or deletion requests, or other inquiries about CricLive published by TechHarbour:

12. Changes to this policy

We may update this Privacy Policy from time to time. We will post the new version at https://zesty-medovik-e904c3.netlify.app/ (the same HTTPS URL linked from Google Play for CricLive) and update the “Last updated” date. Continued use after changes means you accept the updated policy.