Reference

Open with privacy terms for India

Your winexch24 account connects login details, KYC checks, cookies, and UPI, Paytm or PhonePe payment records in one privacy flow, so you can see why each data point…

Account dataKYC checksCookie choicesUPI privacy
winexch24 Open with privacy terms for India
CONTACT PATHS

Check privacy help from our team

Privacy requests need a clear route because your account data cannot be changed from a public message.

Privacy email Send your account email, mobile number and a short privacy request. We use that route for access, correction, deletion and consent questions, then reply after checking the account holder.
Live chat handoff If you contact chat first, ask for the privacy queue. The agent may confirm your last login details and payment reference before escalating, so personal data is not discussed with the wrong person.
Document request form For KYC or withdrawal privacy questions, upload only the file we ask for through the secure form. Extra screenshots can expose more data than needed, so we remove unrelated attachments.
ACCOUNT CARE

Browse the controls behind your data

We handle privacy as an account process, not as a hidden page. Each collection point has a purpose: login security, KYC matching, wallet reconciliation, device protection, support history, or legal record keeping.

Data collection

We collect account details, login signals, device data, KYC files and payment references when they are needed for access, identity checks, wallet records, support handling or legal duties.

Cookie choices

Cookies help keep you signed in, detect unusual access and remember site preferences. You can manage browser settings, though blocking some cookies may affect login checks and account security prompts.

Account security

Password resets, one-time codes and device checks create security records. We use those records to confirm that a privacy request comes from you and not from another person.

Payment records

UPI, Paytm and PhonePe references are stored with wallet activity so deposits, withdrawals and disputes can be matched. We do not store more payment data than the account process requires.

Retention window

Some records must remain for fraud checks, pending withdrawals, tax needs or legal requests. When those reasons end, we delete, mask or reduce data according to the account status.

Change requests

You can ask to access, correct, restrict or delete personal data. We may need identity proof first, and some changes cannot be made while a payment or dispute is open.

Explore privacy answers before you join

This FAQ explains the privacy steps you are most likely to ask about before opening or using your account. The answers focus on account data, payment references, KYC files, cookies, access requests and deletion requests. If your request depends on local law, we will explain what can be done for your location and what records must remain for compliance or account safety.

We collect account details, contact data, login records, device signals, KYC files, wallet activity and support messages. Each type is linked to account access, security checks, payment matching or legal record keeping.

KYC data helps confirm that the account belongs to you before withdrawals, account changes or privacy requests. We use it for verification, fraud checks and legal duties that may apply in India.

We use payment references to match deposits, withdrawals, refunds and disputes to your wallet. The record helps support verify a transaction without exposing more payment data than the request needs.

Yes, you can ask us to correct account details that are incomplete or inaccurate. We may request proof before changing KYC fields, mobile numbers, payment references or details linked to withdrawals.

You can request deletion, and we will remove data where allowed. Some records may need to remain for pending payments, fraud checks, tax duties, disputes or other legal retention reasons.

Cookies record login sessions, device checks and site preferences. You can adjust browser settings, but some account security features may ask for extra verification if key cookies are blocked.

Only staff who need to handle your request can see it. Access is limited for privacy email, chat escalation, KYC checking, payment matching and any required legal response.