Reference

Privacy Policy for India Accounts

This Privacy Policy tells you how winclash handles the data you share when you open an account, verify access, use UPI, Paytm or PhonePe, set cookies, contact support…

India account dataUPI privacy contextCookie choicesSupport contact path
winclash Privacy Policy for India Accounts
CONTACT ROUTES

Privacy contact paths for your account

If your privacy question is personal to your account, contact us from the same email or mobile number you use on winclash so we can match the request safely.

Privacy email Write to [email protected] with your account email, mobile number and a clear request. We use that channel for access copies, correction requests, deletion queries, cookie questions and follow-up on previous privacy replies.
Signed-in chat Open account chat after signing in when your request involves wallet references or KYC files. That route helps us confirm the request comes from you before we discuss any personal record.
Help ticket If you cannot access the account, send a ticket from the help page with a reachable email and recent payment reference. We will ask limited checks before discussing any personal data.
DATA CONTROLS

Data controls behind Crash X sessions

The policy is written around the way our account flow works: sign-in, wallet records, cookies, KYC checks, support messages and security events.

Data handling

We collect only details tied to account creation, verification, wallet activity, fraud checks, support contact and site performance. Sensitive files are kept in restricted systems, and internal access is limited to staff handling that task.

Cookie use

Cookies help keep you signed in, remember display choices, measure site errors and protect sessions from repeated failed access attempts. You can change browser cookie settings, but some account screens may then behave differently.

Account security

Password resets, device signals and login checks create security logs. Those records help us spot unauthorised access, recover your account when you contact support, and protect wallet actions linked to UPI, Paytm or PhonePe.

Retention periods

Retention periods depend on the record type. Support chat may close sooner than KYC or transaction records, because payment tracing and legal duties can require a longer archive before deletion is available.

Service providers

We share data only with service providers needed for payments, verification, hosting, analytics, fraud control and customer support. Contracts limit their use of the data and require security controls for the work they do.

Change requests

To request a change, use the privacy email or signed-in chat and state what should be updated. We will check identity, confirm what changed, or explain why a record cannot be altered.

Privacy Policy questions before you join

These answers focus on the privacy choices you are most likely to need after opening an account: data access, correction, deletion, cookies, payment references and contact routes. They do not replace the full policy, but they show how we handle common requests in India and what we may ask from you before sharing personal data. If your question is specific, contact us with enough detail to locate the right record, and keep your account email current so replies do not miss you.

The policy covers account details, contact data, device signals, login records, cookie data, wallet references, KYC files when required, and support messages. It also covers how those records are used, stored, shared and deleted.

Payment references help match deposits and withdrawal checks to your account, resolve failed transfers and keep audit records. We do not collect your full banking credentials; we store the transaction detail needed for account support.

Yes. Email [email protected] or use signed-in chat with your account email and mobile number. We will verify your identity first, then share the records we can provide under applicable law.

Send the corrected detail and the reason for the change through the privacy email or signed-in chat. For fields linked to KYC or payments, we may request proof before updating the account record.

You can request deletion, and we will erase records where the law allows it. Some transaction, fraud-control or KYC records may need to stay for a set period before deletion can happen.

Cookies keep sessions active, remember language and display choices, measure technical errors and support security checks. You can manage cookies in your browser, but blocking essential cookies may affect sign-in and account pages.

Use [email protected] for policy questions, or signed-in chat when the request relates to your account. Include your email, mobile number and a short description so we can find the right record.