Reference

Your Privacy Policy at v60e

This page sets out how we handle account data, device signals, cookie traces and wallet records for India accounts.

Data useCookie controlIndia accessWallet records
v60e Your Privacy Policy at v60e
CONTACT PATHS

How to Reach Our Team

For privacy requests, use the route that matches your account status. Logged-in accounts can raise a request from the help area, while locked accounts can send the same details through the support…

Account panel If you can still sign in, send your correction or deletion request from the account panel. That gives us the registered details, the request time and the message trail we need to verify ownership quickly.
Support form When access is limited, use the support form and state exactly which detail you want changed. Attach the registered contact and any payment reference linked to the query so we can match the record.
Privacy desk For urgent privacy concerns, message the privacy desk with your registered name, contact number and the exact change you want. We route the request to the team that handles retention and data access.
TRUST CONTROLS

How We Handle Your Data

We keep personal data handling narrow: collect only what is needed for sign-up, session safety, payment reconciliation and service replies.

Collection limits

We only ask for the details needed to open, secure and service your account, plus the payment references needed to reconcile a deposit or withdrawal. Unneeded fields are not part of our standard flow.

Cookie control

Cookie settings help us remember your language choice, device session and form progress. If you clear them, some preferences may reset, but you can still sign in again with your account details.

Login checks

Device logs and sign-in timestamps help us confirm whether access came from you or from an unknown device. This reduces misuse and helps us answer access disputes with a clear trail.

Retention windows

We keep records only for the time needed to run the account, answer disputes and meet legal duties. After that, the data is archived or removed under our retention rules.

Change requests

If you want a copy, correction or deletion request, send the exact change and the reason. We may ask for proof that the request came from the account holder before acting.

Contact record

Keep your message simple: account name, registered contact, request type and any payment reference linked to the issue. That helps us route the case to the right privacy contact faster.

Privacy Policy Questions You May Ask

These answers cover what we collect, why we keep it and how you can contact us. If local law permits access in your area, the same policy applies to sign-up, sign-in, payment references and support messages. We keep the wording short so you can check it before you send any request, and we may ask for a verification step before making a change.

We ask for the details needed to create and secure your account, plus the contact and payment references that help us match your records. We avoid extra fields unless a legal or support step needs them.

Cookie data helps us remember your session, language choice and form progress. It also helps us spot unusual access patterns and reduce repeated sign-in prompts on the same device.

We use those references to match account activity, settle queries and confirm the source or destination of a transfer. The records stay tied to the transaction trail and are not used for unrelated purposes.

We keep records only as long as needed for account running, dispute handling and legal duties. After that period, they are archived or removed according to our retention rules.

Send the exact detail you want corrected, the reason and the registered contact linked to the account. If we need more proof, we will ask for it before making the change.

Use the account panel, the support form or the privacy desk, depending on your access. Include your registered name and any payment reference so we can route the request quickly.

Yes. Where local law permits, the service and this policy apply to your account. If a region is restricted, we follow the local rule set and the access path shown to you.