Reference

Privacy Policy for India accounts

Account creation, UPI wallet checks and lobby activity around Live Baccarat, John Hunter, Football Strike, Rocketon, Bingo and Fishing God create account data that this Privacy Policy explains.

UPI data contextPaytm wallet recordsPhonePe request routeCookie choicesAccount privacy
y85 Privacy Policy for India accounts
CONTACT PATHS

Three privacy contact paths

Privacy questions should reach the right team without asking you to repeat account details in several places.

Account help desk Use account help for corrections to your name, mobile number, email or login record.
Wallet privacy requests For UPI, Paytm, PhonePe or Google Pay record questions, share the transaction reference and…
Cookie choice support If you want to change cookie choices, ask support for the current browser steps.
ACCOUNT SAFETY

Six ways we handle data

Our Privacy Policy is written around real account actions: joining, signing in, making a deposit, asking for a withdrawal, using the lobby and contacting support.

Personal data handling

We collect account details such as your name, contact data, login signals and verification records when needed. Internal access is limited to teams handling account checks, payments, security alerts or privacy requests.

Cookie choices

Cookies help keep your session active, remember language choices and spot unusual login attempts. Where optional cookies are used, we explain their purpose and help you change browser choices when you ask.

Account security records

Login time, device type, IP signals and password reset actions help us protect your account. If an access issue appears, support may use those records to confirm whether the action came from you.

Payment record care

UPI, Paytm, PhonePe and Google Pay references are used to match deposits, withdrawals and refund checks. We do not ask for full card numbers or full bank passwords through chat or email.

Retention periods

We keep records while your account is active and for periods needed for legal, payment, fraud prevention or dispute reasons. When records are no longer needed, we delete or anonymise them where feasible.

Correction requests

You can ask us to correct personal data that is outdated or wrong. We may request proof before changing sensitive records, especially where a payment, withdrawal or account recovery request is involved.

Privacy Policy questions before joining

These answers explain how the Privacy Policy applies when you open an account, use local payment methods, change details, manage cookies or ask us to delete records. They are written for India account access and should be read together with any account terms shown during registration.

It covers personal data linked to your account, including registration details, login records, device signals, support chats, cookie choices and payment references from UPI, Paytm, PhonePe or Google Pay.

Payment references help us match deposits, withdrawals, refunds and dispute checks to the correct account. We use the smallest set of details needed and do not request full banking passwords.

Yes. Contact support from your registered email or mobile number and explain what should be corrected. For sensitive changes, we may ask for proof before updating the account record.

Cookies support sign-in, session safety, language choices and fraud checks. Some browser choices can be changed by you, and support can explain which cookies are needed for account access.

We may share limited data with payment processors, verification checks, hosting providers, advisers or authorities when needed for account operation, legal duties, disputes, security checks or your own privacy request.

You can ask us to delete personal data, and we will assess the request against legal, payment, security and dispute requirements. Some records may need to be retained for a lawful reason.

Yes. Account access and eligibility depend on local law and are available where local law permits. Privacy handling still applies to account records we hold, even when access changes.