Reference

Your data choices stay clear

Open your account and we show exactly why we ask for identity, wallet, device, and contact details before you enter the lobby.

DANA recordsOVO wallet checksGoPay supportQRIS receipts
polobet Your data choices stay clear
CONTACT PATHS

Reach us about privacy quickly

Privacy questions should reach the team that can read your account record, not a generic inbox. Use the logged-in help centre when you can, because your account ID, device type, and recent wallet references travel with the message. For urgent access concerns, start chat and mention the affected phone number or email.

Team online

Live chat

Use live chat from 09:00 to 23:00 WIB for account access, cookie, or wallet-record privacy questions. We may ask you to confirm your registered phone number before discussing DANA, OVO, GoPay, or QRIS activity.

Email privacy desk

Email us for correction, copy, or deletion requests that need a written trail. Include your account name, registered email, and the exact data you want checked so we can route it without extra back-and-forth.

Account menu

Head to Account > Security > Active Devices to check recent sign-ins before contacting us. If a device looks unfamiliar, send the time, browser, and city shown so we can inspect the privacy log.

ACCOUNT CONTROL

How we handle private records

Privacy protection is built into the account flow you use every day. We separate contact details, wallet references, device history, and support messages so each team sees only what it needs.

Data we collect

We collect what you type during account opening, wallet references tied to DANA, OVO, GoPay, QRIS, device IDs, IP region, cookie settings, and messages you send to support. Each record is linked to your account timeline.

Why we use it

We use personal data to open your account, process wallet actions, keep session access secure, respond to privacy requests, and spot unusual account behaviour. Game-category history, such as live tables or slots, helps support verify context.

Cookie choices

Cookies keep you signed in, remember language and wallet display choices, and measure page errors. You can clear browser cookies on mobile or laptop, then sign in again if the lobby asks for a fresh session.

Device security

Active Devices shows browser, device type, and recent access timing. Use Account > Security > Active Devices after using a shared phone, then ask us to close sessions you no longer recognise.

Retention checks

We keep payment, support, and account records only as long as needed for service, security, dispute handling, and legal duties where local law permits. Older records are restricted or removed when they no longer serve that purpose.

Your requests

You can ask us to correct profile data, send a copy of account records, or remove data we no longer need. We verify your identity first so private wallet and device details stay with you.

Common privacy questions answered

These answers cover the privacy issues you are most likely to raise before opening an account or after seeing a wallet, device, or cookie record in your profile. For anything account-specific, contact us through chat or email so we can verify you first.

We ask for contact details, account login data, basic verification details, device signals, and wallet references. If you use DANA, OVO, GoPay, QRIS, or bank transfer, the payment reference is stored with your account.

Payment records help us match deposits, check withdrawals, answer disputes, and investigate account access issues. We keep only the references needed for those tasks and restrict who can view wallet details internally.

Yes. Contact the privacy desk from your registered email and tell us what data you want, such as payment history, device logs, or support messages. We verify your identity before sending anything private.

Sign in and check your profile first. If the field is locked, message support with your account name and the correct contact detail. Sensitive changes may require extra verification before we update the record.

Our cookies focus on sign-in, language, wallet display, error checks, and session security on our pages. Browser settings can block or clear cookies, but some account features may ask you to sign in again.

Only the teams needed to handle the request can see the relevant data. Support may view your contact path, payments may check wallet references, and security may inspect device logs tied to your account.

Retention depends on the record type and local requirements. We keep account, wallet, support, and security records while needed for service, disputes, and legal duties where local law permits, then restrict or remove them.