Reference

Privacy Policy for your r2d2 account

Your r2d2 account links lobby access for Blackjack, Wild Toro, Football Strike and wallet actions with a privacy policy that explains what data we collect, why we use…

Account data useCookie choicesUPI privacy contextSupport requests
r2d2 Privacy Policy for your r2d2 account
CONTACT ROUTES

Privacy help through clear contact paths

If something in this Privacy Policy feels unclear, contact us before sharing extra documents. We will ask for enough detail to locate your account and confirm the request belongs to you.

Privacy email Send privacy requests to our support email with your registered mobile number or email address. Keep screenshots cropped to the relevant line, and cover unrelated wallet balances before attaching them.
Live chat handover Start in chat if you need quick direction, then ask for a privacy handover. We log the chat case number so the privacy team can follow the same request without repeating sensitive data.
Account correction request Use this route when your name, contact number or payment reference looks wrong. We may ask for a document check, then update the account record or explain why a field must stay unchanged.
CARE CONTROLS

Account privacy around Blackjack and Aviator

We treat privacy as a daily operating duty, not a hidden page footer. Data access is limited by role, payment checks are separated from game-session logs, and support cases are kept with…

Data we collect

We collect account identifiers, contact details, device signals, session activity, payment references and support messages. These records help us run login checks, process wallet actions, answer you, and detect account misuse.

Cookie handling

Cookies help keep you signed in, remember basic preferences and spot unusual access attempts. You can manage browser cookies, but some security and wallet flows may not work correctly without required cookies.

Payment privacy

For UPI, Paytm, PhonePe and Google Pay, we store transaction IDs, status codes, timestamps and masked sender markers. We do not store your app PIN, card PIN or full banking login secrets.

Security checks

When a login or withdrawal looks unusual, we may compare device signals, location range and account history. These checks protect your balance and help us confirm that the request is really yours.

Retention periods

Some records are deleted when they no longer serve the account, while payment and dispute records may be kept longer for audit, tax or legal needs. We review stored data on a scheduled basis.

Your privacy choices

You can ask to correct account data, limit non-essential contact, close an account record where allowed, or receive an explanation of stored data. We verify identity before acting on any request.

Privacy Policy questions before you join

These answers explain the privacy points we are asked about most often before account creation and after wallet activity. They cover data collection, payment records, cookies, correction requests and account access checks. If your case involves a legal notice, dispute or document mismatch, contact support with your account email so we can route it to the right privacy workflow.

We collect your name, contact details, age confirmation status, login data, device signals, payment references and support messages. We use these records to run your account, manage wallet actions, protect access and meet legal duties.

Yes. It covers how we handle UPI, Paytm, PhonePe and Google Pay references connected with deposits, withdrawals or failed attempts. We keep transaction IDs and status records, not your private app PIN or banking password.

Yes. Contact support with the field that looks wrong and proof that matches the account. We verify the request first, then correct the record or explain why a legal or payment entry cannot be changed.

Cookies support login sessions, language choices, fraud checks and error measurement. You can adjust browser settings, but turning off required cookies may affect sign-in, wallet confirmation or account security checks tied to your device.

Only team roles that need the case can access your request. Support may see the first message, while payment or account-security staff may see limited records needed to verify and resolve the specific privacy matter.

We keep account and payment records only as long as needed for service operation, dispute handling, audit duties and legal requirements. When a record is no longer needed, we delete it or reduce it where possible.

Access and eligibility depend on local law and are available where local law permits. If a region-based rule affects your account, we may keep limited records needed to explain the decision and handle related wallet queries.