Reference

Privacy Policy for your c2fo account

c2fo keeps your account, wallet, payment context and lobby activity under one Privacy Policy so you can see what we collect, why we use it and how to…

Account dataCookie choicesUPI contextPrivacy contact
c2fo Privacy Policy for your c2fo account
CONTACT ROUTES

Privacy contact paths we monitor

Privacy requests need a clear route, so we keep account, email and support channels separate from general lobby questions. Tell us what you want changed, checked or removed, and include the mobile number or email tied to your account. We may ask for identity confirmation before acting, because privacy changes can affect wallet records, login access and withdrawal checks.

Team online

Email privacy desk

Write to [email protected] for access, correction, deletion or data-use questions. Include your registered email or mobile number, but do not send full card details, UPI PINs or one-time passwords.

Account message centre

Use the message centre after login when your request relates to wallet activity, KYC records or session history. That route lets us match your request to the account without asking for extra public details.

Support chat handoff

If you start in chat, ask for a privacy handoff and we will move the request to the right queue. Chat can confirm receipt, but document changes may need email follow-up.

DATA HANDLING

Six ways we handle account data

Our Privacy Policy is written around the moments where your data actually moves: account creation, login, wallet activity, game sessions, support contact and legal record keeping.

Account creation

When you join, we collect details needed to create and secure your account, such as name, mobile number, email address…

KYC and withdrawals

Verification documents and withdrawal records help us confirm that a payout request matches the account holder.

Payment context

UPI, Paytm, PhonePe and Google Pay references may appear in your wallet history, transaction status or support messages.

Cookies and devices

Cookies help keep you signed in, remember basic preferences and detect unusual access.

Game session records

Records for Speed Baccarat, Cherry Blast, Football Strike, Cash or Crash, Bingo and Fishing War may include session time, stake…

Retention and deletion

We delete or de-identify data when it is no longer needed, unless law, fraud prevention, tax records or disputes require…

Privacy Policy questions before you join

These questions explain the privacy choices you can make before and after opening an account. They focus on data access, correction, cookies, payment context, security checks and contact routes. If your request depends on local law, we will tell you how that law affects the next step.

We collect data needed to run your account, such as name, mobile number, email address, login records, device signals, KYC documents, wallet activity and support messages. We use it for account access, security and legal duties.

Payment context helps us match deposits, withdrawals, refunds and support requests to your wallet. We may store transaction references and status details, but we do not ask for or store your UPI PIN.

Yes, you can ask us to correct data that is wrong or outdated. We may request identity confirmation first, especially when the change affects your mobile number, email address, KYC record or withdrawal route.

You can request deletion through the privacy desk. Some records may need to stay for legal, fraud prevention, tax or dispute reasons, and we will explain what can be removed and what must be retained.

Cookies support login sessions, basic preferences, fraud checks and account security. You can manage cookies in your browser, but blocking required cookies may interrupt login, wallet checks or support verification.

Access is limited to staff or service partners who need those records for verification, withdrawal checks, fraud prevention, legal duties or support resolution. We do not use KYC documents for unrelated promotion.

Email [email protected] or use the account message centre after login. Include the account email or mobile number, describe your request clearly, and avoid sharing passwords, one-time passwords or payment PINs.