Reference

Open Your Account With Clear Privacy Terms

Our Privacy Policy explains what we collect when you open an account, log in, use DANA, OVO, GoPay or QRIS, and move between Caishen Wins, Live Football Odds…

Account data explainedCookie use made clearDANA and QRIS contextSupport request paths
bintang4dp Open Your Account With Clear Privacy Terms
CONTACT PATHS

Check Privacy Help Before You Continue

A privacy question should not sit in a queue without context.

Live chat verification Start with live chat when you need a quick privacy check.
Email privacy request Use email for access, correction or deletion requests that need written follow-up.
Account page route From mobile or computer, open Account, choose Profile, then check Contact Details before sending…
DATA CARE

Browse With Practical Privacy Controls

We handle privacy as part of daily account operation, not as a separate promise page. Login records, cookie settings, payment references and support transcripts are kept so we can run the wallet…

Account details

We collect account data you provide directly, such as login name, phone number, email and profile updates. These details let us confirm access, respond to privacy requests and keep one account tied to one contact path.

Payment references

DANA, OVO, GoPay and QRIS records are used to match deposits and withdrawals to your wallet. We store transaction references and status details, not full private banking access from your payment app.

Cookie settings

Cookies help keep your session active, remember device choices and detect unusual login patterns. You can clear browser cookies through your device settings, then log in again to rebuild a fresh session.

Device and session logs

We record device type, IP range, login time and browser data when you access the lobby. This helps us spot account takeover attempts before wallet or profile changes are accepted.

Retention checks

We keep account and payment records only as long as needed for operation, dispute handling, legal duties and security checks. After that, we remove or separate data when the request and rule allow it.

Correction requests

If your phone number, email or profile detail is wrong, contact us before adding funds. We verify the request through your current account channel, then update the record after identity checks are complete.

See Common Privacy Questions Answered

These answers explain how our Privacy Policy works when you create an account, use local wallets, clear cookies or ask us to change data. If your question involves another person, shared device or payment mismatch, contact us before sending documents. We will ask for proof that links the request to your account and will not discuss private records through an unverified channel.

We collect the details needed to create and protect your account, including login name, phone number, email, password data and profile updates. We also record device and session details when you access the lobby.

We keep payment references, wallet status and transaction matching data so your account balance can be checked. We do not receive full private access to your DANA, OVO, GoPay or QRIS app.

Cookies keep your session active, remember browser choices and help detect unusual access. On Android or iOS, you can clear site data in browser settings, then log in again with your account details.

Yes, you can request account data through live chat or email after identity checks. Access depends on local law, account status and whether the request would expose another person’s private data.

Open Account, check Profile, then contact support if the detail cannot be changed inside the page. We verify your current login, registered contact and recent activity before applying the correction.

You can ask us to delete or reduce stored data by email. Some records may stay for payment disputes, security checks or legal duties, and the final handling depends on local law.

Only the verified account holder can receive account-specific privacy answers. We may discuss general policy by chat, but wallet records, login history and profile data require matching contact and identity checks.