Reference

Your Privacy Policy at c31

Lightning Roulette, Frozen Gems and Kabaddi Crash run through one account flow, and this Privacy Policy explains the data we collect while you browse, join and pay with…

UPI data contextPaytm privacy scopePhonePe recordsCookie choices

Explore the Lobby Read FAQ

How Your Data Stays Within Policy

c31 Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

This Privacy Policy sets out how c31 collects, uses, stores and protects data connected with your account, wallet activity, game sessions and support chats. We collect only the data needed to run account access, verify payments, protect sessions and answer your requests. Access depends on local

1
law and is available where local law permits. For UPI, Paytm, PhonePe and Google Pay, we keep payment references, timestamps, status messages and fraud checks linked to your wallet, not your full bank credentials. We do not sell your account data. Where a service partner helps
2
with hosting, payments, analytics or security checks, we limit access to the task required and keep records for the period needed for legal, tax, safety and dispute handling duties.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT ROUTES

Reach Us About Privacy Choices

You can ask us about your privacy choices before or after opening an account. Our support team can confirm what data is attached to your profile, explain cookie settings, receive correction requests…

Privacy inbox Email us through the privacy address shown inside your account area. Include your registered mobile number or email, the request type and a short description so we can route it without asking for extra data.

Live help chat Use chat when your question concerns cookies, account access, payment references or an active privacy request. The agent can collect the request, confirm identity checks and share the expected next step.

Account request form The account form helps when you want a copy, correction or deletion check. We record the time, request category and verification result so the privacy team can handle it properly.

ACCOUNT SAFETY

Privacy Controls Around Your Account

Our policy is written for the way the account actually works: lobby browsing, table launches, wallet actions, device checks and support contact.

Account data collected

We collect contact details, login identifiers, device signals, location at a broad level and wallet references. These help us keep your account reachable, reduce duplicate access and match payment events to your balance.

Cookie handling

Cookies remember your session, language choice, device state and consent choices. Some are needed for login and fraud checks, while measurement cookies help us understand page errors without reading private messages.

Payment privacy

When you use UPI, Paytm, PhonePe or Google Pay, we store the transaction status, reference code and wallet result. Full bank credentials stay with the payment provider, not in our account database.

Security checks

We monitor login attempts, password resets, device changes and unusual wallet patterns. If a check affects access, we may ask you to confirm ownership before changing account data or releasing records.

Retention periods

We keep data for as long as needed to run your account, meet legal duties, handle disputes and prevent abuse. When data is no longer needed, we delete it or detach it from your profile.

Change requests

You can ask us to correct contact details, update consent choices or check whether older records can be removed. We verify the request first so another person cannot alter your account data.

Privacy Policy Questions Before You Join

These answers explain the most common privacy questions we receive about account data, cookies, payment records and correction requests. They are written to help you decide what to share with us and how to contact us later. If your case involves a legal right or a data request, we may need to verify your identity before responding in detail.

We collect the data needed to create and protect your account, including contact details, login records, device signals, payment references and support messages. We also log game session events so balances and disputes can be checked.

Payment records help us match UPI, Paytm, PhonePe and Google Pay activity to your wallet. We keep reference codes, timestamps, status results and fraud checks, but not your full bank login credentials.

Yes. Send a request through the account form or privacy inbox. We will verify that the request comes from you, then share the categories of data we hold and the method for receiving them.

Cookies keep you logged in, remember choices and help us detect unusual device changes. Some cookies are needed for account safety, while optional measurement cookies help us fix page errors and loading issues.

Access is limited by role. Support can see the data needed to answer your question, payment teams can check transaction references and security staff can inspect risk signals when account safety requires it.

Use the account settings area for simple contact updates, or contact support if the field is locked. We may ask for verification before changing data that affects wallet access or account ownership.

You can ask us to delete or detach data when it is no longer needed. Some records may be kept for legal duties, payment disputes, fraud prevention or account safety before removal is allowed.

Your Privacy Policy at c31

Reach Us About Privacy Choices

Privacy Controls Around Your Account

Account data collected

Cookie handling

Payment privacy

Security checks

Retention periods

Change requests

Privacy Policy Questions Before You Join

01 What account data does c31 collect?

02 Why do you need payment records?

03 Can I ask for a copy of my data?

04 How do cookies affect my account?

05 Who can see my account data inside c31?

06 How can I correct wrong details?

07 When can data be deleted?

Related Pages