Reference

Your Privacy Policy starts here

zenbet uses this Privacy Policy to explain what we collect when you open an account, verify your profile, use UPI, Paytm or PhonePe, and contact our team.

Account data clarityCookie choicesUPI record handlingContact route
zenbet Your Privacy Policy starts here
CONTACT PATHS

Reach us about privacy requests

Privacy questions need a clear route, not a maze. Use the contact method linked to your account email so we can confirm the request belongs to you before changing, sharing or deleting any record. If your concern relates to UPI, Paytm, PhonePe, cookies, KYC files or login security, include the account email and the date of the activity so our team can trace it safely.

Team online

Privacy email

Write from the email tied to your account and state the exact privacy request. We may ask one verification question before we share copies, correct records or update contact details.

Account chat

Use in-account chat for quick privacy checks such as cookie choices, recent login queries or payment reference questions. We do not ask for full card, wallet PIN or app password details.

Security alert

If you see a login you do not recognise, contact us quickly with the time, device type and location shown on your account. We can check access logs and secure the profile.

SECURITY HANDLING

How your data stays controlled

Our Privacy Policy is written around practical account handling: collect what is needed, restrict internal access, keep records for clear reasons, and answer your requests through verified channels.

Account details

We use your name, contact details and account settings to create access, send service messages, and confirm profile changes.

KYC records

When identity checks are required, we use the documents only for verification, account safety and legal duties.

Payment references

UPI, Paytm and PhonePe records help us match deposits, withdrawals and failed attempts to your wallet.

Cookie choices

Cookies keep you signed in, remember basic preferences and help us detect risky sessions.

Session security

We log device type, IP address, browser data and login time to spot unusual account activity.

Retention checks

We keep records while your account is active and for legal, tax, fraud or dispute needs.

Privacy Policy questions answered clearly

These answers explain how the Privacy Policy works when you manage your account, payment records and contact choices. They are written for India and should be read with the full policy on this page. If your request needs identity confirmation, we will ask for enough detail to protect your account before we act.

We collect account details, contact data, KYC records when required, payment references, login logs, device data, cookie choices and support messages. Each data type is linked to account access, payment matching, security or legal duties.

Yes. Contact us from your account email and state that you want a copy of your personal data. We may verify your identity first, then provide eligible records in a practical format.

We record payment references, status, amount, date and wallet method so deposits and withdrawals can be matched to your account. We do not ask for wallet PINs, app passwords or full device access.

Yes. Send the correction request from your account email and mention the field that needs change. For KYC-linked data, we may need a valid document before the record can be updated.

Retention depends on the record type and the reason it was collected. Account, payment, KYC and dispute records may stay while legal, tax, fraud or operational duties still apply.

Cookies help with login, security checks, preference storage and error tracking. You can manage cookies through your browser, but essential cookies may be needed for account pages and payment status checks.

Use the privacy email or in-account chat and include your account email, request type and relevant date. If the matter involves access or eligibility, local law may decide what actions are available.