Reference

emas168 Legal And Account Access

emas168 Legal gives you a clear view of account access, identity checks, data handling and contact routes before you open an account.

Account termsData and cookiesLocal access rulesContact routes
emas168 emas168 Legal And Account Access
POLICY CONTACT

Get Help With Legal Questions

A clear contact path helps when a Legal question affects your account or wallet status. We ask you to start from the signed-in support area so our team can connect your message with the correct account record. Include the policy heading, the account email or phone number, and any relevant receipt reference, while removing passwords and one-time codes from your message.

Team online

Account policy desk

Use the support path beside your account area for questions about eligibility, phone verification, account closure requests or a clause in the Legal notice. We can ask for account details to confirm that the request comes from you.

Wallet status contact

If a DANA, OVO, GoPay or QRIS record appears under the wrong account, send the payment receipt and reference through support. We use those details to trace the event without asking you to share a password or access code.

Policy change request

For a correction, access request or objection about personal data, identify the exact record and explain the change you want. We will route the message to the team handling Legal and data requests, subject to identity checks.

DATA SAFEGUARDS

How We Handle Your Legal Requests

The Legal process is tied to practical account controls rather than broad promises. We use the details needed to operate access, verify account ownership and trace payment records, then route requests to…

Data handling

We use account details, phone verification results and transaction references for access control, payment matching and support replies. We do not need your password in a Legal request, so leave it out of messages, screenshots and attached receipts.

Cookie choices

Cookies may help keep your sign-in path active, remember selected settings or connect a support session to the right account page. You can ask us which cookie category applies to a feature and request help changing available settings.

Account security

Phone verification helps us connect account access with the contact detail you provided. If your phone changes, contact support before attempting repeated access, and never send a one-time code to anyone claiming to handle your Legal request.

Record retention

We keep selected account, payment and contact records only as needed for service operation, dispute handling, security checks or a lawful obligation. A retention question should name the record involved so we can give a relevant response.

Who responds

Questions about a policy clause, personal data or account access are routed through the support area to the team responsible for that subject. This keeps a payment receipt question separate from a request to change stored details.

Change requests

You may ask us to correct inaccurate account details or explain how a particular record is used. We may request matching account information before making a change, and access remains subject to local law and the applicable Legal terms.

Answers Before You Open An Account

These Legal answers cover the searches we hear most often before account access. They explain where to find the policy, what may be requested during verification, how data questions are handled, and why a lawful access condition can differ by location. If your situation is specific, send the exact clause or account reference through the support path.

The emas168 Legal notice covers account access, phone verification, data handling, cookies, payment records, contact requests and account actions. It also explains that access depends on local law, so you should read the current text before opening an account or using a wallet-linked account path.

Access is available where local law permits and may depend on your location and account details. If you are in Indonesia, check the current Legal notice before opening an account. Our support team can explain the relevant policy wording without asking for your password.

Phone verification helps connect an account with the contact detail supplied during access. It can also help us identify the correct record when you ask about DANA, OVO, GoPay, QRIS or a bank transfer reference. Never share a one-time code in a support message.

Send the request through the signed-in support area and name the detail you want corrected. Include enough matching account information for us to confirm ownership, but exclude passwords and one-time codes. We will assess the request under the current Legal terms and applicable local requirements.

Cookies can support sign-in continuity, saved settings and account-linked support pages. The Legal and cookie text explains their purposes. If you want to ask about a cookie category or request a settings change, contact us with the page or feature concerned.

Retention depends on the record and the reason it is needed, such as account security, payment matching, dispute handling or a lawful obligation. Ask about a specific record through support, and we will explain the applicable handling under the current Legal terms.

Start from the support area connected to your account and quote the clause heading or section name. For a wallet question, add the DANA, OVO, GoPay or QRIS receipt reference. We can then send the question to the team handling that Legal subject.