Reference

Privacy Policy for Your Account

Your account data, DANA, OVO, GoPay, and QRIS records, device checks, cookie choices, and session logs are handled under this Privacy Policy before you enter Baccarat, Phoenix Rises…

Account data handlingPayment record contextCookie choice detailsDevice security checks
prda4d Privacy Policy for Your Account
CONTACT PATHS

Three Ways to Ask About Data

Fast answers reduce account friction, so we route Privacy Policy questions through the same service desk that sees wallet tickets and login checks. Tell us your account ID, the payment rail involved, and the device you used, such as Android Chrome or iPhone Safari. We answer in English for Indonesia, and we may ask you to confirm a recent QRIS or DANA reference before we discuss account records.

Team online

Live chat desk

Use live chat from the lobby footer when you need a quick privacy answer. Our team is available 09:00-23:00 WIB and may ask for your account ID before discussing login or wallet records.

Email privacy request

Send privacy requests to the support email shown inside your account page. Include your registered phone, last DANA, OVO, GoPay, or QRIS reference, and the exact data change you want us to check.

Account security path

Open Account > Security > Devices to see recent device entries before contacting us. If an entry looks wrong, send the date, browser name, and city shown on the login alert.

DATA HANDLING

How We Handle Six Data Areas

Practical controls make a privacy promise easier to verify. We separate account identity, payment records, device logs, cookies, support messages, and retention queues so a wallet question does not expose unrelated game…

Account identity

We store the details you provide during account setup, including username, registered phone, and security answers when used. Changes require account verification, so another person cannot rewrite your profile through chat.

Payment records

DANA, OVO, GoPay, and QRIS records are kept with timestamps, reference codes, wallet direction, and reconciliation status. We use them to match deposits, confirm withdrawal checks, and answer disputed wallet entries.

Device checks

Device data helps us spot unusual access, such as a new browser, repeated failed login, or location mismatch. You can compare entries through Account > Security > Devices before asking support to investigate.

Cookie use

Cookies keep your language, session state, and basic lobby preferences. You can clear cookies in Chrome or Safari, but doing so may sign you out and require fresh account verification.

Game-session logs

When you open Baccarat, Rocket Crash, Bingo, Fishing God, or Tennis Betting, we log session time and account activity. These records help resolve disputes without sharing your full wallet trail.

Retention requests

Some records must stay while a wallet dispute, security case, or legal duty is active. When those reasons end, we apply deletion or anonymisation schedules and confirm what changed where possible.

Seven Privacy Questions We Answer

You should know what happens to your details before you create a login, attach a wallet, or return from a new phone. These answers focus only on the Privacy Policy: account data, payment records, device checks, cookies, support messages, access requests, and retention. For faster help, keep your account ID and latest payment reference ready.

We collect the details you submit, such as username, phone, password credentials, and account preferences. We also create security logs when you sign in, change settings, or contact support about your account.

Yes. We keep payment references, timestamps, wallet direction, and reconciliation status so we can match deposits, verify withdrawals, and investigate disputes. We do not publish your wallet details on public pages.

Contact live chat or the support email listed inside your account. Tell us the field that needs correction, then complete ownership checks using your registered phone and a recent payment reference if requested.

Yes, go to Account > Security > Devices to view recent device entries. If a login looks unfamiliar, send support the date, browser, and entry shown so we can check related security logs.

Cookies help keep your session active, remember language choices, and reduce repeated login checks. You can clear them in your browser settings, but you may need to sign in again afterward.

Retention depends on the record type and reason for keeping it. Wallet disputes, security checks, and legal duties may require storage, while expired or unneeded records move to deletion or anonymisation queues.

Use live chat from 09:00-23:00 WIB or send the support email shown in your account. Include your account ID, registered phone, and the data request you want us to handle.