Reference

Your Privacy Policy Before Account Access

Our Privacy Policy tells you exactly how account details, device signals, cookies, and DANA, OVO, GoPay, QRIS records are used before you open the lobby.

Account dataCookie controlsDANA OVO GoPay QRISWIB support
cuan123 Your Privacy Policy Before Account Access
CONTACT ROUTES

Get Privacy Help Without Waiting

Privacy questions need a clear route, not a long chase. Use live chat for account access issues, email for document requests, or the account form when…

Live chat Reach us through the chat button in the footer from 09:00 to 01:00 WIB.
Email request Send a privacy request to the address shown on our contact page when you…
Account form Open Account > Profile > Privacy Request after login to ask for a correction…
ACCOUNT SAFETY

Controls You Keep Over Your Data

Your privacy controls sit close to the account actions you already use. We separate login data, payment records, device signals, and cookie choices so a privacy request can be handled without exposing…

Minimal data

We ask for the account details needed to identify you, protect login access, and manage wallet records. If a field is not needed for those tasks, we avoid collecting it.

Payment records

DANA, OVO, GoPay, and QRIS references are stored with time, status, and account match data. This helps us trace deposits, review withdrawals, and answer wallet privacy questions.

Cookie controls

You can manage browser cookies through Android Chrome > Settings > Site settings > Cookies. If cookies are blocked, some login checks and session recovery steps may ask you to verify again.

Login security

We record device type, IP signal, and session time when your account signs in. These records help spot unusual access and support account recovery when you contact us.

Retention window

We keep account and payment records only for operational, security, dispute, and legal needs. When a record is no longer needed, we remove it or separate it from your profile.

Change requests

You can ask us to correct account data, check stored records, or review deletion where allowed. We verify the request through your registered email, phone, or login session first.

Privacy Policy Questions Before You Join

These answers explain the Privacy Policy points we get asked about most before an account is opened or updated. We keep the language practical: what data we collect, why it is needed, how payment references are handled, and how you can contact us. If your question involves access rights, local rules matter; service is available only where local law permits.

We collect the details needed to create and protect your account, such as registered contact data, login activity, device signals, and wallet records. Payment references are tied to your account for matching and support checks.

We use payment references to confirm deposits, review withdrawal requests, resolve wallet issues, and answer privacy questions. The record usually includes time, status, method, and account match data, not your full wallet login.

Yes. Use Account > Profile > Privacy Request or contact support with your registered email or phone. We verify account ownership first, then update eligible data or explain why a record must remain.

You can ask us to review deletion where local law permits. Some records may need to stay for payment checks, dispute handling, security logs, or legal duties before they can be removed.

Cookies may help keep your session active, remember language choices, and support security checks while you browse game pages. You can block cookies in your browser, but login verification may appear more often.

Access is limited to teams that need it for account support, payment checks, security monitoring, or privacy requests. We do not sell your personal data or publish your wallet activity.

Send your registered email or phone, the request type, date involved, and any DANA, OVO, GoPay, or QRIS reference. Do not send wallet passwords or full screenshots that reveal unrelated personal data.