Reference

Privacy Policy For Your rbo88 Account

Our Privacy Policy explains what account, device and payment details we collect when you open and use rbo88 in Indonesia.

Account clarityWallet contextDevice accessPolicy access
rbo88 Privacy Policy For Your rbo88 Account
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact path matters when you need to ask about your personal data.

Policy access Ask support to direct you to the current Privacy Policy from the account area.
Data questions For a question about contact details, device records or verification information, describe the issue…
Wallet reference If your request concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account…
DATA CONTROLS

How Privacy Works Inside rbo88

We apply the Privacy Policy across the account flow rather than treating it as a page you only see once.

Account records

We may hold your account identifier, contact details and phone-verification status so we can provide account access and answer a…

Payment references

A wallet or bank transaction reference can be stored with account activity to reconcile a deposit or withdrawal request.

Cookies and storage

Browser cookies or local storage may keep a session active, remember a language choice or support a security check.

Device signals

We may record practical device and sign-in signals, such as browser type, session time and network details, to identify unusual…

Retention

We keep information only as long as it serves account operations, security, dispute handling or a legal requirement.

Change requests

To ask for a correction or another privacy action, contact support through the account help route with enough detail to…

Answers About Your Privacy Policy

The questions below focus on the parts of our Privacy Policy that affect an Indonesian account holder. They cover the information used for sign-in, wallet reconciliation, cookies, retention and requests for access or correction. Read them alongside the full policy before you submit account details or connect a payment method. For an account-specific matter, use the support path with a transaction reference where relevant.

The rbo88 Privacy Policy covers details connected with your account, such as contact information, phone-verification status, sign-in activity and device signals. We use these details for account access, security checks, support responses and accurate records, subject to the conditions described in the policy.

Yes. The Privacy Policy includes payment references and status information linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests. These references help us match an account action with the correct record without asking for your wallet password or one-time code.

You can contact support through the account help route and ask what personal information is held about your account. Include your account identifier and a clear description of the request. We may verify your identity first, and access depends on local law.

Cookies and similar browser storage may support your session, remember basic settings or assist a security check. You can adjust browser permissions, but the change may sign you out or affect page access. The Privacy Policy explains how these tools fit within the account flow.

We retain different records for the period needed for account operations, security checks, transaction questions, dispute handling or legal requirements. The exact period can vary by record type. The Privacy Policy sets out the retention approach, and support can identify the relevant category for your request.

Send a correction request through the account help route and explain which detail is inaccurate, such as a contact field or verification record. Do not send a password or one-time code. We may confirm account ownership before making a change, where local law permits.

Yes. The Privacy Policy applies when you access the account pages from a phone, tablet or desktop browser. Device and session signals may be recorded for security, while cookies can support sign-in continuity. The same policy access and local-law conditions apply across supported devices.