Reference

6c2 Privacy Policy for India Accounts and Data Use

When you use 6c2 from India, we explain how we handle your account data, cookies, and request records.

Account DataCookie UseIndia AccessChange Requests
Explore Lobby Read FAQ
6c2 6c2 Privacy Policy for India Accounts and Data Use
REQUEST CHANNELS

Ways To Reach Us For Data Requests

If you want access, correction, or deletion where local law allows, use the message path inside your account or write from the email tied to that account.

Email Send privacy requests from the email tied to your account, and we use that match to confirm who is asking before we touch access, correction, or deletion records where local law permits.
In-Account Message If you are already signed in, use the message path in your account area. It keeps the request attached to the right profile and gives us the cleanest trail for follow-up.
Verification Reply When we need extra proof, we may ask for a short reply with the exact details we need. That extra step protects your record from changes made by someone else.
STORAGE AND ACCESS

Cookies, Security, and Record Handling

We keep the policy practical: collect only what is needed, store it only for the time needed, and limit who can open it.

Data Scope

We keep the details needed to run your account, confirm transactions, and handle disputes. Anything that is not needed for those tasks stays out of the core record and is not asked for again.

Cookie Use

Cookies help hold your session, remember language choice, and reduce repeat checks on the same device. They also help us spot unusual access and protect your login while you move through the site.

Access Control

Only staff who handle account care, payment checks, or request handling can see the related records. Access is limited by role, so a support task does not open the full account file.

Retention

We keep account and payment records only for as long as needed for service, dispute handling, and legal duties. After that period ends, the records are removed or archived under the rule that applies.

Change Requests

If a detail is wrong, ask for a correction from the email or message channel linked to the account. We verify ownership first, then update the field that can be changed.

Contact Route

For any privacy concern, use the account-linked channel first so we can confirm identity quickly. If local law limits the request, we will tell you what we can change and what must stay.

Questions About Your Privacy Rights

The questions here cover the requests we see most often: what we collect, why cookies are used, how you can correct a record, what may stay on file, and how to reach us. We answer from the account-linked channel whenever possible, because that keeps the request attached to the right record and lets us confirm identity without extra back-and-forth. If local law changes the result, we follow that rule and explain the limit.

We collect the details you enter for the account, login and device signals, and the payment trail tied to UPI, Paytm, PhonePe, or Google Pay so we can run the record and check disputes.

Cookies keep you signed in, remember language and session settings, and help us spot unusual access. They also reduce repeat checks on the same device without changing your account details.

Yes. Send the request from the address linked to your account or through the message path inside it. We verify ownership first, then change the record where the change is allowed.

You can ask, and we will check the request against local law and the records we must keep for account, payment, dispute, or tax handling. If something must stay, we explain why.

Only the staff and service partners who need the data for account care, payment checks, fraud checks, or legal duties can access it. We do not open the file more widely than that.

Use the account-linked channel or write from your registered email. That lets us confirm the request faster and protects your details from being changed by the wrong person.

Related Pages

Register Shark Attack About Us Rainbow Riches