Reference

Legal terms for your plasa4d account

plasa4d Legal gives you a clear route through account access, wallet checks and policy requests before you enter the lobby.

Policy accessWallet contextAccount controlsLocal-law wording
plasa4d Legal terms for your plasa4d account
POLICY CONTACT

Three routes for Legal questions

A clear contact path helps when a Legal question affects login, wallet status or a request to change account data. We ask you to describe the issue in plain English, include the account step where it occurred, and attach a payment receipt only when it is relevant. This lets us separate a policy request from a routine lobby question and check the correct record without asking you to repeat the same details.

Team online

Account access

If phone verification or a policy check pauses your account access, tell us which step appeared on your device. We can direct the request to the account path and explain whether the next action depends on local law.

Wallet records

For a Legal question involving DANA, OVO, GoPay or QRIS, include the wallet name and payment receipt reference. Our support route can compare that detail with the account record before explaining the applicable policy step.

Data requests

When you want a copy, correction or removal request considered, state the account detail involved and the reason for contact. We use that description to identify the right policy path and tell you what verification is needed.

DATA PRACTICE

How we handle Legal requests

Legal requests work best when your account record is current and the request is specific. We use the information needed to check account access, wallet status, security events and policy changes, rather…

Account data

We use account details such as your verified phone status to connect a Legal request with the correct account. If a detail is wrong, tell us which field needs correction and complete any identity check we request.

Cookies

Cookies can support session continuity between the Legal page and your account area. You can manage browser cookie settings on your device, but changing them may interrupt login or require you to verify the account again.

Account security

Never send a password or one-time phone code with a Legal request. We may ask you to confirm account ownership through the established account path, especially when a request could change access or payment details.

Record retention

We retain records when they are needed to resolve a policy question, check a payment receipt, protect account access or meet a local-law requirement. A request can ask what record is involved and why it remains necessary.

Policy changes

If a policy changes, we place the current wording on this Legal page and connect it to the relevant account step. Check the page before opening the lobby when you need the latest access or data-handling terms.

Requesting changes

To request a correction, access copy or removal of eligible data, describe the request clearly and use the support route. We may verify your account first, then explain what can change under the applicable policy.

Answers before you open an account

These Legal answers focus on the questions that arise before account access: jurisdiction, data, wallet records, cookies and policy changes. They are written for Indonesian account holders using the same mobile path as the lobby. If your situation is not covered, use the policy contact route with the account step, payment rail or device detail involved so we can direct you accurately.

Legal covers account access, jurisdiction wording, data handling, cookies, security checks, record retention and requests to change account information. It also explains how payment references from DANA, OVO, GoPay, QRIS or bank routes may be used when a policy question needs checking.

Access and eligibility depend on local law. You should continue only where local law permits and should check the rules that apply to your location. Our Legal page explains our account process, but it does not replace the requirements that apply in your jurisdiction.

Phone verification helps us connect an account request to the correct account before access or a data change is completed. It can also help when a wallet record needs checking. Do not send your one-time code in a support message.

Use the policy contact route and name the field that needs correction, such as a phone detail or account profile entry. We may verify account ownership before making a change, then explain whether the request can proceed under the current Legal terms.

When a request concerns DANA or QRIS, we may use the payment rail name and receipt reference to locate the relevant account record. Share only the details needed for the check. We do not need your wallet password or one-time code.

Yes. Your browser provides cookie controls, and you can adjust them on your phone or desktop. Some changes may interrupt the session between the Legal page and account area, so you might need to log in and verify access again.

Start with the current wording on this Legal page, then use the policy contact route if a point remains unclear. Include the section or account step involved. We can explain the relevant change and whether it affects access where local law permits.