Reference

Open cx660 Privacy Policy with clear terms

We set out what account details, device signals and cookie choices we keep, why we keep them, and how they help with sign-in checks, withdrawal verification and fraud…

Data useCookie choicesLocal lawAccount access
cx660 Open cx660 Privacy Policy with clear terms
CONTACT PATHS

Browse contact paths for privacy requests

If you want a privacy change, use the path that matches the request so we can verify it faster. The email route suits access, correction and deletion asks, while the in-account form suits record checks tied to your login. If you cannot enter the account area, send the request from the email linked to it and we will move from there.

Team online

Email us

Send the request from the email linked to your account and include the detail you want checked, such as a contact record, cookie choice or transaction trace. That helps us confirm identity before we make any change.

Use account form

Open the form inside your account to ask for access, correction or deletion where local law permits. Tell us plainly what should change, and we will reply with the next step.

Reply in thread

If a request needs more context, reply in the same thread so the record stays tidy. We keep one trail for each case, which helps us match your question with the right data.

DATA CARE

Switch between data, cookies and security

We keep collection narrow: only the records needed for login, service replies, payment traces and site safety.

Data collection

We collect the details you enter, the contact route you use and the device signals needed to protect access.

Cookie use

Cookies remember session state, page choices and a few security flags.

Access checks

Login attempts, device history and session timing help us spot unusual access.

Payment traces

When you use UPI, Paytm, PhonePe or Google Pay, we keep transaction references, timestamps and status flags needed for reconciliation…

Retention

We keep records for as long as needed to run your account, settle disputes or meet duties that apply in…

Change requests

If you want access, correction or deletion where local law permits, contact us from the address tied to your account…

Open answers on privacy rights

These answers explain how your data is used, how you can ask for changes and what we need before we act. The process is tied to your account and the law that applies to your location, so we can confirm the right record without asking for extra detail. If something is missing, reply from the same email we already have on file and we will continue there.

We keep the details you enter in forms, your login history, device signals and the contact route you use. If a payment trace is needed, we also keep the reference tied to that action only.

Cookies help remember session state, language choice and a few security flags. They also let the page load with the same account context on your next visit, unless you clear them in the browser.

Yes. Send the request from the email linked to your account or from the in-account form, and we will confirm what we can share after checking identity and any local-law limits.

If you use UPI, Paytm, PhonePe or Google Pay, we may keep a narrow transaction trail for reconciliation, dispute handling and support replies. We do not keep extra payment detail beyond that purpose.

We keep records only for the time needed to run the account, handle disputes, meet duties that apply in India or answer a valid request. After that, we remove or anonymise them.

Write from the address linked to your account, name the record that needs change and say whether you want correction or deletion where local law permits. We will reply with the next step.

Reply in the same email thread or use the in-account form again, and we will pick up the existing case. That keeps the trail together and helps us match the request to the right record.