Reference

indoroyal88 Privacy Policy For Your Account

indoroyal88 Privacy Policy explains how we use account, device and wallet details when you open the lobby, verify your phone or choose DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesPolicy requests
indoroyal88 indoroyal88 Privacy Policy For Your Account
CONTACT THE TEAM

Reach Support About Privacy Policy

A clear contact path matters when a Privacy Policy question concerns your own account. Start from the signed-in account help area and include the email or phone detail attached to your profile…

Account access If you cannot sign in after phone verification, use the account help path and state that your request concerns the Privacy Policy. We can explain which account details are needed to identify your record and protect it during the reply.
Wallet status For a DANA, OVO, GoPay or QRIS record, share the date, amount reference and wallet name only through the account support path. We use those details to locate the relevant event without requesting your wallet PIN.
Data request To ask for a copy, correction or deletion of eligible personal data, write through the policy contact route linked in your account area. We may ask for account checks first so another person cannot request changes to your record.
HOW WE HANDLE DATA

Browse The Privacy Controls We Apply

We treat Privacy Policy work as an account operation, not a loose statement. The points below show how we approach session data, wallet references, account protection, cookies, retention and requests.

Account details

We use your registered contact details to create and secure the account, complete the clear phone verification step and respond to policy requests. Keep your sign-in details private; support will not ask for your wallet PIN or full password.

Wallet references

DANA, OVO, GoPay and QRIS references help us match a wallet event with the correct account. For bank transfer or virtual account activity, we may retain the reference needed to reconcile status and answer a payment-data question.

Device signals

When you move from mobile login to the lobby, we may record device and session signals used for sign-in protection, fault tracing and session continuity. These signals help us distinguish a normal return from an unusual access attempt.

Cookie settings

Cookies can keep a session open, remember selected settings and help us understand technical failures. You can manage cookies through your browser controls, although turning some off may affect login continuity or the path from account access to the lobby.

Retention checks

We retain personal data only for the period needed for account operation, security checks, legal duties or a documented request. A wallet receipt or account event may therefore remain after you stop using the mobile or desktop path.

Request changes

You can ask what personal data we hold, request a correction or ask whether deletion is available for a particular record. Send the request through the account policy route, and we will check identity before making any change.

Find Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often before an account is opened. If your question concerns a particular wallet reference, device session or account detail, use the policy contact path with the smallest useful set of identifying facts.

The indoroyal88 Privacy Policy covers account creation, phone verification, sign-in sessions, device signals, cookies, wallet references and policy requests. It also explains how we handle records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your registered phone and account details to create the correct profile, complete phone verification, protect sign-in and answer requests about your data. The checks help prevent another person from changing or receiving details from your account.

Yes. The Privacy Policy covers references linked to DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use those references to match a wallet event with your account and check its status when you ask for help.

Use the policy contact route in your account help area and state whether you want a copy, correction or another permitted action. Include your registered contact detail, but do not send a password, wallet PIN or complete payment credential.

On a mobile browser, cookies may keep your session connected between sign-in and the lobby, remember settings and help trace technical faults. You can adjust them in browser controls, though disabling some cookies may interrupt account access or session continuity.

We keep records for the time needed to operate the account, protect access, meet applicable legal duties or handle a documented request. A QRIS receipt, bank transfer reference or security event may remain while that purpose still applies.

Yes. Contact us through the signed-in account policy route and identify the record by its date, wallet name or account event. We may complete an identity check before discussing it, and access or eligibility depends on local law.