Reference

Open With Clear Privacy Controls

Your account data, DANA wallet records, OVO and GoPay chip movements, and QRIS receipts are included in this Privacy Policy before you jump into Auto Roulette, Wild Bandito…

Account data scopeDANA recordsCookie choicesSupport requests
gemarbola Open With Clear Privacy Controls
CONTACT ROUTES

Ask About Your Privacy Request

Privacy questions need a channel that can confirm your account without spreading details across chat.

Live chat privacy check Send a privacy request through live chat from 09:00-01:00 WIB.
Email document route Use [email protected] when your request includes identity correction, payment matching, or a record export…
Account page message From your account area, open Profile > Help > Privacy Request to send a…
ACCOUNT CONTROLS

Manage Cookies and Account Records

Good privacy practice is visible in small account steps, not only in policy text.

Data collected at account opening

When you create an account, we collect the username, registered phone, email if provided, password credential, and referral tag if…

Payment record handling

DANA, OVO, GoPay, and QRIS transactions are stored as wallet records with timestamps, account references, and status values.

Cookie and device signals

Cookies help keep you signed in, remember language choices, and flag unusual login behaviour.

Session security view

Open Account > Security > Active Sessions to see recent device access.

Retention and deletion requests

Some records must stay longer because payment matching, dispute handling, or account security requires them.

Game activity privacy

Activity in Auto Roulette, Rocket Crash, Super Bingo, and Mega Fishing is tied to your account record for balance history…

Browse Common Privacy Questions

These answers focus only on how our Privacy Policy affects your account, wallet records, cookies, and contact choices. If your question involves a specific transaction, include the payment rail, time, and account ID when you write to us. That helps us answer without asking you to share extra personal data.

We collect the details needed to create and protect your account, such as username, registered phone, login credential, session data, and payment references. We do not ask for wallet passwords, PINs, or private OTP codes.

We use payment records to match deposits, verify withdrawal requests, and answer wallet questions. The record normally includes payment rail, time, status, and account reference, not your wallet password or private app login.

Yes, you can ask us to correct your registered phone, email, or name data when it is inaccurate. We may ask for account ID and a recent payment reference before changing sensitive profile details.

Cookies help keep your session active, remember basic preferences, and detect unusual access. On Android Chrome, check Settings > Site settings > Cookies if you want to clear or adjust site storage.

Support messages are handled by team roles that need them to answer your request. We keep privacy requests, payment matching, and account access questions inside support tools rather than public lobby areas.

Retention depends on why the record exists. Login logs, wallet references, and support messages may be kept while needed for account security, payment matching, dispute handling, or legal requirements that apply locally.

You can send a removal request through live chat or [email protected]. Some records may need to remain for payment matching or legal reasons, and we will explain the reason tied to your request.