Reference

Open Your Privacy Policy First

Your DANA, OVO, GoPay and QRIS wallet records, login sessions, and device checks are covered here before you open an account.

DANA wallet contextOVO record handlingGoPay account checksQRIS receipt data
jp1131slot Open Your Privacy Policy First
CONTACT ROUTES

Check Your Privacy Contact Paths

A direct privacy channel saves time when you want to correct data, ask about a stored receipt, or check why a device session appears on your…

Live chat privacy desk Open live chat between 09:00 and 23:00 WIB and choose Privacy Request.
WhatsApp account check Use WhatsApp when you need a private record checked while away from the lobby.
Email data request Send privacy email requests to [email protected] with your username and the data topic.
DATA CONTROLS

Browse Your Account Data Controls

Clear controls matter when your account touches wallet rails, cookies, live table sessions, and support chats.

Data we collect

When you open an account, we collect your username, password record, contact check, wallet rail choice, IP signal, and device type. Game names such as Super Bingo or Royal Fishing create session logs, not public profile data.

Cookie choices

Cookies help keep you signed in, remember language display, and detect repeated failed access attempts. You can clear browser cookies on Chrome or Safari, then sign in again for a fresh session.

Wallet record handling

DANA, OVO, GoPay, and QRIS records are used to match account wallet activity with payment provider receipts. We keep references, time stamps, and status notes so support can trace a dispute accurately.

Device security

Account > Security > Active Devices shows recent device sessions linked to your profile. If a phone, tablet, or computer is unfamiliar, contact us and we will help close that session after ownership checks.

Retention checks

We keep account and wallet records while needed for service, security, dispute handling, and legal record duties. When retention is no longer required, we remove or anonymise data through scheduled internal checks.

Correction requests

Account > Privacy Request is the path for correcting contact details, duplicate support notes, or a mistaken device label. We may ask for email or phone confirmation before changing private account data.

Explore Privacy Policy Questions

These answers cover the privacy questions we receive most often before and after an account is opened. They focus on account data, wallet records, cookies, device sessions, and request handling. If your question involves a personal record, contact us through live chat, WhatsApp, or [email protected] so we can verify ownership first.

We ask for account details needed to create access, such as username, password record, phone or email check, and wallet rail choice. Security signals like device type and login time help protect the account.

We keep payment references, status notes, time stamps, and provider labels so your wallet activity can be matched with your account. We do not display those details publicly or share them for unrelated marketing.

Login and device records help us detect unusual access, repeated failed passwords, and sessions from unfamiliar devices. You can check them under Account > Security > Active Devices and ask support to close a session.

Use Account > Privacy Request or email [email protected] with your username and the field you want corrected. We may confirm your phone, email, or recent wallet rail before making the change.

Cookies store session and preference signals, such as staying signed in or remembering language display. They do not replace account records. Clearing cookies may log you out, and you can sign in again afterward.

Only the customer-care and security staff assigned to privacy handling can view your request details. If a payment trace is involved, limited wallet fields may be checked against the relevant provider record.

We keep account data while needed for service access, security checks, dispute handling, and legal record duties. After that need ends, records are removed or anonymised through our scheduled data-retention process.