Reference

3c1 Privacy Policy for India, UPI, Paytm, PhonePe

Before you open an account, we set out what we collect, why we need it, and how long we keep it.

India-first handlingAccount data in scopeCookie controlRequest access

What This Privacy Policy Covers

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

We collect only the data needed to open and run your account, confirm contact details, process deposits or withdrawals, answer privacy requests, and spot abuse or duplicate use. If you share UPI, Paytm or PhonePe details, we keep the records needed to match the payment trail

1
and handle disputes or reversals. We also keep cookies and device signals to remember login state, reduce repeated checks, and protect the account from unauthorised access. Where local law requires a different rule, we follow that rule in India or any other permitted region. If a
2
record can be changed or deleted, we do it after we confirm your identity and check the retention duty tied to that record. We do not keep data longer than needed for the stated purpose.

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

CONTACT ROUTES

How to Reach Us About Data

If you want a copy of what we hold, need a correction, or want to ask about a payment record, use the contact paths below.

Email us Send the address linked to your account, the change you want, and any date or payment reference involved. We use that to locate the right record and answer within our usual support window.

Support form Use the form from your account when you want a correction, deletion request, or a copy of stored data. Add a short note so we can match the request with the right profile and verify it.

In-account message If your request touches a UPI, Paytm or PhonePe record, add the reference number and time window. That helps us check the trail, confirm the account holder, and update you without unnecessary back-and-forth.

STORAGE RULES

How We Keep Records Safe

We treat privacy work as part of account care, not a side task. Cookies help us remember login state and keep sessions stable, while device and browser signals help us spot misuse.

Data minimisation

We ask for the details that let us open, verify, and service your account. If a field is not needed for that purpose, we do not ask for it and we do not keep it longer than needed.

Cookies and local storage

Cookies help us keep you signed in, remember language settings, and reduce repeated checks on return visits. You can clear them in your browser, though some page settings may need to be set again.

Account security logs

We record login time, device type, and key actions on the account so we can spot unusual access and answer support queries. Those logs are read only when we need them for security or service work.

Retention periods

We keep records only for the period needed for account use, dispute handling, tax or legal duties, and abuse checks. Once that period ends, we delete or block access in line with our retention rules.

Correction requests

If your contact details, identity data, or payment reference is wrong, ask us to fix it from your registered channel. We will confirm the request and update the record where the law allows.

Deletion checks

When you ask us to delete data, we first check whether any part must stay for fraud control, payments, or legal duties. Anything not needed is removed or detached from active use.

Privacy Policy Questions You May Ask

These answers cover the privacy choices you make on 3c1, what we retain for account service, and how you can ask for a change where local law allows. If your request mentions UPI, Paytm or PhonePe, include the time and reference so we can match the record quickly. We aim to keep the process plain: verify the account, check the duty attached to the data, and reply through the contact route you used.

We collect the details needed to create and secure the account, confirm contact routes, and process requests you send us. That can include login data, device markers, and payment references when a transaction needs to be matched.

Cookies help us remember your session, reduce repeated checks, and keep settings such as language or page state in place. They do not replace your account controls, and you can clear them through your browser.

Yes. Send a request from your registered contact path and we will confirm your identity before sharing the data set we are allowed to disclose. Some records may stay back if law or payment duties require them.

Payment records let us match deposits or withdrawals, spot errors, and answer disputes. If you mention UPI, Paytm or PhonePe, include the reference number and time so we can find the right trail.

We verify the request against the account, the contact route, and any other proof we need for safety. If the request is about a payment trail, we may ask for a screenshot or reference to avoid mistakes.

We keep data only as long as the purpose, legal duty, or dispute window needs it. After that, it is deleted or restricted from active use, subject to the record type and local law.

3c1 Privacy Policy for India, UPI, Paytm, PhonePe

How to Reach Us About Data

How We Keep Records Safe

Data minimisation

Cookies and local storage

Account security logs

Retention periods

Correction requests

Deletion checks

Privacy Policy Questions You May Ask

01 What data do you collect when I open an account?

02 Why do you keep cookie data?

03 Can I ask for a copy of my stored data?

04 How do you handle payment records for UPI, Paytm or PhonePe?

05 How do you verify a privacy request?

06 How long do you keep my data?

Related Pages