Privacy Policy

1. Scope

CrickSync is a cricket scoring, professional broadcast graphics, PDF scorecard and YouTube live-production app. This policy applies to the CrickSync Android app and its supporting cloud services.

2. Data we use

• Account: name, verified mobile number, email address when provided, profile photo, sign-in provider, verification status and account identifiers. For mobile sign-in, Firebase sends and verifies a one-time SMS code. Guest browsing stays on your device and does not create a Firebase account identifier.
• Match: team and player names, team logos, scores, ball events, rules, room codes, graphics commands, device presence and synchronization acknowledgements.
• Camera and microphone: preview and live-production media only when you use these features. A live feed is sent to the streaming destination you select after Start Live.
• Device media: images you select for team logos. PDF scorecards are created locally and shared only when you choose.
• Diagnostics: operational status needed to connect scoring and camera phones. CrickSync currently does not include third-party advertising SDKs.

Do not enter sensitive personal information as a player or team name.

3. YouTube API Services

CrickSync uses YouTube API Services. When you connect YouTube, the app requests permission to manage the broadcasts it creates for you. Channel identity and live-session details are used to create, configure, bind, start and complete a broadcast with your selected Public, Unlisted or Private visibility.

Use is also subject to the YouTube Terms of Service and Google Privacy Policy. You can revoke CrickSync access at any time from Google Account permissions. Disconnecting YouTube in CrickSync also revokes the connected consent.

4. Google Play purchases

Google Play processes payment details. CrickSync sends product and purchase identifiers, purchase token, store name and a one-way account hash to a secure verification service. Verified entitlements, transaction references and anti-fraud records may be retained to restore purchases, prevent token reuse and meet legal or security obligations.

5. Service providers

CrickSync uses Google Firebase for mobile OTP, account authentication and synchronized cloud data, Google Sign-In and YouTube APIs for connected live streaming, and Google Play Billing for digital purchases. Mobile carriers and their messaging partners may process the destination number and SMS delivery information. Information is not sold. It is shared only with providers needed to deliver user-requested features, comply with law or protect users and the service.

6. Security and retention

CrickSync uses access-controlled Firebase rules, verified account identity and server-side purchase verification. Account profile data is kept while an account is active and removed when deletion completes. YouTube-authorized data is deleted or refreshed as required by YouTube policies. Transaction, security and fraud-prevention records may be retained where reasonably required.

7. Your controls

• Disconnect or revoke YouTube access.
• Choose Public, Unlisted or Private for each broadcast.
• Edit optional profile information in My Account.
• Delete your CrickSync account inside the app or use the web deletion request.

CrickSync is a match-operations tool and is not directed to children. Organizers should obtain appropriate permission before entering junior-player information.

8. Contact

Privacy and account requests: cricksyncofficial@gmail.com