Reference

Open cx660 legal terms for India

Before you open your account, we set out how cx660 handles identity checks, cookies, and record keeping for India.

India accessAccount dataCookiesLocal law
cx660 Open cx660 legal terms for India
CONTACT PATHS

Browse contact paths for legal requests

For legal questions, use the message box inside your account, the email address shown there, or the written form in the footer. Add your registered name, the date, and any UPI, Paytm, or PhonePe reference so we can find the record quickly. If your request affects identity, access, or a change to stored details, we may ask for one extra check before we reply.

Team online

Account mailbox

Send requests from the email linked to your account. We use that address to confirm identity, match your file, and reply with the next step when the request concerns records or access.

In-account form

Use the secure form inside the logged-in area when you want to correct a name, contact line, or payment reference. Add the date and transaction code if the request touches UPI, Paytm, or PhonePe.

Written follow-up

If you need a clearer record, ask for a written reply and keep it with your files. We can return the relevant policy path, the status of your request, and any verification step still pending.

DATA HANDLING

Switch to data handling and security

We handle this policy area by collecting only what we need, keeping access limited, and logging changes against the right account.

Data collection

We collect your name, contact details, device signals, and payment references only when they help with access, fraud checks, account…

Cookies

Cookies remember login state, language choice, and form progress.

Account security

We log password changes, device switches, and failed sign-in attempts so we can spot unusual access.

Record retention

We keep records only as long as needed for support, dispute handling, accounting, and the law that applies to your…

Change requests

To update a detail, tell us exactly what must change, attach proof where asked, and use the email or form…

Contact routing

Requests go to the mailbox, form, or chat path listed inside your account area, so the message stays tied to…

Open answers to account rights questions

These questions cover the most common legal requests we receive from India accounts. The answers focus on access, data use, correction steps, and the way we handle changes when local law sets a limit. If your case is unusual, send the details through the contact path in your account so we can check the file directly.

Send the request from the email linked to your account and mention the period you need. If local law allows the request, we verify the identity match first and then share the relevant record set.

Yes, if the change is allowed in your region and the proof matches your account. We may ask for one extra check, especially when the request affects access, payment history, or the contact line.

We keep account and payment records for the period needed to run the service, handle disputes, and meet legal duties. When that period ends, we remove or anonymise material that no longer needs to stay.

No. Cookies mainly remember session state, language choice, and form progress. Your full account record stays in our secured systems, and you can clear cookies in browser settings if you want a fresh session.

Only staff who need the record for access checks, support, dispute handling, or legal duties can view it. We keep permissions narrow so unrelated teams do not use account data without a work reason.

If local law changes or your region no longer permits access, we may pause the account from that location and adjust the terms shown to you. Any pending request is handled under the rule active at the time.

Use the contact path in your account area, say exactly what should change, and attach proof if we ask for it. We review the file, confirm the match, and then update or explain the reason we cannot.