Reference

Privacy Policy for Your rajaturbo Account

Your account data, wallet references and device choices are explained in the rajaturbo Privacy Policy, so you can understand what we collect before opening access to Live Roulette…

Clear data purposesWallet detail contextAccount request pathLocal law wording
rajaturbo Privacy Policy for Your rajaturbo Account
REQUEST ROUTES

Where Privacy Policy Questions Go

A clear support route helps when you need to ask what data we hold, why an account check is pending, or how a wallet reference appears…

Account data request Ask for access to personal data connected with your account through the account support…
Wallet reference query If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction detail…
Correction request Tell us which account detail needs changing and why it is inaccurate.
DATA PRACTICE

Six Practical Privacy Commitments

Privacy work follows the same account path you use to reach the lobby: we identify the record, check the request, apply the relevant purpose and keep an audit trail for security.

Purposeful collection

We collect account details needed for access, verification, wallet matching and support. Choosing a payment rail such as QRIS can create a transaction reference, while the game area you open may create session data.

Cookie controls

Cookies help keep your login session connected while you move between Live Roulette, station4d and account pages. Your browser settings can restrict cookies, although some account functions may then require another verification step.

Account protection

We use account checks to reduce mistaken access and connect requests with the correct account. Keep your phone detail and login credentials private; support will not need your full password to discuss a Privacy Policy request.

Retention logic

We retain records for as long as needed for the stated account, payment, security or legal purpose. A BCA, BRI, Mandiri or BNI transfer reference may remain while reconciliation or a permitted request is still being handled.

Your corrections

You can ask us to correct inaccurate profile details or clarify how a data field was obtained. Include the affected account step, such as phone verification or a wallet reference, so we can locate the right record.

Limited disclosure

We disclose account data only for the purposes described in the Privacy Policy, such as processing a requested payment or meeting a lawful request. We do not treat your DANA or QRIS reference as a public profile.

Privacy Policy Answers Before Account Access

These Privacy Policy answers focus on the searches you may make before opening an account or asking us to change a record. We cover payment references, mobile sessions, cookies, account access and contact steps without turning the page into a general lobby description. If your situation is not listed, use the support path attached to your account and explain the specific data concern.

The rajaturbo Privacy Policy covers account details, phone verification, device sessions, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, permitted disclosure and how to request access or correction.

We do not describe your wallet balance as a rajaturbo account balance. The Privacy Policy concerns transaction references, status details and account-matching information needed for a requested payment step. DANA or QRIS remains your chosen payment rail, while our records support reconciliation and security.

Use the account support path and ask for a personal data access request. Include the phone detail connected with your account and identify the relevant area, such as cookies, Live Roulette session data or a GoPay reference. We verify the request before responding where local law permits.

Yes, you can request correction when an account detail is inaccurate or incomplete. Tell us the field, the correct value and the account step where it appears, such as phone verification or a bank transfer reference. We assess the request under the Privacy Policy and local requirements.

Cookies help maintain your session when you move from the login page to the lobby on a mobile browser. They can support account continuity and security checks around areas such as station4d. You can adjust browser settings, but restricting cookies may interrupt access or trigger another check.

Retention depends on why the record exists. A DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI reference may be kept for account matching, reconciliation, security or a legal obligation. The Privacy Policy explains the purpose, and deletion requests are assessed where local law permits.

Yes, this Privacy Policy is available before you complete the account path. Read it before submitting phone details or selecting a wallet rail. Account access and any related request depend on local law, so the policy wording should be considered alongside the eligibility conditions shown at the time.