Reference

Open royal505 Privacy Policy Clearly

royal505 Privacy Policy explains what we collect when you create an account, verify your phone and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record contextAccount access choicesCookie controls
Explore Our Lobby Read FAQ
royal505 Open royal505 Privacy Policy Clearly
HELP WITH REQUESTS

Browse Support Paths for Privacy Questions

A clear support route helps you ask about your Privacy Policy choices without sending sensitive details through an unsuitable path.

Account access path Use the account help route for a Privacy Policy question about your phone verification…
Wallet record check For DANA, OVO, GoPay or QRIS questions, include the relevant receipt reference and wallet…
Device access query If a mobile session looks unfamiliar, tell us the device path and approximate login…
HANDLING YOUR DATA

Switch Through Privacy Controls With Care

We handle this policy area through practical account and payment checks rather than broad collection.

Purpose of collection

We collect account details to create and maintain access, complete phone verification and respond to account requests. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account help us reconcile a cashier status without treating unrelated browsing activity as payment data.

Cookies and sessions

Cookies and similar session records can keep you signed in, remember a selected device path and help us identify an interrupted mobile session. You can manage browser cookie settings, although removing necessary cookies may affect account access or require another phone verification step.

Account protection

Phone verification, session checks and device signals help us respond when a login appears unusual. We do not need your password or one-time code for a Privacy Policy request. If you spot an unfamiliar session, use the account support path promptly and describe the device involved.

Retention approach

We keep account, support and transaction records for as long as they serve access, dispute handling, security checks or a legal requirement. When a record is no longer needed for those purposes, we work to remove or separate it, subject to lawful recordkeeping duties.

Access requests

You may ask what personal data we hold about your account, subject to identity checks and limits that depend on local law. A useful request names your account phone number and the record type, such as a QRIS receipt, device session or support conversation.

Change or correction

If your account detail is wrong, request a correction through account support and explain which field needs attention. We may verify the phone linked to the account before changing it, helping prevent an unauthorised person from altering your profile or wallet record.

Browse Privacy Policy Questions Before Opening

These Privacy Policy answers focus on the account steps Indonesian customers most often need to understand before opening access. They cover data collection, wallet references, cookies, deletion and contact routes without asking you to share private credentials. If your situation is not listed, use the account help path and describe the specific record or device involved.

The royal505 Privacy Policy covers account creation, phone verification, login and device records, cookies, support messages and payment references. It explains how we use those details for access, security, cashier checks and lawful recordkeeping where local law permits.

Phone verification links an account request to the person completing the access step and helps us respond to unusual login activity. We may use the verification result when handling a Privacy Policy request, but you should never send us your password or one-time code.

Yes. The Privacy Policy covers transaction references, wallet status and receipt details created when you use DANA, OVO, GoPay or QRIS. We use these records to match a cashier question, check a stalled status and handle an account request.

Use the account support route and state that you are making a data access request. Include the phone number linked to your account and name the record you need, such as a device session or QRIS receipt. We verify identity before responding.

You can request a correction or ask about removal through account support. We first confirm the account and the record involved. Removal may be limited where transaction, security or lawful retention duties apply, and the outcome depends on local law.

Cookies can preserve a session, recognise a selected device path and help restore an interrupted mobile visit. Browser controls let you delete or block them, but necessary cookie changes may sign you out or require phone verification when you return.

Start with the account help path and label the request as a Privacy Policy concern. Mention whether it involves profile data, a DANA or QRIS reference, a device session or a correction. Do not include passwords, wallet PINs or one-time codes.

Related Pages

royal505 Indonesia Premier League Match Bet Account information FAQ Access guide