Reference

Privacy Policy for India access

This Privacy Policy sets out the data we need to run account access, wallet checks, cookies and session records for Speed Baccarat, Medusa, Football Strike and other rooms…

Account data useUPI record handlingCookie choicesCorrection requests
0yy Privacy Policy for India access
CONTACT ROUTES

Privacy questions through India channels

Use these contact paths when your question is about this Privacy Policy, your stored data, cookie choices, account access records or payment references.

Privacy email Send a privacy request with your registered mobile number or email, the data category involved and the change you want. We reply with the next check needed before any account data is amended.
Live chat privacy queue Open chat from your account when you need help finding cookie settings, payment records or recent login data. The agent can explain policy steps without exposing private data in the chat window.
Account request form Use the form for correction, access or deletion requests where available. We compare the request with your account record, payment references and login history before taking action.
DATA CARE

Controls behind 0yy privacy handling

Our privacy handling is built around account identity, payment verification, device safety and clear request paths.

Data collection

We collect registration details, login records, device signals, wallet references, cookie choices and support messages. Each category is tied to account operation, payment checks, fraud prevention, service messages or legal record duties.

Cookie controls

Cookies help keep you signed in, remember language choices, secure sessions and measure page errors. You can change browser settings, but some account and payment pages may need essential cookies to work.

Payment records

For UPI, Paytm and PhonePe, we retain transaction reference numbers, status updates, timing and account links. We do not need your full bank password or one-time payment code for privacy requests.

Access security

When you ask to view or correct data, we verify that the request comes from the account holder. Checks may include registered contact details, recent activity or payment reference confirmation.

Retention approach

Account and payment records are kept for as long as needed for disputes, security checks, legal duties and account management. When retention is no longer required, we delete or anonymise eligible records.

Change requests

You can ask us to correct inaccurate profile details, update contact fields or remove eligible data. We explain if a record must remain because of payment, security or legal requirements.

Privacy Policy questions for India

These answers explain how the Privacy Policy works when you create an account, use local payment options, adjust cookies or contact us about your data. They are written for India access, but the exact availability of account features and data rights can depend on local law. For anything private, contact us from the account channel where possible.

It covers account details, contact data, device records, login history, payment references, cookie choices, support chats and play-session records. We use these categories to run your account, protect access and handle requests.

No. For UPI, Paytm and PhonePe, we store transaction references, status updates, timings and account links. We do not ask for your full banking password or one-time payment code.

Contact us from your registered account email, chat or privacy form. We verify your identity before sharing account data because payment references, login history and support records must be protected.

Yes, you can request correction of inaccurate profile or contact data. Some changes may need verification through your registered mobile number, email or recent payment reference before we update the record.

We keep data only for account operation, dispute handling, security checks, payment reconciliation and legal duties. When a record is no longer needed for those purposes, we delete or anonymise it.

Access is limited to staff who need it for support, payment checks, security work or legal response. We use role-based access and may record internal actions for audit purposes.

Some access, eligibility and data handling duties depend on local law and are available where local law permits. If a regional rule applies to your account, we follow that rule for the affected record.