Reference

Open cmsatta Privacy Policy for India

This page explains what we collect when you open an account, move through the lobby, or use UPI, Paytm or PhonePe.

Account detailsDevice signalsCookiesPayment records

Explore how data use works

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

We collect only what is needed to open your account, verify sign-in attempts, process wallet activity and answer requests. That can include your name, contact details, device and browser signals, session logs, cookie data and payment references from UPI, Paytm or PhonePe. We use that data

1
to keep access working, prevent misuse, settle disputes and meet record-keeping duties. We may share limited details with service providers that help run payments, hosting, verification and messaging, but only for those tasks. If local law limits any part of access or use, we follow that
2
rule. When you ask for correction or removal, we may keep a small record if we need it for security, fraud checks or legal duty. Retention periods depend on the account action, the support case and any rule that asks us to keep a log longer.

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

REQUEST ROUTES

Open contact paths for privacy requests

If you want access, correction, deletion or a limit on processing where local law allows it, reach us through the contact route in your account.

Email Send the address on your account and say whether you want access, correction or removal. We use it to match your request with the right record and may ask one check step before replying.

Account message If you can sign in, send the request from your account area. That keeps the thread linked to your profile, wallet logs and session records, which helps us answer faster.

Signed form When you cannot access the account, send a signed form from the contact page. We will check the details, confirm ownership where needed and share the next step if the law allows the change.

HANDLING STEPS

Switch to our handling steps

We keep privacy work tied to the account flow, not to loose copies of your data. Cookies remember sign-in state and basic choices, logs help us spot unusual access, and payment records…

Collection

We collect account fields, device signals and cookie data only when they help with sign-in, wallet action or support. We avoid storing extra text that does not serve a clear account purpose.

Cookies

Cookies keep the session moving, remember language choices and help us spot repeated sign-ins from the same device. You can clear them in your browser, though some pages may then ask you to sign in again.

Security

We use password checks, session timeouts and device flags to reduce account misuse. If a sign-in looks unusual, we may ask for a quick confirmation before the account lets you proceed.

Retention

We keep records for as long as the account, support case or payment check needs them, then remove or archive them under our retention rules. Some logs stay longer only when law or dispute handling requires it.

Change requests

If your name, contact details or other stored field changes, send a request from the contact route. We will check the record, update what we can and explain anything that must stay as is.

Contact

For any privacy question, reach the address or form linked in your account. We respond in the order requests arrive and keep a record of the reply for audit and follow-up.

Browse common privacy questions

These answers cover what we collect, why we keep it and how you can ask for change. If a request touches payment logs, sign-in records or identity checks, we may need a short confirmation before acting. Where local law limits access, correction or removal, we will say so plainly and keep the explanation tied to your request.

We keep the details you give when you open an account, plus device signals, session logs and cookie data needed to run sign-in, handle support and check wallet actions. We do not keep extra details without a clear reason.

Cookies remember your session state, reduce repeated logins and help us spot device changes that need another check. They also store small settings such as page choice so the account opens the way you left it.

Yes. Use the contact route in your account or the linked email address and ask for access. We may confirm your identity first, then share the records we can release under the law and our security rules.

Yes, where local law allows it. Tell us what should change, and we will check the record, update what we can or remove what we can no longer keep, while retaining anything needed for disputes or legal duty.

We keep payment references only as long as they are needed for wallet checks, dispute handling, fraud checks or a legal duty. After that, they are removed or archived under our retention schedule.

Contact us through the email or form shown in your account area. If you cannot sign in, use the signed request route and include enough detail for us to find the record.

Open cmsatta Privacy Policy for India

Open contact paths for privacy requests

Switch to our handling steps

Collection

Cookies

Security

Retention

Change requests

Contact

Browse common privacy questions

01 What data do you collect from my account?

02 Why do you use cookies?

03 Can I ask for a copy of my data?

04 Can I ask for deletion or correction?

05 How long do you keep payment records?

06 Who can I contact about a privacy request?

Related Pages