Reference

Your Data Terms Before Account Access

Live Casino, Aviator, and Fishing God each create different account signals, so our Privacy Policy explains what we collect before you open an account and jump into the…

DANA data useOVO record checksGoPay and QRISCookie controls
jago78 Your Data Terms Before Account Access
CONTACT PATHS

Reach Us About Your Privacy

Privacy questions should not wait behind general account chat. Our support desk is available every day from 09:00 to 23:00 WIB through live chat and account message, with email used when you…

Live chat privacy queue Open Help > Live Chat and choose privacy concern so our agent sees your account ID, device type, and recent login time. We answer daily from 09:00 to 23:00 WIB.
Email for document checks Use email when a privacy request needs an attachment, such as a QRIS receipt or account correction proof. We confirm receipt, mask sensitive fields, and reply to the address on your profile.
Account message thread From Account > Messages, start a private thread if you want a data copy, cookie question, or payment record check. Keeping the request inside your account reduces identity back-and-forth.
ACCOUNT SAFETY

How We Handle Your Data

Your privacy choices sit inside the same flow you use for login, wallet checks, and session access.

Account data we collect

We collect the name, contact detail, login ID, and security answers you provide during account setup. These fields help us verify you before we discuss wallet records or privacy changes.

Payment record handling

DANA, OVO, GoPay, and QRIS references are used to match your wallet activity with your account. We do not place full payment app credentials inside your public profile or lobby screen.

Cookie and session checks

Cookies help keep you signed in, remember language choice, and detect unusual session changes. You can clear them in your browser, but you may need to log in again afterward.

Device safety signals

When your device, browser, or location pattern changes sharply, we may ask for a fresh login check. This protects your privacy request from being handled through the wrong account session.

Retention and deletion

We keep account and payment records only for operational, dispute, security, and legal needs. If you request deletion, we explain what can be removed and what must remain for required checks.

Correction requests

If your contact detail, payment reference, or login record is wrong, send the correction path through live chat or account message. We verify ownership before changing privacy-linked fields.

Privacy Questions You May Ask

You may want privacy answers before opening an account, after changing device, or when a DANA, OVO, GoPay, or QRIS record looks different from your wallet screen. These answers explain what we collect, how we use it, and how you can ask us to check, correct, or remove data tied to your account.

We collect the details you enter, your login ID, device signals, security checks, and wallet references tied to DANA, OVO, GoPay, or QRIS. We use them for account access, payment matching, and privacy request handling.

We use payment references to match wallet activity with your account balance and resolve disputes. Full payment app credentials are not shown in your profile, and sensitive receipt details are masked where possible.

Yes. Send the request through Account > Messages or live chat, then confirm your account ID and contact detail. We may ask a security question before preparing a copy linked to your profile.

Cookies keep your session active, remember basic preferences, and help detect unusual login patterns. If you clear browser data on Android or iOS, your privacy choice remains, but you may need to log in again.

Use live chat from 09:00 to 23:00 WIB or send an account message with the exact field that is wrong. We verify ownership before changing contact details, wallet references, or login records.

You can request removal through support, and we will explain which fields can be deleted. Some records may remain for payment disputes, security checks, or legal requirements where local law permits.

Only the support and account teams needed to handle your request can access the related thread. We keep the request tied to your account message or email case to avoid sharing extra data.