Reference

Privacy Policy for Your raja88bet Account

Your raja88bet Privacy Policy explains the account data we collect when you open the lobby, choose VIP Baccarat or Crash Games, and use DANA, OVO, GoPay or QRIS.

Account dataCookie controlsQRIS receipts24 hour privacy help
raja88bet Privacy Policy for Your raja88bet Account
PRIVACY CONTACTS

Ask Us About Your Data

Privacy requests should reach the team that can match your account and verify your identity safely.

Live chat Open live chat from the account menu any hour of the day and ask for privacy help. We will confirm your login name, last payment rail used, and the request type before sending it onward.
Email request Send account-data requests to the address shown after login so we can attach your message to your account record. Include your username, registered mobile number, and whether you need access, correction, or deletion where allowed.
Account page Use Account > Security to change your password, check active sessions, and refresh contact details. For wallet edits linked to DANA, OVO, GoPay or QRIS, we may ask for extra proof before applying changes.
DATA HANDLING

How We Handle Account Data

We handle privacy as an account operation, not a formality. The same checks that protect your balance also shape how data is stored, who can access it, and when it can be…

Account collection

We collect the details needed to run your account: login name, mobile number, password status, one-time code results, wallet references, and support messages. We do not ask for unrelated profile data during normal account creation.

Payment records

DANA, OVO, GoPay and QRIS records are stored as transaction references, timestamps, and matching results. These help us confirm deposits, investigate failed credits, and respond when you ask about a payment trace.

Cookie choices

Cookies keep your session active, remember language choices, and help detect repeated failed sign-ins. You can clear them through Chrome > Settings > Site settings > Cookies, but you may need to log in again.

Device checks

We log device type, browser, IP range, and session timing to spot unusual access. If your Android phone changes network between Wi-Fi and mobile data, we may ask for another verification step.

Retention rules

We keep account, payment, and support records only for as long as needed for service, dispute handling, security checks, or legal obligations that apply. When retention ends, records are removed or anonymised.

Change requests

You can ask us to correct account details, export personal data, or remove records where the law allows. We verify identity first so another person cannot change your wallet, phone, or login data.

Privacy Policy Questions You May Ask

These answers focus on the data choices you are most likely to care about before opening or maintaining an account. We explain what we collect, how payment rails appear in our records, how cookies affect your session, and how to reach us when you want to change or remove data.

We collect your login name, mobile number, password status, one-time code results, device details, and wallet references. We use these items to create your account, protect access, match payments, and answer support requests.

We store payment references, timestamps, amounts, and matching results needed to credit your wallet or investigate a failed transaction. We do not need your private app password for DANA, OVO, GoPay or QRIS.

Cookies keep you signed in, remember basic preferences, and help us detect repeated failed login attempts. If you clear cookies on Chrome or Safari, your session ends and you may need a fresh verification step.

Yes, you can contact us through live chat or the logged-in email path and ask for an account data export. We will verify your identity before sharing records tied to your login.

Go to Account > Security for password and contact updates, then contact support for wallet changes. We may ask for payment proof or a one-time code before changing DANA, OVO, GoPay or QRIS records.

You can request deletion where local law allows and where we no longer need the record for security, payment dispute handling, or required retention. We will explain which records can be removed after verification.

Only staff assigned to account safety, payments, or support handling can access the parts needed for your request. We limit access by role and keep a record of internal changes made to account data.