Reference

Privacy Policy for your India account

When you open an account, our Privacy Policy explains how jz481 handles data from sign-in, cookies, Baccarat table activity and UPI, Paytm or PhonePe records.

UPI record careCookie choicesAccount data accessGoogle Pay context
jz481 Privacy Policy for your India account
CONTACT ROUTES

Privacy help through India channels

Privacy questions should reach the right queue, not get buried inside a general game chat.

Privacy email Send privacy requests from the email linked to your account and include your username only when needed. We will ask for extra checks before sharing account, wallet or device data.
Live chat handover If you start in live chat, ask for the privacy queue. The chat team can capture the request, but account data changes are handled after verification through the privacy contact path.
Payment record query For UPI, Paytm, PhonePe or Google Pay privacy questions, include the reference ID and date. We use that to locate the record without asking for unnecessary wallet screenshots.
DATA CARE

Data care across your account

Our Privacy Policy is written around the account steps you actually use: sign-in, wallet checks, game session records, support contact and device security.

Data we collect

We collect account details, sign-in logs, device data, wallet references and session records needed to run your account.

Cookie controls

Cookies help remember sign-in state, language choice and security signals.

Payment records

UPI, Paytm, PhonePe and Google Pay records may include reference IDs, status messages and timestamps.

Account security

We protect sign-in data with access controls, session checks and staff permissions based on job need.

Retention periods

Some records are kept while your account is active, and some payment or security records may be kept longer where…

Correction requests

You can ask us to correct email, phone, name or other account data where the record is inaccurate.

Privacy questions before you join

These privacy answers explain how we treat account data before and after you join. They cover what we collect, why payment records are kept, how cookies work, and how you can contact us about access or correction. If a request involves eligibility, access or account status, the answer may depend on local law and is available where local law permits.

We collect data needed to run your account, such as sign-in details, contact details, device signals, wallet references, support messages and session records from rooms like Baccarat, Rocketon or Bingo.

Payment records help match wallet activity to your account, trace failed or pending transfers, answer disputes and meet record duties. We usually need reference IDs, time, amount and status, not full wallet access.

Yes. Contact us through the privacy path in your account and verify that the request is yours. We will explain the data categories we hold and any lawful reason for withholding limited parts.

Send a correction request from the email or phone linked to your account. For details tied to payments or verification, we may ask for evidence before changing the record.

Cookies can remember sign-in state, language, security checks and basic usage patterns. Game session records are kept separately from optional analytics settings, and you can adjust cookie choices through your browser or panel.

We may share limited data with payment processors, security vendors, analytics tools or support systems that help operate your account. Contracts restrict how those vendors use data received from us.

We keep a record of your request, verification step and our answer so we can prove how the matter was handled. The length depends on account status, dispute needs and legal duties.