Reference

raja bos Privacy Policy for Your Account

The raja bos Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and access the lobby from your device.

Account clarityPayment contextDevice safeguardsRequest support
raja bos raja bos Privacy Policy for Your Account
CONTACT ROUTES

Ask About Your Privacy Policy Data

A direct support route helps you question a record without exposing account details in a public message.

Account support form Use the account support form to ask what personal data we hold, request a correction or ask for a copy of details connected with your raja bos account. We may ask you to complete phone verification before sending account-specific data.
Cashier support path When a payment reference looks wrong, contact support from the account route near the cashier. Include the rail used, such as QRIS or bank transfer, and the transaction reference; do not send a wallet PIN or full banking password.
Access recovery If you cannot sign in, tell support which device and account phone number you used. We limit replies until the account check is complete, helping prevent another person from receiving your Privacy Policy data or changing your contact details.
HANDLING DETAILS

Live Roulette Elite and Data Controls

Privacy protection is handled through the same account steps you use to reach the lobby. We separate identity checks from payment references, restrict account records to operational needs and use device signals…

Account details

When you open an account, we collect the details needed to create it and the phone number used for verification. Your account record may also show preferences, support messages and access history, allowing us to investigate a request without relying on a public username alone.

Payment references

We record payment references and status information for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet PIN for this process. Bank names such as BCA, BRI, Mandiri or BNI may appear as part of a transfer reference.

Cookies and devices

Cookies can keep your sign-in session, language choice and basic page settings in place. We may also record browser, device and security signals. Clearing cookies can sign you out and may require phone verification again before account access returns.

Security checks

A new device, unusual login pattern or account change may trigger an additional check. We use this step before discussing private records or changing a phone detail. If the check fails, support will not disclose account data through an unverified request.

Retention approach

We keep account, payment and support records only for the period needed for access, security, reconciliation, dispute handling and legal duties. When a record is no longer needed for those purposes, our internal process removes it or separates it from direct account identification.

Change requests

To correct a name, phone detail or other account record, contact support through the signed-in account path. State the requested change and why it is inaccurate. We verify ownership first, then confirm whether the update is possible under local rules.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the questions we expect before you open an account or connect a local wallet. They explain the practical steps for access, data requests, device changes and payment references. If your situation is not listed, contact us through the signed-in support route so we can check the account safely.

The raja bos Privacy Policy covers account creation, phone verification, sign-in records, device signals, cookies, support messages and payment references. It applies when you access the lobby, use the cashier or ask us to change, provide or remove personal data, where local law permits.

We may collect your account and phone details, verification status, browser and device signals, login activity, support correspondence and payment status references. For DANA, OVO, GoPay and QRIS, we use the transaction details needed to match status with your account, not a wallet PIN.

Phone verification helps us confirm that the person opening or recovering an account controls the listed contact number. We may request it again after cookies are cleared, a new device appears or you ask for a private data change. This reduces disclosure to an unverified person.

Sign in and send the request through the account support form. Tell us whether you want a copy, correction or clarification, and identify the relevant account detail. We check ownership before replying, then handle the request according to the Privacy Policy and applicable local rules.

Yes. Cookies can preserve a login session and basic settings when you move through the mobile lobby. Device and browser signals may support security checks. If you remove cookies, the next sign-in may require phone verification again before your account data is shown.

We use DANA and QRIS references to identify payment status, reconcile an account record and investigate a cashier question. The same approach applies to OVO, GoPay, bank transfer and virtual account activity. Send only the reference needed for the request, never a PIN or password.

We retain account, payment and support records for as long as they are needed for account access, security, reconciliation, disputes or legal duties. The exact period can depend on the record and local requirements. You can ask support about a specific record through the verified account path.