Reference

Open Your Privacy Choices

The winmatch Privacy Policy explains how we collect account data, payment references from UPI, Paytm, PhonePe and Google Pay, device signals, cookies, and support messages before you open…

India privacy termsCookie controlAccount data requestsUPI and wallet records
winmatch Open Your Privacy Choices
CONTACT ROUTES

Check Help Paths For Privacy

Privacy requests should reach the team that can act on account records, not a generic chat queue.

Privacy email Email [email protected] from your registered address for data access, correction, deletion, or cookie questions. We may ask one verification step before we share account records or change stored details.
Account chat Use in-account chat when you can still log in and want a quicker privacy ticket. Chat agents can tag the request, confirm your account ID, and move it to our data team.
Security escalation If you think your login, mobile number, or payment reference has been exposed, contact support with the time, device, and payment method involved. We prioritise account access checks and password resets.
ACCOUNT CARE

Browse Our Data Practices

Your Privacy Policy rights sit beside the everyday account checks we run in the background. We separate payment references from gameplay history where practical, restrict staff access by role, and keep logs…

Data we collect

We collect account profile data, login signals, device details, cookie IDs, support messages, KYC files where required, and payment references. We avoid asking for data that is not needed for account or legal checks.

Cookie use

Cookies help keep you signed in, remember privacy choices, detect repeated failed logins, and measure page errors. You can clear or block cookies in your browser, though some account actions may need them.

Payment records

UPI, Paytm, PhonePe and Google Pay references are stored to match deposits, withdrawals, refunds, disputes, and fraud checks. We keep payment tokens and reference IDs separate from full account notes where practical.

Account security

We use password controls, session checks, device signals, staff role access, and audit logs to reduce unauthorised viewing. If your mobile number changes, we verify ownership before changing privacy-linked contact details.

Retention period

We keep records while your account is active and for a limited period after closure when law, disputes, tax checks, fraud checks, or payment reconciliation require it. Data not needed is removed or anonymised.

Your requests

You can ask to access, correct, export, restrict, or delete personal data. Some records may be retained when law or active disputes require it, and we will explain the reason in our response.

Discover Privacy Answers Before Joining

These answers explain how the Privacy Policy works when you create an account, add payment details, contact support, or ask us to change stored records. Keep your registered email and mobile number active so we can verify privacy requests safely. If a request affects wallet records, KYC checks, or access logs, we may need extra time to match the account trail correctly.

It covers account profile details, contact data, login activity, device signals, cookie IDs, payment references, KYC files where required, support chats, and request history linked to your winmatch account.

We keep UPI, Paytm, PhonePe and Google Pay reference IDs to match wallet activity, verify withdrawals, handle refunds, check disputes, and investigate suspicious account access without storing more payment data than needed.

Yes. Email [email protected] from your registered address or raise an in-account chat ticket. After verification, we can share the main account records we hold, subject to legal and security limits.

Send the corrected detail through account chat or privacy email and confirm your identity. For mobile number, email, or KYC changes, we may ask for proof before updating the account record.

You can request deletion, and we will remove data that is no longer needed. Some records may stay for legal duties, payment disputes, security checks, or fraud prevention until retention needs end.

Cookies keep your session active, remember privacy choices, help detect repeated failed logins, and show us page errors. You can manage cookies in your browser, but account actions may work differently.

Only authorised support, security, payment, or data staff can handle your request. Access is role-based, logged, and limited to what is needed to verify, answer, or complete the privacy action.