Reference

What this legal page covers

This page explains how we handle access, data use, cookies, account records and request handling on 3c1.

IndiaUPIPaytmPhonePe

Local law and account access

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

3c1 serves India audiences, but your ability to access any service depends on local law and is available where local law permits. If a local rule conflicts with what appears here, the local rule controls. We may ask for account details, payment records or identity checks

1
when needed to confirm a request, settle a dispute or complete a correction. We keep only the records needed for service, fraud checks and audit duties where they apply. If you send a legal request, we use the contact paths below and respond after we verify
2
the account. This wording can change when law, court orders or payment-network rules change.

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

CONTACT PATHS

Legal contact routes for your account

For questions on access, correction, closure or record handling, use the channels below.

Email request Send the request from the email linked to your account and include the change you want, the reason for it and any reference number you already have. We use that to locate the record and confirm the next step.

In-app form Use the account form when you want a correction, deletion query or access question. Add the same contact details you use on 3c1 so we can match the request with the right profile without back-and-forth.

Written postal request If you need to send a signed request, write the full name on the account, the date and the exact change you want. We review postal requests the same way we handle digital ones, after identity checks.

HANDLING STANDARDS

How we handle legal records

We keep legal records tied to the purpose they serve: access checks, dispute handling, security and any duty that applies.

Data use

We use your account details only to run the service, answer requests, manage disputes and meet duties that apply. We do not write the record for unrelated purposes, and we limit access to staff who need it.

Cookies

Cookies and similar tags keep you signed in, remember basic settings and help us spot unusual access. You can clear them in your browser, though some pages may ask you to sign in again after that.

Account security

We expect you to keep your password private and use a device lock where possible. If you think another person has used your account, tell us at once so we can freeze access and check recent activity.

Retention

We keep records for as long as needed to run the account, resolve a dispute, meet legal duties or meet financial checks tied to a request. After that, we delete or mask what we no longer need.

Change requests

To change personal details, send the exact update and the reason for it. We compare the request with the account record, apply the change where allowed and tell you what was changed or why we could not do it.

Access checks

When you ask for access, we may confirm the email, phone number or a recent transaction reference before we share anything. That protects your record and keeps the response limited to what we can lawfully disclose.

Legal questions you may ask

These questions cover access, correction, deletion, cookies and contact steps. We answer only after we verify the account and confirm what local law allows us to share. If your request involves a payment trail, include the UPI, Paytm or PhonePe reference you still have. That shortens the check and helps us match the right record.

It applies to account holders and account requests for India audiences. If local law changes or a court order affects a service, that rule takes priority and we adjust the position here.

Yes. Send the request from the contact tied to your account, and we will confirm identity before we share what local law allows. If a payment record is involved, include the UPI, Paytm or PhonePe reference.

Tell us exactly what needs to change, why it is wrong and which account detail proves the right version. We check the record, update it where allowed and confirm the result through the same contact route.

We keep records only for the period needed to run the account, settle disputes, meet tax or audit duties and protect against misuse. When that reason ends, we delete or mask the parts we no longer need.

Cookies mainly help the site remember session state and recognise a return visit. They do not replace identity checks, so we still confirm the account before any legal request is processed or any record is shared.

Use the support path that matches your issue and include your account name, the date, the reference number and a plain description. We review the record, reply after verification and explain the next step we can take.

What this legal page covers

Legal contact routes for your account

How we handle legal records

Data use

Cookies

Account security

Retention

Change requests

Access checks

Legal questions you may ask

01 When does this legal page apply?

02 Can I ask for the data you hold?

03 How do I ask for a correction?

04 How long do you keep records?

05 Do cookies affect my legal request?

06 Who should I contact about a dispute?

Related Pages