Reference

Your Privacy Clarity Before You Join

Baccarat, Asgardian Rising, and MotoGP Betting sit behind one account, so this Privacy Policy explains the data we use when you join, log in, fund with DANA, OVO…

Account data explainedCookie use statedDANA and QRIS recordsPrivacy request route
mahkota 78 Your Privacy Clarity Before You Join
CONTACT PATHS

Reach Us About Privacy Requests

Privacy questions should not sit in a general chat queue without context.

In-account request Open Profile > Help > Privacy Request, choose correction, access, deletion, or cookie question…
Live chat handoff Use live chat between 10:00 and 02:00 WIB if you need help finding the…
WhatsApp follow-up If a privacy case needs identity checking, we may confirm a masked phone number…
PRIVACY CONTROLS

Controls That Keep Your Data Clear

Clear privacy handling makes it easier for you to open an account with confidence. Our policy links data collection to real account steps: registration, login, wallet use, gameplay records, support contact, and…

Account registration data

We collect the name, phone number, login credential, and account contact details you provide when joining. These details let us identify your account, send security alerts, and handle privacy requests tied to that account.

Payment privacy records

DANA, OVO, GoPay, and QRIS activity creates wallet records showing time, amount, status, and account match results. We keep those records to resolve payment questions, detect mismatches, and meet operational record needs.

Device and login checks

Account > Security > Devices shows recent device sessions where available. We use IP address, browser type, device signals, and login time to flag unusual access before your wallet or privacy settings are changed.

Cookie use

Cookies help keep you logged in, remember language choice, and measure page errors. Optional tracking is separated from session cookies, and you can clear browser cookies through your device settings at any time.

Record retention

We keep account and wallet records only for the period needed for service, security, dispute handling, and legal record duties. When data is no longer needed, we remove it from active tools or restrict access.

Request handling

Privacy requests are logged with a case reference, request type, and account check status. We may ask you to verify phone access before changing records that affect your wallet, login, or security settings.

Privacy Questions You May Ask

The questions below focus only on how our Privacy Policy works for your account. They cover account data, payment records, cookies, device checks, correction requests, and contact routes. If your case involves access to the lobby, eligibility depends on local law; if it involves data rights, start from your account so we can verify the request securely.

We collect the details you enter during registration, such as name, phone number, login credential, and account contact data. We also store account status, security events, and wallet records linked to your activity.

Those payment rails create records we need to match wallet activity with your account. The policy explains that we store transaction time, amount, status, and matching results so privacy requests can be handled accurately.

Yes. Use Profile > Help > Privacy Request and choose account data access. We will verify your account, prepare key records we can share, and reply through your account message thread.

Submit a correction request from your logged-in account and include the field that needs changing. For wallet-linked details, we may ask for extra verification before updating records connected to DANA, OVO, GoPay, or QRIS.

We may record device type, browser, IP address, approximate location, and login time. These checks help us spot unusual access before changes are made to your wallet, password, or privacy settings.

Session cookies keep you logged in and help pages load the right account state. Optional cookies may measure errors or page use, and you can clear them through your browser settings whenever you choose.

We keep records for service, security, dispute handling, and legal record duties. When we no longer need a record in active tools, we remove it from working systems or restrict access to it.