Reference

Your Privacy Policy at c3po

c3po brings account creation, Lightning Roulette, Valhalla and local payments into one wallet, so this Privacy Policy explains which data keeps that account flow running.

Account data clarityUPI record contextCookie choicesSupport request route
c3po Your Privacy Policy at c3po
HELP DESK

Privacy Help When You Need It

Privacy requests need a clear route, not a guessing game. Use the channel that matches your situation, and we will ask only for details needed to locate your account and protect it…

Linked email request Write from the email linked to your account so we can match your request without sharing data with the wrong person. Add your username, the device used and the privacy action you want.
Signed-in account chat Use the account chat when you are signed in and need a quick privacy check. Our team can confirm cookie choices, explain verification steps or move a data request to email for records.
Privacy mail queue Send privacy mail for correction, access, deletion or consent questions. We may ask for a fresh login check before we change account records tied to payments or withdrawal history.
SAFETY CHECKS

How Your Data Is Handled

We keep privacy work close to the account systems that create the records. That means wallet checks, login alerts, cookie choices and support cases are handled with role-based access, audit trails and…

Account data

When you create an account, we record details such as name, email, phone number, login device and security events. These records help us verify you, protect access and respond to privacy requests accurately.

Payment records

UPI, Paytm and PhonePe activity can create transaction IDs, timestamps, amount status and settlement references. We use those records to match wallet entries, investigate disputes and support withdrawal checks.

Cookie controls

Cookies help keep your session active, remember privacy choices and detect unusual sign-in patterns. You can change browser settings, though some account functions may need essential cookies to work.

Access security

Before we share, correct or delete eligible data, we may confirm your email, recent login or payment reference. This protects your account from changes requested by someone else.

Retention rules

We keep data only as long as it is needed for account service, legal duties, fraud checks, tax records, dispute handling or security logs. Different record types can have different retention periods.

Request handling

Your privacy request is logged with its date, channel and outcome so we can track the response. If we cannot complete a request, we explain the reason in plain language.

Privacy Questions Before You Join

These answers explain the parts of our Privacy Policy you are most likely to check before opening an account. They cover data categories, payment records, cookies, correction requests, deletion limits and support contact routes. If your question involves a live account, contact us through the signed-in channel so we can confirm it is really you.

We collect data needed to create and protect your account, such as name, email, phone number, login device, security events and support messages. Extra verification may apply when payments or withdrawals need checks.

We use transaction references, status messages and timestamps to match payments with your wallet, handle disputes and support withdrawal checks. We do not ask for your banking password or wallet PIN.

Yes. Send the request from your linked email or signed-in account chat, and include the field you want changed. We may verify your identity before updating records tied to payments or security.

You can ask us to delete eligible data. Some records may need to stay for legal, tax, dispute or security reasons, and we will explain what can be removed and what must remain.

Cookies keep your session active, remember choices and help detect unusual access. You can adjust browser settings, but essential cookies may be required for login, wallet display and account protection.

Only team roles that need the request can access it. We use internal access controls and request logs so your correction, access or deletion query is handled by the relevant support staff.

Yes. Access and eligibility depend on local law and are available where local law permits. Data retention, identity checks and response options may also differ when legal duties apply.