Reference

Legal Terms For Your Account

Your account, wallet records, cookie choices, and access checks are handled under the legal terms published here.

Account termsData request pathCookie controlsDANA record checks
mbahslot Legal Terms For Your Account
CONTACT ROUTES

How To Reach Legal Support

Legal questions need a clear trail, so we separate them from general lobby chat. Send your account ID, registered phone number, payment method, and the date of the issue; we use those details to find the right record before replying.

Team online

Live Chat Handover

Open chat from your account menu and ask for legal help. Our team is available 09:00-23:00 WIB, then creates a case number so payment or data questions are not mixed with lobby messages.

Email Case File

Use the email path for document requests, account corrections, or written answers. Include your username, DANA, OVO, GoPay, or QRIS reference, and the device you used when the issue appeared.

Account Menu Request

From mobile, open Account, choose Help, then Legal Request. That path keeps your logged-in session attached to the case, which helps us verify ownership before changing stored account data.

DATA PRACTICE

How We Handle Legal Records

Our legal handling is built around account ownership, payment traceability, and clear contact steps.

Account Ownership

Before we discuss legal account details, we check your username, registered phone number, and recent login pattern. This step helps prevent another person from requesting changes to your wallet or personal data.

Payment Records

DANA, OVO, GoPay, and QRIS references are stored with transaction time, status, and account ID. If a wallet issue appears, we compare those records before giving a written answer.

Cookie Controls

Cookies help keep sessions active, remember language choices, and flag unusual account activity. You can clear cookies in your browser, but we may ask you to log in again after that change.

Retention Checks

We keep account and payment records for service, dispute, and legal handling needs. When data is no longer needed for those purposes, we remove or separate it from active service files.

Security Requests

If you report a lost phone or unknown login, we can pause sensitive account changes while we verify ownership. We may ask for a recent payment reference, not your wallet password.

Correction Path

If your name, phone number, or payment detail is wrong, send a correction request through chat or email. We review the account trail before updating records linked to withdrawals or access.

Questions About Legal Handling

These answers cover the legal questions we receive most often about accounts, payments, data, cookies, and access. Use them before contacting us so your request reaches the right team with the right details.

Your account is subject to the terms shown on this page and the account steps you accept during setup. Access to games and wallet features depends on local law and account verification.

We keep payment references so wallet disputes can be checked against account activity. The record usually includes transaction time, method, status, and account ID, not your wallet password or private app login.

Send a request through logged-in chat or email with your username and registered phone number. We verify account ownership first, then tell you what data can be shared or corrected.

Yes, you can request a correction for details such as phone number, name spelling, or payment reference. We check login and wallet records before making changes that affect access or withdrawals.

Cookies do not replace your account record, but they help keep sessions, language choices, and security signals connected. If you clear them, we may ask you to log in again.

We may restrict access when account checks, security concerns, or local rules require it. If this happens, contact support with your account ID so we can explain the next step.

Use the email case path for written legal answers. Include your account ID, registered phone number, payment method involved, and issue date so we can match the request correctly.