Reference

erek erek 83 Legal: Clear Access Rules

Legal at erek erek 83 explains how account access, wallet records and policy requests work before you enter the lobby.

Access depends on local lawPhone verification before entryPolicy requests through supportDANA, OVO and QRIS context
erek erek 83 erek erek 83 Legal: Clear Access Rules
CONTACT ROUTES

Reach us about Legal questions

A clear contact route matters when a Legal question affects your account or wallet record. Start with the account support path and include your registered phone number, request type and any relevant payment reference; do not send a password. If the question concerns access from Jakarta, tell us the device path you used, such as a mobile browser, so we can match the request to the correct account step.

Team online

Account access requests

Ask through the account support path when phone verification, a changed phone number or a policy question prevents access. Include your registered contact and request details so we can check the account record without asking for your password.

Wallet record questions

For DANA, OVO, GoPay or QRIS questions, send the payment reference and wallet name through support. We use those details to locate the relevant record and explain whether the request concerns account status, transaction matching or Legal wording.

Policy change requests

If you want a correction, clarification or access request handled under our Legal notice, state the exact change you seek. Our support path can connect the request to your account record and explain the next required step.

DATA PRACTICE

How we manage Legal requests

We handle Legal requests around the account record rather than treating them as general lobby messages.

Account data

We use account details such as your registered phone number to connect a Legal request with the correct record. Phone verification helps us distinguish an account-holder request from an unverified message before access or data changes are considered.

Cookie controls

Cookies can keep a browser session connected to the account path and help us understand whether a request follows a valid login step. Check your browser controls if you want to remove or restrict cookies before returning.

Security checks

We do not ask you to place a password in a support message. When a Legal request affects account access, we may compare the registered phone, verification step and request details before discussing the record.

Request retention

We retain the request details needed to trace a Legal question, including its account reference and response history. Keeping that trail helps us explain a prior decision when a wallet or access matter is raised again.

Correction requests

You can ask us to correct account details that are inaccurate or no longer current. State the field to change and provide the matching account reference; we may require phone verification before applying an update.

Policy contact

For a Legal question, contact us through the account support route with a short description and relevant reference. We will identify the applicable wording, explain the next step and avoid treating a policy request as a lobby question.

Legal answers before account access

These Legal answers cover the questions we expect before an account is opened or a wallet record is checked. Read them alongside the current notice, especially when access, data handling or a policy request may affect your next step. Where local law permits, the published wording applies to the relevant account activity.

Legal covers account access, phone verification, wallet records, cookies, security checks, request retention and ways to ask for a correction or clarification. It also explains that access depends on local law, so the current notice should be checked before you proceed.

Access depends on local law and may differ by location or circumstance. We do not describe access as universal. Check the current Legal notice before opening an account, including when you are connecting from Jakarta, Yogyakarta or another Indonesian location.

Phone verification connects an access request to the account record and helps prevent an unrelated person from changing details. We may request it before discussing account data, correcting a phone number or processing a Legal request.

DANA and QRIS references are treated as transaction context linked to the account record. If you ask about a wallet matter, provide the payment reference and wallet name through support; do not include your password or private login code.

Yes. Send a correction request through the account support path and identify the field that needs changing. We may compare your registered phone and complete a verification step before applying the change or explaining why more detail is needed.

We keep request details for the period needed to trace the question, account reference and response history. The record supports later clarification about access or wallet matters. Ask support if you need the retention wording connected to your request.

Use the account support route and describe the exact policy wording or account step you want clarified. Include a relevant reference, but never a password. We can explain the current Legal notice and the next step where local law permits.