Reference

Legal clarity for your zen666 account

zen666 Legal explains how we handle account access, wallet records, personal data and requests to change your details.

Account access rulesWallet record handlingData request pathPolicy contact steps
zen666 Legal clarity for your zen666 account
CONTACT THE POLICY TEAM

Get a clear answer on Legal

A policy question should not leave you guessing about your account. Start from the support route shown after login and include the account detail, wallet rail…

Account access Tell us which login step stopped you and whether phone verification was completed.
Wallet records For DANA, OVO, GoPay or QRIS questions, include the rail name and receipt reference…
Policy changes If you want to question a restriction or request a policy change, state the…
DATA AND ACCOUNT CARE

How we handle your Legal requests

We keep this policy practical by linking each request to the account step or transaction that caused it.

Account data

We use the details attached to your account to process access, phone verification and policy requests.

Cookies and sessions

Cookies and session markers can help keep your login path consistent between the account screen and lobby.

Account security

Do not send a password, wallet PIN or one-time code in a support message.

Payment records

A payment record can include the rail, reference and account match needed to resolve a status question.

Retention questions

Ask us how long a particular account or payment record is retained by naming the record type and date.

Change requests

To request a correction, identify the field that needs changing and provide the account step where it appears.

Answers before you open an account

These Legal answers address the questions we expect you to ask before using an account in Indonesia. Read the full policy notice when your question concerns a restriction, a data request or a transaction record. If a clause still does not fit your situation, use the support route shown after login and include the relevant account step.

It covers account access, phone verification, payment records, cookies, data handling, retention and requests to correct account details. Access depends on local law, so the terms should be read together with any restriction or eligibility message shown during your account journey.

Access is available where local law permits. If you are in Indonesia, check the access message shown during account creation and complete the requested phone verification. Do not continue if the page indicates that access is not available for your location.

We may retain the rail name, reference and account match needed to check a transaction request. A DANA or QRIS receipt lets us identify the event you are asking about, but you should never send a wallet PIN or one-time code.

Use the support route displayed in your account, name the field that is incorrect and explain where it appears. We may ask you to complete phone verification before changing personal details or connecting a corrected record to the account.

Read the restriction message first, because it may identify the required account step or legal condition. Where local law permits, you can ask for clarification through the displayed support route and include the message reference without sharing private login codes.

Name the record type, such as an account detail, QRIS receipt or bank transfer reference, and give its date through the policy contact path. We assess the request under the applicable Legal terms and explain why a record is retained when required.

A new phone or browser can trigger an additional security check because session details have changed. Complete the account step shown on screen, then contact support through the displayed route if the check does not match your verified phone.