Reference

How 2coms handles India data

Your account data, KYC records, UPI, Paytm, PhonePe and Google Pay transaction traces, cookie choices, and support messages are covered by this Privacy Policy before you open an…

India data requestsUPI record careCookie choicesAccount security
2coms How 2coms handles India data
CONTACT PATHS

Reach us about privacy

Privacy questions should reach a team that can see the right account trail without asking you to repeat sensitive details.

Email privacy desk Send your request from the email linked to your account and include the topic, such as correction, access, deletion or cookie choice. We use that address to match your profile before discussing account records.
Live chat privacy handoff If you start in live chat, ask for a privacy handoff. The chat team can capture your account ID, request type and preferred reply channel, then route the matter to the privacy desk.
Account ticket trail For a request involving wallet entries, KYC status or device access, open a ticket after logging in. A ticket keeps timestamps, replies and identity checks in one place for later reference.
ACCOUNT SAFETY

How we protect your records

We handle privacy through account-level controls, not broad promises. Each record type has a purpose: identity checks help prevent account misuse, payment references help reconcile wallet activity, cookies keep session choices working…

Data we collect

We collect account details, KYC files, login events, device signals, cookie choices, wallet references and support messages. Game activity may be stored to settle rounds, handle disputes and keep account history accurate.

Payment record handling

UPI, Paytm, PhonePe and Google Pay entries are logged with transaction IDs, timestamps, status and account references. Full banking passwords or app PINs are not requested by us or stored in our systems.

Cookie controls

Cookies help keep you signed in, remember basic choices and detect repeated failed logins. You can adjust browser settings, though some account pages may need session cookies to work correctly.

Access checks

Before we share, correct or delete account records, we verify that the request comes from you. That may involve account email confirmation, recent ticket checks or wallet reference matching.

Retention periods

Some records are kept while your account stays active, and some are retained longer for tax, dispute, security or legal reasons. When retention is no longer needed, records are deleted or de-identified.

Service partners

Limited data may be shared with payment processors, identity checks, hosting services, analytics tools and legal advisers. Each partner receives only what is needed for the relevant task.

Privacy answers for your account

These answers explain common privacy requests connected with your account, wallet, cookies and support history. They are written for India access, with local law and account verification in mind. If your request involves a specific payment, game round or login event, keep the date, amount reference and device details ready so we can trace the record faster.

We collect details needed to create and secure your account, such as name, contact details, age check data where required by law, login records, device signals, wallet references and support messages.

We use payment references to match deposits, process withdrawals, resolve failed transfers and keep your wallet ledger accurate. We do not ask for your banking password, app PIN or full card credentials.

Yes, you can request a copy of account records we hold about you. We first verify account ownership, then provide data that can be shared under applicable law and security rules.

You can ask us to correct inaccurate profile details. Some changes, such as name or KYC document updates, may require proof before we update the record and reflect it across account systems.

You may request deletion, and we will assess it against legal, tax, security and dispute-retention duties. Records no longer needed for those purposes are deleted or de-identified where practical.

Cookies can remember session status, language choices, security checks and basic site preferences. You can manage them through your browser, but some logged-in areas need cookies to function.

Use the email linked to your account or open a logged-in ticket. Include the request type, date range and any relevant UPI, Paytm, PhonePe or Google Pay reference.