Come Privacy Policy
Effective date: 2026-08-25. Operator: Come. Jurisdiction: India.
Information we collect
Come collects the minimum information needed to operate the app: account registration (mobile number, name), KYC documents (Aadhaar, PAN or Voter ID), wallet transactions, and device metadata for fraud prevention.
How we use information
Information is used to operate the wallet, settle bets, prevent fraud, comply with KYC and AML obligations, and improve the product. Marketing use is opt-in and separately controlled.
Sharing and disclosure
Come does not sell personal data. Information is shared with KYC processors, payment partners and regulatory authorities when required by law. Service providers are bound by data-processing agreements.
Cookies
Come uses strictly necessary cookies to keep allappcome.com working - login, OTP, wallet balance and live contest odds. Optional analytics and marketing cookies default off. You can change your preference at any time using the Cookie Settings link in the footer.
Full cookie details live on the Cookies policy.
Retention
Account and KYC records are retained for the period required by Indian law. Wallet transaction history is retained for 7 years for audit and reconciliation.
Your rights
You can request access, correction or deletion of your personal data through the support desk. Deletion requests are honoured unless a legal obligation requires continued retention.
Contact
Privacy questions can be sent through the support desk at /contact.
What this document covers, in plain language.
Privacy policy is the Come Come privacy practices. The plain-language summary below maps every clause to a short reading. The full text follows the summary.
What this document covers
This privacy policy covers the personal data Come collects, the purposes it is used for, the retention windows, the third-party processors, the player rights, and the contact channel for privacy enquiries.
Data collected
Come collects registration data (name, email, phone, PAN, Aadhaar), gameplay data (contest entries, table stakes, outcome history), payment data (transaction rail, amount, timestamp), and support data (ticket content, conversation history).
Purposes
Data is used for account verification, KYC, AML screening, contest settlement, payout settlement, support, fraud detection, responsible-use monitoring, and regulatory reporting.
Retention
Registration and KYC data is retained for the published retention window after account closure. Gameplay data is retained for the longer of the regulatory minimum and the published retention window. Payment data is retained for the regulatory minimum.
Third-party processors
Come uses payment processors for transactions, identity-verification processors for KYC, and analytics processors for traffic analysis. Each processor is bound by a data-processing agreement.
Player rights
Players can request access to their data, correction of inaccurate data, deletion of data past the regulatory minimum, and a copy of their data in a structured format. Privacy requests are handled by the privacy desk within the published response window.
How this document is organised.
The full text of Privacy policy is organised into sections that mirror the plain-language summary above. Each clause in the full text corresponds to one of the summary blocks. Reading the summary first, then the full text, is the recommended path.
How to cite a clause
When opening a support ticket that cites this document, quote the section heading, not the section number. Section numbers shift on review but section headings stay stable.
Translation and review
This document is reviewed on the same cadence as the rest of the legal page. The English version is the controlling version. Translations into Hindi or other Indian languages are convenience versions; the English text controls in any dispute.
Reading checklist before you share personal data.
Reading the privacy policy in full is the recommended first step. The reading checklist below maps every clause to a section of the document. Reading the summary first, then the full text, is the recommended path.
What data is collected
Come collects registration data, gameplay data, payment data, and support data. The collected data is the minimum required to operate the verified Come access route and to meet regulatory obligations.
Why data is collected
Data is collected for account verification, KYC, AML screening, contest settlement, payout settlement, support, fraud detection, responsible-use monitoring, and regulatory reporting.
How long data is retained
Registration and KYC data is retained for the published retention window after account closure. Gameplay data is retained for the longer of the regulatory minimum and the published retention window. Payment data is retained for the regulatory minimum.
Who has access to data
Data is accessed by Come staff on a need-to-know basis. Data is shared with payment processors, identity-verification processors, and analytics processors, each bound by a data-processing agreement. Data is shared with regulators on lawful request.
Player rights
Players can request access to their data, correction of inaccurate data, deletion of data past the regulatory minimum, and a copy of their data in a structured format. Privacy requests are handled by the privacy desk within the published response window.
Cookies
The cookie policy below sets out the cookie categories and the controls available. Strictly necessary cookies remain on while the player is signed in. Analytics and marketing cookies remain off until the player opts in.
Practical scenarios for the privacy policy.
Reading the privacy policy in theory is one thing. The practical scenarios below show how the policy applies in common player situations.
Closing an account
When a player closes their account, registration and KYC data is retained for the published retention window after closure. Gameplay and payment data is retained for the regulatory minimum. After the retention window, all data is purged from operational systems. Backup copies age out on the standard backup retention cycle.
Requesting a data export
A player can request a copy of their data in a structured format. The request is handled by the privacy desk within the published response window. The export is delivered as a downloadable archive that the player can store offline. The export includes registration, KYC, gameplay, payment, and support data.
Updating personal details
Players can update their registered email, phone, and address from the account settings. Updating KYC documents (PAN, Aadhaar) requires re-verification. The privacy desk handles re-verification requests and confirms the update by email.
Sharing data with a third party
Come does not sell player data. Data is shared with payment processors, identity-verification processors, and analytics processors only, each bound by a data-processing agreement. Data is shared with regulators on lawful request.
Cookie preferences
The cookie preferences panel sets which categories of cookies are loaded. Strictly necessary cookies remain on while the player is signed in. Analytics and marketing cookies remain off until the player opts in.
Children's data
Come does not knowingly collect data from players under 18. If a player under 18 registers, the account is closed on detection and the collected data is purged from operational systems. Backup copies age out on the standard backup retention cycle.