Reference

raja bandar88 Privacy Policy

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Account recordsWallet detailsDevice signalsCookie choices
raja bandar88 raja bandar88 Privacy Policy
CONTACT ROUTES

Where To Ask About Privacy

A clear support path helps when a privacy question is linked to a login or wallet event.

Account privacy request Use the support path inside your account to ask what personal records are linked to your phone verification. We may ask for an account step or recent sign-in detail before releasing data, so the request reaches the correct account rather than another person.
Wallet record question For a DANA, OVO, GoPay or QRIS reference, share the date, amount display and payment rail name without sending secret wallet credentials. We use those details to locate the relevant record and explain whether the source is our account system or the payment provider.
Access and correction Ask us to correct an inaccurate phone, email or profile detail through the available support contact. We first verify account control, then explain any legal or operational reason a record must remain, including a transaction reference needed for security checks.
SIX DATA CHECKS

Six Privacy Checks Behind Your Account

We keep this policy practical by tying each privacy choice to an account action you can recognise.

Account creation

We use the phone number and details you submit to create and maintain your account. Phone verification confirms control before account access, while login records show when the account was opened from a browser or device.

Wallet references

DANA, OVO, GoPay and QRIS can generate reference data connected with your account activity. We use the reference to reconcile a status question, while payment providers and banks remain responsible for records held in their own systems.

Cookies and storage

Cookies can keep a signed-in session, remember selected settings and help us understand basic page loading. You can manage browser storage through your device settings, although removing it may require another login or clear saved preferences.

Account security

We examine sign-in time, browser details, device signals and unusual access patterns to protect your account. If a check is triggered, we may request phone verification or another account step before discussing personal records.

Retention period

We keep personal records only as long as needed for the purpose collected, account security, dispute handling or a legal requirement. When a record is no longer needed, we remove it, separate it from the account or restrict further use.

Change requests

You can ask us to correct, access or delete eligible personal data through the support route shown in your account. State the record and requested action clearly; we verify account control and explain any limit before making a change.

Privacy Policy Questions From Indonesia

These answers address the privacy searches we expect when you are deciding whether to open an account or need help with an existing record. Each answer stays focused on data use, account control, payment references, browser settings and the steps available to you under local law.

It covers personal details used for account creation, phone verification, login security, wallet references, cookies, device signals and support requests. It also explains how to ask for access, correction or deletion, with any restriction handled where local law permits.

Yes. We explain how DANA and QRIS references may connect to your account for status checks and reconciliation. We do not replace the privacy rules of the wallet or bank, so records held directly by those providers may require a request to them.

We may record browser type, device signals, language, IP address and sign-in time. These details help us recognise unusual access and keep the account secure. They are handled alongside your account event, not treated as a public profile.

Use the support route shown after you sign in and ask for an account data access request. Identify the phone verification or account record involved. We verify that you control the account, then explain the available records and any lawful restriction.

Yes. Send a correction request through the account support path and name the inaccurate field, such as a phone or email detail. We may confirm account control first, then update eligible records or explain why a record must remain unchanged.

Use the cookie and site-storage controls in your mobile browser settings to remove or restrict stored data. This can end a signed-in session or clear preferences. Our Privacy Policy explains the purposes of cookies, while your browser controls the local setting.

The period depends on why the record exists. We retain data for account security, dispute handling or a legal requirement only while needed, then remove it, separate it from the account or restrict further use. Requests remain subject to local law.