Reference

Open wincash Privacy Policy for India

This page explains how wincash handles your account data, device data, cookies, and payment records when you open an account or ask us for help.

Account dataCookiesPayment recordsIndia law
wincash Open wincash Privacy Policy for India
REQUEST CHANNELS

Browse contact paths for policy requests

If you want to ask for access, correction, or deletion where allowed, use the contact path linked to your account.

Account form Open the support form inside your account and send the exact privacy request you want. That path keeps the request tied to the right profile and helps us confirm the record before we act.
Secure message Use the message route shown in your account area when you need a copy of data, a correction, or a deletion request. We use that channel because it is easier to verify and track.
Identity check If you are locked out, send the proof we ask for so we can confirm you before changing account details. That step protects your data from being changed by the wrong person.
CONTROLLED HANDLING

Switch on the controls we use

We keep privacy work tied to the least data needed for account access, fraud checks, support, and legal retention.

Data scope

We collect the details you enter, the device signals your browser sends, and the transaction records needed to run your account. We avoid holding extra fields that do not support the service or a legal duty.

Cookie use

Cookies help us keep you signed in, remember your settings, and spot unusual login behaviour. They also let us see whether the page loads correctly on your device without storing more than we need.

Security checks

We use login history, session markers, and verification steps to protect your account from unauthorised access. If something looks unusual, we may ask you to confirm the request before the account changes move ahead.

Retention window

Records stay only for the period needed to run the account, resolve a dispute, complete a security check, or meet a legal duty. When the reason ends, we remove or archive the record as required.

Change requests

You can ask us to correct, access, or delete data where local law allows it. We review the request against the account record, then confirm what can be changed and what must stay for legal reasons.

Contact trail

Every privacy request gets a clear path so you know where it sits and what action is next. If we need more details, we ask through the same secure channel rather than using an open message thread.

Check common privacy questions

These questions cover the parts of the policy you are most likely to use: what we keep, why we keep it, how you can ask for a copy or correction, and how long records may remain in place. If your case depends on local law, we follow the rule that applies to your region and proceed only where local law permits.

We collect the details you enter, device and session signals, and account activity needed to verify access and keep the wallet record accurate. We do not ask for extra data unless a check or legal duty requires it.

Cookie data helps us keep you signed in, remember your settings, and detect unusual access patterns. It also supports page loading and security checks, and you can clear cookies in your browser if you want a new session.

Yes, where local law allows. Send the request through the secure contact path in your account, and we will verify that it is really you before we share the record or explain what we hold.

Yes. If your name, contact detail, or another field is wrong, send the correction request through the secure route. We check the record, confirm your identity, and update the file when the change is allowed.

We keep records only for the time needed to run the account, handle a dispute, complete a verification step, or meet legal retention duties. After that, the record is removed or archived as required.

We may share data with service partners who help us process account tasks, verify requests, or keep the system running. They receive only the data needed for that task and must use it for that purpose alone.

Use the secure message path in your account or the support route shown there. If you cannot sign in, send the identity proof we ask for so we can confirm the request and continue.