Reference

Open Your Privacy Controls

Clear privacy controls, named payment-record handling, and a direct request path sit behind your account from the first login.

DANA record checksOVO privacy handlingGoPay request trailQRIS data controlsCookie choices
hantam303 Open Your Privacy Controls
CONTACT PATHS

Open A Privacy Request

Fast privacy help starts with the right channel and enough account context. We handle privacy questions through live chat, email, and the account center, with support available daily from 09:00 to 01:00…

Live Chat Message us from the lobby footer between 09:00 and 01:00 WIB. We ask for your registered phone or email, then move privacy conversations into a private thread before discussing account records.
Email Desk Send privacy requests to [email protected] with your account ID, payment rail involved, and the date range. We answer in English and may request one extra check before changing stored data.
Account Center Use Account > Security > Active Sessions to see device activity before you contact us. That path helps you point to a phone, browser, or session that needs a privacy check.
ACCOUNT SAFEGUARDS

Browse Our Privacy Safeguards

Privacy is handled inside the same account workflow you use for login, wallet checks, and support contact.

Data We Collect

We collect the details needed to run your account: phone, email, login time, device type, IP region, payment reference, and gameplay records such as Dragon Tiger or Ganesha Gold session IDs.

Payment Records

DANA, OVO, GoPay, and QRIS data is logged as transaction references, not full wallet contents. We use those records to reconcile deposits, confirm withdrawals, and answer privacy requests tied to your account.

Cookie Controls

Cookies remember language, session status, and basic security signals on your phone browser. You can clear them in your browser settings, but the next login may require a fresh verification step.

Account Security

Two checks matter most: your password and the code sent during sensitive account actions. If a new device appears in Active Sessions, contact us before you share any screenshot or document.

Record Retention

We keep account and transaction records only for operational, dispute, security, and legal needs. When a record no longer serves those needs, we remove it from active systems on a scheduled cycle.

Correction Requests

Ask us to correct phone, email, name spelling, or payment reference errors through chat or email. We may compare DANA, OVO, GoPay, or QRIS receipts before changing wallet-related records.

Check Your Privacy Questions

These answers focus on practical privacy questions you may ask before or after opening an account. We explain what we collect, why payment references matter, how cookies work, and how you can contact us when a stored record looks wrong. For account-specific requests, we verify your identity before sharing or changing private records.

We collect your phone, email, login details, device type, IP region, and account activity. If you use DANA, OVO, GoPay, or QRIS, we also store payment references needed for matching and support.

We share only the details needed to process, trace, or reconcile a transaction. For DANA, OVO, GoPay, and QRIS, that usually means a reference number, amount status, time, and account match.

Cookies keep your session active, remember language choices, and help flag unusual access. You can clear them in your browser settings, but your next login may ask for another verification step.

Yes, you can contact us by chat or email and ask for account records tied to your profile. Access depends on local law, and we verify your identity before sharing private data.

You can request deletion through [email protected] or live chat. Some records may need to remain for transaction disputes, security checks, or legal duties, and the outcome depends on local law.

Session records help us answer disputes, check unusual account access, and trace technical issues. A Dragon Tiger, Rocket Crash, or Bingo session ID is handled as account data under this policy.

Send the correction request with your account ID, the field that is wrong, and a recent payment reference if wallet data is involved. We verify the request before changing stored records.