Privacy Policy
This policy applies specifically to CricScore, our live cricket scoring and match analytics platform. We are committed to transparency in how your match records, player lists, and credentials are handled.
1. Core Architecture: Offline-First with Secure Cloud Sync
CricScore operates on a hybrid architecture designed for sports fields with variable connectivity. When scoring a match, all ball-by-ball events are captured and saved inside a secure, local SQLite database on your device. Once an internet connection is established, data is synchronized with our secure Spring Boot microservices backend via Apache Kafka streams.
2. Information We Collect and Process
To provide live scoring, team management, and match histories, CricScore processes the following categories of information:
Account & Authentication
We use secure Google Sign-In/OAuth. We retrieve only your email address, name, and profile picture to establish a secure user session.
Match & Scoring Records
Ball-by-ball details, runs, wickets, overs, and match statuses are stored locally and synced online to compile statistics and match history.
Team & Player Rosters
Player profiles, team names, and squad statistics entered by you are managed to facilitate scoring workflows and database integrity.
Offline Database Files
A sandboxed SQLite database file caches all details locally. It handles guest scoring sessions and coordinates server-sync requests upon login.
3. Guest Mode & Automatic Background Syncing
CricScore provides a "Continue as Guest" option allowing you to score matches completely offline without registering an account. In guest mode:
- All match scorecards and player information are held strictly inside your device's SQLite storage.
- No personal identifiers are stored or uploaded to our servers.
When you later log in with an authenticated account, the app automatically triggers a background synchronization queue, transferring your guest match records to the secure cloud server so your stats are consolidated.
4. Permissions Required
CricScore requires minimal system access to perform its functions:
- •Network & Internet: Required to authenticate users via OAuth and to push updates from the local database to the microservices scoring backend.
- •Notifications: Used to display background sync status updates and match completion alerts.
5. Data Sharing & Security
We employ strict industry-standard security measures to safeguard your matches:
- We do not share, sell, or rent your scoring records or player profiles to third-party advertisers.
- Data transmitted to our microservices backend (Match, Team, and Score services) is encrypted via Transport Layer Security (TLS).
- OAuth tokens are securely stored on the device using keychain/secure storage mechanisms and are never exposed.
6. Children's Privacy
CricScore is designed for general audiences, including youth cricket leagues. When scoring matches for players under 13, only team names and statistics are processed. We do not request or store any personal contact details for minors, keeping the application compliant with COPPA and global safety regulations.
7. Contact & Support
If you have any questions or concerns regarding this privacy policy, data deletion requests, or need technical support for CricScore, feel free to contact us:
Company: Kangeyam Innovations
Developer: BOOPATHIRAJAN S
Email: kangeyaminnovations@gmail.com
Location: Tiruppur, Tamil Nadu, India
© 2026 Kangeyam Innovations. All rights reserved.
CricScore is a protected software service of BOOPATHIRAJAN S.