Come Cookie Policy
Effective date: 2026-08-25. Operator: Come. Jurisdiction: India.
What cookies we use
Come uses three categories of cookies:
- Strictly necessary - authentication, session management, security. Always on.
- Analytics - aggregate, anonymised traffic analysis. Off by default.
- Marketing - campaign attribution. Off by default.
How to control cookies
Open the Cookie Settings button in the footer to change your preference. The change applies across every page on allappcome.com and is stored in your browser.
Browser-level controls and privacy extensions can also block cookies. Blocking strictly necessary cookies will break login, wallet access and OTP verification.
Duration
Strictly necessary cookies last for the session. Analytics and marketing cookies last up to 90 days.
Changes to this policy
Material changes are communicated inside the Come app and on the cookies policy document. The effective date printed under the "Effective date" line above this section reflects the most recent update.
Contact
Cookie questions can be sent through the support desk at /contact.
What this document covers, in plain language.
Cookie policy is the Come Come cookie usage. The plain-language summary below maps every clause to a short reading. The full text follows the summary.
What this document covers
This cookie policy covers the cookie categories Come uses, the purposes of each category, the retention of each cookie, the third-party cookies, and the controls available to the player.
Strictly necessary cookies
These cookies are required for the verified Come access route to function. They manage session state, CSRF protection, KYC state, and payment flow. These cookies cannot be disabled while the player is signed in.
Analytics cookies
Analytics cookies are off by default. They measure traffic, page views, and conversion funnels. They are set only after the player opts in via the cookie preferences panel.
Marketing cookies
Marketing cookies are off by default. They support campaign attribution and retargeting. They are set only after the player opts in via the cookie preferences panel.
Third-party cookies
Third-party cookies are loaded only from processors bound by a data-processing agreement. A full list of third-party cookies is published inside the cookie preferences panel.
How to change cookie preferences
Open the cookie preferences panel from the footer at any time. Toggling a category takes effect on the next page load. Strictly necessary cookies remain on for the duration of the session.
How this document is organised.
The full text of Cookie 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 change cookie preferences.
Reading the cookie 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.
Strictly necessary cookies
Strictly necessary cookies manage session state, CSRF protection, KYC state, and payment flow. They cannot be disabled while the player is signed in. The retention is the duration of the session.
Analytics cookies
Analytics cookies are off by default. They measure traffic, page views, and conversion funnels. They are set only after the player opts in via the cookie preferences panel. The retention is the published analytics window.
Marketing cookies
Marketing cookies are off by default. They support campaign attribution and retargeting. They are set only after the player opts in via the cookie preferences panel. The retention is the published marketing window.
Third-party cookies
Third-party cookies are loaded only from processors bound by a data-processing agreement. A full list of third-party cookies is published inside the cookie preferences panel.
How to change preferences
Open the cookie preferences panel from the footer at any time. Toggling a category takes effect on the next page load. Strictly necessary cookies remain on for the duration of the session.
Cookies and account closure
When an account is closed, strictly necessary cookies are cleared at the end of the session. Analytics and marketing cookies remain on the device until their natural retention expires, unless the player clears them manually.
Practical scenarios for the cookie policy.
The practical scenarios below show how the cookie policy applies in common player situations.
First-time visit
On a first-time visit, only strictly necessary cookies are loaded. The cookie preferences panel is displayed once per visitor. The player can accept all, reject optional, or manage preferences granularly. The choice is stored for the next visit.
Returning visit
On a returning visit, the stored cookie choice is honoured. The player can change preferences at any time from the footer. Changes take effect on the next page load.
Signed-in session
While signed in, strictly necessary cookies remain on. Analytics and marketing cookies follow the stored preference. The session cookie expires at the end of the session or after the published session timeout.
Account closure
When an account is closed, strictly necessary cookies are cleared at the end of the session. Analytics and marketing cookies remain on the device until their natural retention expires, unless the player clears them manually.
Third-party processors
Third-party cookies are loaded only from processors bound by a data-processing agreement. A full list of third-party cookies is published inside the cookie preferences panel. Each entry shows the processor, the purpose, the retention, and the category.
Browser settings
Browser cookie settings can supplement the cookie preferences panel. Blocking strictly necessary cookies in the browser prevents the verified Come access route from functioning. Blocking analytics and marketing cookies in the browser matches the panel setting.
Cookie reference and how to read it.
The cookie reference below lists the cookies set by Come on a typical signed-in session. The reference is published inside the cookie preferences panel and is updated when the cookie set changes.
Session cookies
Session cookies manage the signed-in session. They expire at the end of the session or after the published session timeout. The session cookie is set by Come directly and is not shared with any third party.
CSRF cookies
CSRF cookies protect form submissions against cross-site request forgery. They are set by Come directly and expire at the end of the session.
KYC cookies
KYC cookies track the KYC state during the verification flow. They are set by Come directly and expire after the verification window. KYC cookies do not carry personal data.
Payment cookies
Payment cookies track the payment flow during deposits and withdrawals. They are set by Come directly and expire after the payment window. Payment cookies do not carry payment data.
Analytics cookies
Analytics cookies measure traffic, page views, and conversion funnels. They are set by Come directly and expire after the published analytics window. Analytics cookies are off by default.
Marketing cookies
Marketing cookies support campaign attribution and retargeting. They are set by Come directly and expire after the published marketing window. Marketing cookies are off by default.