Privacy Policy
CricKOrbit ("the app", "we") is a cricket scoring, statistics, club and tournament app published by Chetan Bathre. This policy explains what data the app collects, why, and the choices you have.
1. Data we collect
- Account data: mobile number (used to sign in with an OTP), or your Google account email if you sign in with Google.
- Profile data you enter: name, profile photo, state and city, date of birth, gender, playing role, batting/bowling style, jersey number and bio. Date of birth and gender are used for age and gender categories (for example Under-16, Women, Masters 40+) and for safety settings for younger players.
- Parent or guardian number: for players under 13, the mobile number of a parent or guardian, verified with a one-time code. It is stored only on our servers and is never shown to other users.
- Cricket data: matches you score or play in, ball-by-ball records, scorecards, statistics, teams, clubs, tournaments, grounds and awards.
- Content you share: club posts, comments, chat messages, photos and attachments you upload, polls and reports.
- Location: your city/state from your profile; when you set up a match or ground, the ground location may be used to show weather and nearby grounds. If you claim a ground as its owner, we collect your precise location at that moment, the Google Maps link and the photos you add, so our team can check the claim. We do not track your location in the background.
- Camera and microphone (CricKOrbit Live): only when you choose to go live, the app uses your camera and microphone to send video and sound directly from your phone to the streaming service you pick (for example YouTube, Facebook or Twitch) with your own stream key. The video and sound do not pass through or get stored on CricKOrbit servers. Your stream key is saved only on your phone. We store your live tokens, the match you streamed, the overlay settings (theme, ticker text, commentator names, sponsor names) and the public video link if you add one, which is shown on the match page.
- Purchases: subscription and coin purchases are processed by Google Play. We receive a purchase token and product ID to activate your plan; we never see your card or bank details.
- Device and technical data: push-notification token, app version, device model and identifiers used for fraud and abuse prevention, and the advertising ID used by Google AdMob. If you join through a friend's invite link, we read the Google Play install referrer and a one-way hash of your device ID to prevent invite reward abuse.
2. How we use data
- Sign-in and account security.
- Recording matches and calculating statistics, rankings, leaderboards and insights.
- Showing your public cricket profile, teams, clubs and tournaments to other users.
- Sending notifications you choose to receive (match invites, results, club messages).
- Activating premium plans and coins, preventing cheating, fake matches and abuse.
- Showing ads to free users.
3. What other users can see
Your name, photo, city, role and cricket statistics are visible to other users of the app. You can switch your profile to Limited in Settings → Profile privacy: you are then hidden from name search and suggestions, and your photo, bio and social links are shown only to people you follow. Your date of birth is not displayed to other users; leaderboards only use it to place you in an age group. When a match is scored live and shared, a public web page shows the score, team names and the names of the current batters and bowler to anyone with the link (no phone numbers). Your phone number is not displayed on your profile, but it is used as your player identity, so other users who know your number can find you to add you to a match or team. Club content is visible to members of that club according to club settings.
4. Third-party services
- Google Firebase (Authentication, Cloud Firestore, Cloud Storage, Cloud Functions, Cloud Messaging) – stores and processes app data on Google Cloud servers.
- Google Play Billing – processes purchases.
- Google AdMob – shows ads; may use the advertising ID. See Google's ad policies.
- Google ML Kit – on-device translation of app text.
- Streaming platforms you choose (YouTube, Facebook, Twitch or a custom RTMP server) – receive your live video directly from your phone under their own terms and privacy policies.
- Open-Meteo – weather for a match location (only coordinates are sent).
We do not sell your personal data.
5. Data security and retention
Data is sent over encrypted connections (HTTPS/TLS) and protected by access rules on our servers. We keep your data while your account is active. When you delete your account, your profile and personal data are deleted as described on the account deletion page. Match records that include other players may keep your name as it appeared in that scorecard so other players' statistics stay correct.
6. Children
Players under 13 can create an account only after a parent or guardian verifies their own mobile number with a one-time code. For these accounts we collect only the data needed to play and record cricket (profile, matches and statistics), show no advertising (no banner, full-screen or rewarded ads; ad requests are tagged as child-directed), do not offer live streaming or links to outside video sites, keep the profile Limited, and require approval before a team can add the player. Players under 18 always have a Limited profile and teams must ask before adding them. Younger players may also be added to a club by a parent or guardian through the club's guardian process. A parent or guardian can ask us to review or delete a child's data at any time using the contact details below or the account deletion page. If you believe a child's data was added without consent, contact us and we will remove it.
7. Your choices
- Edit your profile at any time in the app.
- Turn notifications on or off in Settings.
- Reset or limit your advertising ID in your device settings.
- Delete your account in the app (Settings → Delete account) or by email (see below).
8. Contact
Questions or requests: chetan.bathre1@gmail.com
We may update this policy; the date above shows the latest version.