Reference

Privacy Policy for your royal378 account

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

Account dataWallet recordsCookie choicesRequest access
Explore Our Lobby Read FAQ
royal378 Privacy Policy for your royal378 account
CONTACT ROUTES

Ask about your account data

A direct request helps us find the right account record without exposing details to the wrong person. Contact our support channel from the signed-in account when possible, include the phone number linked to your account, and describe whether you need access, correction, deletion or a cookie explanation. We can also check a wallet reference or payment receipt when your question concerns DANA or QRIS activity.

Team online

Account support

Open the support route from your signed-in account and state the Privacy Policy request clearly. We use your account step and linked phone details to check identity before discussing records.

Wallet questions

For DANA, OVO, GoPay or QRIS records, attach the relevant receipt reference rather than sharing a wallet password. We use that reference to locate the related transaction entry.

Access concerns

If a login or device check blocks your request, tell us the device type and approximate sign-in time. We can route the matter to account support without asking for your password.

CONTROL DETAILS

Six controls behind our data handling

We keep this policy practical by linking each data use to an account action you can recognise.

Account creation

When you open an account, we record the details needed to identify it and complete phone verification before access. We do not need your game choices, such as Dragon Tiger, for that identity step.

Payment matching

A DANA, OVO, GoPay or QRIS reference may be stored beside the account action it supports. Bank transfer and virtual account records follow the same matching purpose for receipts and status checks.

Device records

We may record browser type, device signals and sign-in time to protect account access. A mobile session and a desktop session can therefore create different technical entries without changing your profile details.

Cookie choices

Cookies can remember a session and help us understand which account page loaded correctly. You can adjust browser cookie controls, although disabling them may require another sign-in during a later visit.

Retention periods

We keep account, support and wallet records only while they serve the stated purpose or a lawful recordkeeping need. When that period ends, records are deleted, anonymised or securely restricted.

Change requests

To correct or request removal of eligible data, contact support from your account and name the exact record. We may ask for a phone verification step before applying a change.

Privacy Policy questions Indonesia account holders ask

These Privacy Policy answers address the practical questions that arise before opening an account or contacting support. We focus on account records, local wallets, cookies, device access and requests, so you can choose the right support path without sending unnecessary personal details.

It covers account details, phone verification, device and browser records, cookies, support messages, and wallet references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Sign in, open the support route, and ask for an account data copy. Include your linked phone number and the record you want checked; we may verify account ownership first.

Yes. The Privacy Policy covers technical records from mobile browsers and desktop sessions, including device type, browser details and sign-in time used for account access checks.

We keep payment references to match a wallet action with the correct account, receipt or status check. We do not ask you to send a wallet password when handling that request.

Where local law permits, you can request a correction or removal of eligible data through account support. Tell us the exact record, and complete any ownership check we request.

Cookies can keep a sign-in session active and help identify whether an account page loaded correctly. Browser settings let you adjust them, but another sign-in may then be required.

Use the signed-in support route whenever possible and describe the concern in specific terms. For wallet records, add the receipt reference; for device issues, add the device type and sign-in time.

Related Pages

royal378 Indonesia royal378 Casino FAQ About Us Dice