Reference

Privacy Terms Before You Join

Your account data, payment confirmations for DANA, OVO, GoPay and QRIS, and session records around Live Baccarat, Great Rhino and Aviator are covered in this Privacy Policy before…

Account data useDANA and OVO recordsGoPay and QRIS checksCookie controlsSupport contact paths
bakwan4d Privacy Terms Before You Join
CONTACT ROUTES

Privacy Help Without Guesswork

A privacy question should reach the right desk fast, not sit inside a game chat thread. Use the contact route that matches your issue: account access, wallet record, or cookie preference. Our support desk is available every day from 09:00 to 23:00 WIB through live chat and email, and we may ask for a recent login time or payment reference before discussing account-specific details.

Team online

Live chat privacy queue

Open live chat from the account menu and choose the privacy topic before typing your question. We use that queue for correction requests, cookie questions, and recent sign-in checks during 09:00 to 23:00 WIB.

Email request record

Send privacy requests from the email address linked to your account so we can match the sender safely. Include your username, device type, and one recent DANA, OVO, GoPay or QRIS reference if payment data is involved.

Account page checks

Use Profile, then Security, to review your active device sessions before contacting us. If you see a phone or browser you do not recognise, tell support the device label and last access time.

DATA PRACTICE

Controls Built Into Your Account

Privacy handling is part of the account flow, not a separate promise on a forgotten page.

Account details

We store the username, contact channel, password status, and account settings you provide during registration or later edits. These records help us verify you before support changes profile details or discusses wallet activity.

Payment references

Wallet records may include DANA, OVO, GoPay and QRIS transaction IDs, timestamps, sender labels, and status messages. We use them to match deposits, check withdrawal requests, and answer payment privacy questions with the right record.

Device signals

We read basic device signals such as browser type, IP range, session time, and login path. These signals help us spot unusual access when your account moves from mobile web to another browser.

Cookie choices

Cookies keep sign-in sessions, language preference, and lobby loading behavior consistent. You can remove them from your browser settings, then sign in again if you want the account to create a new session record.

Retention handling

We keep account and payment records only for operational, security, support, and legal needs. When a record is no longer needed for those purposes, we remove it from active tools or restrict access.

Change requests

You can ask us to correct account details, check stored contact data, or explain a payment record. We may request one account step, such as last login time, before making any privacy-related change.

Answers About Your Privacy Rights

Privacy requests work better when you know what to ask for and which detail proves the account is yours. The answers below focus on data we collect, payment records we keep, cookie use, device sessions, and how you can reach us. If your request involves access or eligibility, our answer will use the standard frame where local law permits.

We collect the account details you submit, such as username, contact channel, password status, device session, and security settings. We also record support messages and wallet references when you use DANA, OVO, GoPay or QRIS.

We keep payment references so your wallet actions can be matched, checked, and answered later. A record may include transaction time, payment rail, status message, and sender label, not your full private wallet login.

Yes. Contact us through live chat or the email linked to your account and explain what needs correction. We may ask for your username, last login time, or one recent payment reference before changing stored details.

Cookies keep your session active, remember basic preferences, and help the lobby load correctly on mobile browsers. You can clear cookies in your browser settings, but you will need to sign in again afterward.

We share only the details needed to process or confirm a transaction through DANA, OVO, GoPay or QRIS. We do not send unrelated lobby activity unless it is needed for security, support, or legal handling.

Go to Profile, then Security, and look for active sessions or recent sign-in details. If a device label or browser time looks wrong, contact support from 09:00 to 23:00 WIB with the device detail.

We keep privacy request records long enough to answer your question, verify the account action, and maintain a support trail. After operational or legal need ends, we remove them from active tools or restrict access.