Reference

Legal terms for your lim4d account

lim4d Legal sets out how account access, privacy, payment records and policy requests work before you enter the lobby.

Account termsPrivacy choicesPayment recordsPolicy contacts
lim4d Legal terms for your lim4d account
CONTACT ROUTES

Get help with a Legal request

A clear contact route helps when a policy question affects your account, payment record or access status. Start from the support path in your account area and include the subject of your request, the phone number connected to the account and any relevant receipt reference. We use those details to direct the question without asking you to resend unnecessary personal data.

Team online

Account policy path

For a question about Legal access, phone verification or account details, open the support route beside your account area. Tell us which policy wording you are asking about and we can direct the request to the relevant team without requiring a new account.

Wallet record check

If DANA, OVO, GoPay or QRIS activity needs clarification, include the wallet name and payment receipt reference in your request. For bank transfer or virtual account questions, add the bank rail used so we can separate a policy query from a payment-status query.

Access clarification

When access is unavailable, ask through the account support path and state your location and the step where access stopped. We can explain the applicable policy wording, but access or eligibility depends on local law and cannot be changed by a support request alone.

DATA PRACTICES

How we handle Legal matters

Legal questions often involve more than account access, so our handling separates identity checks, payment evidence and privacy requests.

Data purpose

We connect account data to the specific Legal task being handled, such as phone verification, access clarification or a payment record check. When you contact us, provide only the details needed to identify the request, rather than sending unrelated identity documents.

Cookie choices

Cookies can support the account session and help remember the path you used to reach a Legal page. Your browser controls whether cookies remain available. If a setting affects access, contact us through the account support route and describe the device behaviour you see.

Account security

Keep the phone connected to your account private and do not share verification codes with another person. If you suspect that account details were changed without your approval, use the support path before submitting another wallet payment or withdrawal request.

Record retention

We retain account, verification and payment records for the period needed for the stated account, legal or transaction purpose. A request about retention should identify the record type, such as QRIS receipt, bank transfer reference or phone verification entry.

Correction requests

To request a change, use the support route in your account area and name the exact field or record that appears wrong. Include the corrected detail and a reason for the request; we may need to compare it with the account or payment evidence.

Policy ownership

Our support team receives Legal questions and routes them according to subject: account access, privacy, payment records or policy wording. You remain responsible for the accuracy of your submitted details, while eligibility continues to depend on local law.

Answers about lim4d Legal terms

These Legal answers cover the questions we expect you to ask before opening an account or sending a payment. They explain the account step, local access wording, privacy requests and the support route for records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

lim4d Legal covers account access, phone verification, privacy choices, cookies, payment records, data requests and policy contacts. It does not replace local law. Where access or eligibility is discussed, the applicable position depends on local law and your location.

Yes. Access or eligibility depends on local law. We may ask for your location and account details when a policy question affects access. Completing phone verification does not override a local restriction or create permission where the service is not allowed.

You need to complete the phone verification requested for your account before access can be confirmed. Use your own current details and keep the connected phone private. If the verification step fails, use the account support path rather than creating duplicate records.

DANA and QRIS records may be checked when a payment question needs evidence. Keep the receipt reference and submit it through the account support route. We use the record for the stated query and may compare it with the account details supplied during verification.

Yes. Use the support path in your account area, identify the exact detail that needs correction and provide the replacement wording. We may ask for matching account or payment evidence before changing a phone, identity or transaction record.

Send a privacy request through the account support route and state whether it concerns cookies, account data, phone verification or payment records. Naming the record type helps us route the request and explain the applicable handling or retention basis.

Open the account support path and include the withdrawal reference, account phone number and payment rail involved. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account matters, we may verify the record before explaining the policy position.