CRICKET DECK
PRIVACY POLICY
Last updated: 23 October 2026
Published by Cricket Deck Games
This Privacy Policy explains how Cricket Deck Games collects, uses, stores, protects and deletes information when you use the Cricket Deck mobile game and its online features.
1. Who We Are
Cricket Deck is a mobile card game published by Cricket Deck Games. In this Privacy Policy, "Cricket Deck", "we", "us" and "our" refer to Cricket Deck Games as the developer and operator of the Cricket Deck application and related backend services.
This policy applies to the Cricket Deck mobile application and to online functionality operated by Cricket Deck Games, including account and identity features, cloud-backed gameplay, Daily play, Quick Match, Friend Challenge, activity records and gameplay notifications.
2. Age and Intended Audience
Cricket Deck is intended for users aged 13 years and older. It is not specifically designed or marketed for children under 13.
Certain online features are available only to eligible players who have the required protected cloud identity. Where notification functionality is used, push registration is gated so that it does not begin for under-13 or offline-only players.
3. Information We May Collect
The information collected depends on which Cricket Deck features you use. We aim to collect only the information reasonably necessary to operate, secure and support the game.
3.1 Account and identity information
A Cricket Deck user or account identifier used to associate cloud-based features with the correct player.
A player nickname or display name where you choose or are assigned one for multiplayer use.
Technical authentication or identity information required to establish and protect access to cloud features.
Your nickname may be shown to another player where this is necessary for multiplayer gameplay, for example during a Friend Challenge.
3.2 Gameplay and multiplayer information
Game state, scores, results, targets, turns, rule versions and other information required to run or validate gameplay.
Friend Challenge invitations, acceptance state, batting order, innings status and match outcomes.
Server-side validation results used to determine whether multiplayer innings are valid.
Operational timestamps associated with gameplay records.
This information is used to provide game functionality, preserve match integrity, prevent invalid state changes and allow players to resume or complete supported online matches.
3.3 Friend Challenge activity records
When you use Friend Challenge, Cricket Deck may create activity records relating to match events. These records may include the activity type, the relevant challenge or match identifier, server-generated notification title and message text, player nickname information already visible to the opponent, match targets or results, timestamps, notification delivery state and whether an activity item has been read.
Friend Challenge activity records are retained by Cricket Deck for up to 30 days and are then scheduled for removal.
3.4 Device and push-notification information
If you enable or use Friend Challenge push notifications, Cricket Deck and Firebase Cloud Messaging may process a Firebase installation identifier and push-notification registration information so that a message can be delivered to the correct installation of the app.
A push-notification registration token or equivalent registration information.
A server-generated identifier derived from the token for safe storage and ownership tracking.
Device platform and registration or refresh timestamps.
Cricket Deck stores its push-registration records for up to 60 days after the last registration or refresh, unless the registration becomes invalid, is removed earlier, or the associated account is deleted.
3.5 Security and app-integrity information
Cricket Deck may process technical information required to authenticate requests, protect backend services and help distinguish genuine app traffic from unauthorized or fabricated requests. This may include tokens or attestation information supplied through Firebase security and app-integrity services.
4. How We Use Information
We use collected information only for legitimate operational purposes connected to Cricket Deck, including:
Providing and maintaining game functionality.
Creating, validating, resuming and completing online matches.
Supporting Friend Challenge invitations, turn-taking, targets, results and rematches.
Delivering optional gameplay notifications.
Showing in-app Friend Challenge activity and unread indicators.
Protecting multiplayer integrity and preventing invalid or unauthorized requests.
Maintaining account and cloud identity functionality.
Diagnosing operational problems and maintaining the reliability of backend services, where applicable.
Complying with legal obligations and enforcing applicable rules or terms.
Friend Challenge push notifications are service and gameplay notifications. They are not used by Cricket Deck for advertising or marketing.
5. Friend Challenge Notifications
Eligible players may receive notifications about Friend Challenge activity. Examples include:
A player has challenged you.
Your challenge has been accepted and batting order has been determined.
Your opponent has completed the first innings and your chase is ready.
A Friend Challenge has been completed, including a win, loss, tie or forfeit.
Notification text is generated by Cricket Deck's server from the authoritative match state. A push notification acts only as an alert or pointer to the relevant match. When you open the match, Cricket Deck loads the current authoritative state rather than trusting the contents of the push message itself.
You can deny or disable operating-system notification permission without losing access to Friend Challenge itself. In-app activity, unread indicators and match actions continue to function even when push notifications are disabled.
6. Firebase and Service Providers
Cricket Deck uses Google Firebase services to support cloud-based functionality. Depending on the feature, these services may include authentication or identity services, Cloud Firestore, Cloud Functions, App Check and Firebase Cloud Messaging.
Firebase Cloud Messaging uses Firebase installation identifiers to determine which app installation should receive a message. Google/Firebase processes information under its own applicable privacy, security and data-processing terms.
Cricket Deck does not sell your personal information to Firebase or to advertisers, and Friend Challenge push notifications are not used for targeted advertising.
7. When Information Is Shared
We do not sell personal information. Information may be disclosed only where necessary to operate the service or where required by law.
With another player: limited multiplayer information, such as your nickname, game state, score, target and result, may be shown to your Friend Challenge opponent as part of normal gameplay.
With service providers: technical information may be processed by service providers such as Google Firebase where necessary to provide hosting, identity, database, security or push-notification functionality.
For legal or security reasons: information may be preserved or disclosed where reasonably necessary to comply with lawful legal process, protect users, investigate abuse, or protect the security and integrity of Cricket Deck.
8. Data Retention
We retain information only for as long as reasonably required for the purpose for which it was collected, subject to technical, legal and operational requirements.
Data / record
Cricket Deck retention
Friend Challenge activity / notification records
Up to 30 days
Push registration / device token records
Up to 60 days after last registration or refresh, unless removed earlier
Invalid push registrations
May be removed automatically when reported invalid
Account-related cloud information
Retained as required to provide the account and associated features, subject to account deletion and applicable legal requirements
Third-party service providers may apply their own technical retention periods. For example, Firebase may retain certain service data or installation identifiers for limited periods in accordance with Google's published Firebase privacy and retention practices.
9. Account Deletion and Data Removal
Where account deletion is available within Cricket Deck or through an approved account-deletion process, deleting your Cricket Deck account removes the Cricket Deck data configured for deletion for that account.
For Friend Challenge notification functionality, account deletion removes:
The player's Friend Challenge notification inbox records stored by Cricket Deck.
Push-notification registration records and token ownership records stored by Cricket Deck.
Some data may remain temporarily in backups, logs or third-party systems according to applicable technical retention cycles, legal obligations or service-provider policies before final deletion.
10. Your Choices and Controls
Depending on the feature and your device, you may be able to:
Choose whether to grant operating-system permission for push notifications.
Disable Cricket Deck notifications later through your device settings.
Use Friend Challenge without receiving push notifications, where the feature is otherwise available.
Request or use the available Cricket Deck account-deletion process.
Contact Cricket Deck Games with privacy questions or requests.
Disabling push notifications does not delete your Cricket Deck account and does not by itself remove information that must remain temporarily to support active gameplay or applicable retention periods.
11. Security
Cricket Deck uses technical and access-control measures intended to protect cloud data and restrict access to authorized users and backend services. Friend Challenge notification inboxes are designed so that a player can read only their own notification records, while push-token storage and token-ownership records are server-only.
No method of electronic storage or transmission can be guaranteed to be completely secure. We therefore cannot guarantee absolute security, but we take reasonable steps to reduce unauthorized access, misuse or alteration.
12. International Processing
Cricket Deck may use cloud service providers that process or store information in countries other than your own. Where this occurs, information may be subject to the laws of those jurisdictions as well as applicable data-protection requirements. We rely on our service providers' applicable contractual and security measures for such processing.
13. South African Privacy Rights
Cricket Deck Games is based in South Africa. Where the Protection of Personal Information Act, 2013 (POPIA) applies, you may have rights relating to access, correction, deletion or objection to certain processing, subject to the conditions and exceptions provided by law.
To raise a privacy request or question, contact us using the address in Section 16. We may need to verify that the request relates to the correct Cricket Deck account before acting on it.
14. Children's Privacy
Cricket Deck is not intended for children under 13. We do not knowingly design Friend Challenge push registration to operate for under-13 players. If we become aware that information has been collected from a child contrary to applicable law or our intended audience settings, we will take appropriate steps to address it.
15. Changes to This Privacy Policy
We may update this Privacy Policy when Cricket Deck features, service providers, data practices or legal requirements change. When we make a material update, we will revise the "Last updated" date at the top of this policy and may provide additional notice where appropriate.
You should review the current version periodically, particularly after significant updates to online or multiplayer features.
16. Contact Us
For privacy questions, data requests or concerns relating to Cricket Deck, contact:
Publisher
Cricket Deck Games
tsaayman92@gmail.com
Application
Cricket Deck
Document control: Privacy Policy version 2.0 • Effective 23 October 2026 • Prepared for public publication and Google Play disclosure alignment.