Reference

Privacy Policy for Your Indonesia Account

Our Privacy Policy explains how raja bandot handles the details you provide when opening an account, checking wallet status, or entering the lobby where local law permits.

Clear data purposesWallet record clarityCookie choicesAccount access steps
raja bandot Privacy Policy for Your Indonesia Account
CONTACT PATHS

Privacy Questions Along Your Account Path

A clear contact route matters when you want to ask what data we hold or why a wallet reference appears in your account history.

Account contact Ask about your phone verification record, sign-in history, or stored account details through the…
Cashier status If a DANA, OVO, GoPay, or QRIS reference looks unfamiliar, mention the date, rail…
Access request For a copy, correction, or removal request, state the account phone number and the…
DATA HANDLING

What We Do With Your Privacy Choices

Our handling process is designed around identifiable account actions rather than broad claims.

Purpose first

We use account details for defined tasks such as phone verification, sign-in protection, wallet-status matching, support replies, and handling a request made under this Privacy Policy. We do not ask you to provide unrelated personal details for a routine account question.

Mobile browser data

When you open the lobby from a phone browser, technical details such as device type, browser version, and connection events may be recorded for access security. These details help us distinguish a normal return from an unusual sign-in attempt.

Cookie control

Cookies or similar browser storage may remember a setting, support an account session, or help us detect repeated access problems. You can clear browser storage through your device settings, though doing so may require another sign-in and phone check.

Account security

We treat your phone verification step and sign-in events as account-security signals. Never send a password, one-time code, wallet PIN, or full payment credential in a support message; our contact path needs an account reference instead.

Retention approach

We keep records only for as long as they serve the stated account, security, support, or transaction purpose, subject to applicable requirements. When a record is no longer needed for those purposes, our handling process considers deletion or removal.

Change requests

You may ask us to correct account details, explain a stored record, or address a privacy concern. Include the relevant category and account reference, then complete any ownership check needed before we disclose or change personal data.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account questions you are most likely to ask before opening access. We keep the examples tied to the actual steps you see, including phone verification, wallet references, browser settings, and the support route. If your situation is not covered, send a focused request through the account contact path.

The Privacy Policy covers personal and technical data linked to your account, including phone verification, sign-in events, browser details, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

A payment reference helps us match an account action with its status, investigate a delayed or unclear cashier record, and answer your request. It is not the same as receiving your wallet PIN or full wallet credentials.

Use the support link available after sign-in and ask for the account data category you want to access. Include your account phone number or reference, but do not send your password, one-time code, wallet PIN, or full payment details.

Yes. Send a correction request through the account contact route and identify the field that needs changing. We may ask you to complete phone verification or another ownership check before discussing or editing personal account details.

Cookies and similar browser storage can preserve a selected setting, support a session, or help identify access trouble on your phone. Clearing them through browser settings may remove that stored choice and require you to sign in again.

We retain a record while it serves the stated account, security, support, or transaction purpose, subject to applicable requirements. The retention period can differ by record type, and you can ask support which category your request concerns.

Yes. Account access and eligibility depends on local law, and the service is described for use where local law permits. If your location or circumstances raise a question, contact us through the account route before continuing.