Reference

royal188 Privacy Policy for Your Account

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

Account clarityWallet recordsDevice controlsCookie choices
royal188 royal188 Privacy Policy for Your Account
PRIVACY HELP

Where To Ask About Your Policy Data

A clear support path helps when you need to ask what data we hold or correct an account detail. Start from the support route connected to your account, describe the request in plain English, and include the phone number or transaction reference that helps us locate the record. We use the same route for privacy questions linked to DANA, QRIS or a sign-in device.

Team online

Account data request

Ask us to locate the account records linked to your verified phone number. We may request an account step or identity detail before discussing private data through the support route.

Wallet reference check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, provide the payment reference and date. We use those details to separate your request from another account.

Device access concern

If a phone or desktop session appears unfamiliar, tell us through account support. We can review the sign-in record, explain the security step and help you protect the account.

HANDLING DETAILS

What We Do With Your Account Records

Privacy controls work best when each record has a practical reason. We use account, device and payment references to operate requested access, investigate unusual activity and answer support…

Account security

Phone verification is used before account access so we can connect a sign-in with the correct account.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a wallet status with your account.

Cookie settings

Cookies can keep your session active, remember a selected setting and show whether a policy page has been opened.

Device records

When you move from a mobile browser to desktop, we may retain device type, browser details and sign-in time for…

Retention period

We retain account and payment references while needed for access, security, dispute handling or a lawful request.

Change request

To correct, access or ask about your personal data, use the account support path and describe the requested change.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the practical questions we expect before you open an account from Indonesia. They explain wallet records, phone verification, cookies, device changes and the support route for requests. If your situation is not listed, send the relevant account detail through support so we can direct the question to the right privacy process.

It covers account details, phone verification, sign-in and device records, cookie use, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps us connect account access with you and identify unusual sign-in attempts. We may ask for a matching account detail before sharing private records or processing a change request.

Our Privacy Policy describes payment status and transaction references, not wallet passwords. DANA, OVO, GoPay and QRIS references help us match a requested payment action with your account.

We may record the device type, browser details, sign-in time and security result when you move from mobile to desktop. These details help us assess whether the session belongs to your account.

Use the account support path and state which detail needs correction. Include the verified phone number or relevant account reference; we may complete a security check before changing or disclosing records.

We keep payment references only while they support account operation, reconciliation, security, dispute handling or a lawful request. After those purposes end, we assess deletion or any required further retention.

Yes. Ask through account support if you need clarification about session cookies or preference files. Browser settings can restrict cookies, but some sign-in and policy access steps may need repeating.