Reference

Privacy Policy For Your Account

Your privacy controls sit beside the same account flow you use for DANA, OVO, GoPay and QRIS, so we can explain what data is collected before you open…

Account data useDANA and OVO recordsGoPay and QRIS checksCookie controls
birutoto slot Privacy Policy For Your Account
HELP CHANNELS

Three Ways To Reach Privacy Help

Privacy requests need a clear route, not a long wait. We handle account-data questions every day from 09:00 to 23:00 WIB through live chat, the Help Center form and the account inbox after login. Before we discuss records, we may ask for your username, registered phone number and the last four digits of a payment reference so we do not release personal data to the wrong person.

Team online

Live chat privacy queue

Use live chat from the lobby footer between 09:00 and 23:00 WIB. Tell us whether you need data access, correction or deletion review, and keep your registered phone nearby for verification.

Help Center form

Open Account > Help Center > Privacy Request and attach a DANA, OVO, GoPay or QRIS reference only when it relates to the data question. We log the ticket under your account record.

Secure account inbox

After login, use Account > Messages for replies that include personal details. We avoid sending sensitive records through public chat screens, and we may split large data files into separate account messages.

ACCOUNT CONTROLS

Six Controls Behind Your Data

We wrote this Privacy Policy around the real actions you take inside your account: joining, logging in, opening slot rooms, checking live tables, funding through local rails and asking support for help.

Account registration data

When you join, we record your username, phone number, password marker and referral field if used. We use those details to create the account, prevent duplicate access and help you recover access after verification.

Payment privacy records

For DANA, OVO, GoPay and QRIS, we keep transaction references, time stamps and status markers. These records help us trace a wallet question without exposing your full payment app screen to wider support staff.

Cookie and device settings

Cookies keep your session active, remember language choice and protect login pages from repeated failed attempts. On Android Chrome, you can check stored site cookies through Settings > Site settings > All sites.

Game session markers

When you open Royal Fishing, Rocket Crash or live table pages, we record session IDs, start time and device type. These markers support dispute checks while keeping game activity tied to your account only.

Retention and deletion review

Some records must remain while wallet checks, security reviews or legal duties are active. When those reasons end, we reduce or remove personal data where our systems and local duties allow.

Correction requests

If your phone number, display name or payment reference is wrong, open Account > Profile or send a privacy ticket. We may ask for proof before changing data tied to wallet records.

Privacy Policy Questions We Hear Often

Before you open an account, you may want to know exactly what we collect and how you can control it later. These answers focus only on privacy: account records, payment references, cookies, device logs and request handling. If your question involves access to a service, the answer may also depend on local law, and we will say that clearly in the support reply.

We collect your username, registered phone number, password marker, device type and login time. If you add wallet activity later, DANA, OVO, GoPay or QRIS references are linked to your account for support and security checks.

We keep payment references so we can trace wallet questions, verify requests and match a transaction to the right account. We do not need your full app history; a transaction ID or time stamp is usually enough.

Yes. Send a request through Account > Help Center > Privacy Request. We verify your identity first, then prepare the account data we can share, excluding security signals that could weaken fraud checks.

Cookies keep you signed in, remember basic preferences and help detect repeated login failures. You can clear them in your browser settings, but you may need to log in again after removing site data.

Only staff assigned to support, account security or wallet tracing can view the ticket details needed for the request. We limit internal access by task, so unrelated teams do not receive your personal records.

You can request a correction through Account > Profile or the Help Center form. For changes tied to wallet activity, we may ask for a recent DANA, OVO, GoPay or QRIS reference before updating records.

We keep records while your account is active and while wallet checks, security needs or legal duties apply. When those reasons no longer apply, we reduce or remove personal data where local law permits.