Reference

Privacy Policy for Your legal4d Account

Our Privacy Policy explains what legal4d collects when you open an account, use the mobile lobby, or check a DANA, OVO, GoPay or QRIS transaction.

Account dataWallet recordsDevice sessionsPolicy requests
legal4d Privacy Policy for Your legal4d Account
HELP WITH REQUESTS

Three Ways to Ask About Privacy

A clear contact route helps when you want to understand a data entry, correct an account detail or ask why a security check appeared. Start from the account support path so we can connect your request with the right login and wallet record. Include the date, the affected device and the relevant payment reference, but do not send a password or full wallet credential. We use the details you provide only to identify and handle the Privacy Policy request.

Team online

Account support path

Open the support contact path from your signed-in account when your request concerns phone verification, a device session or a profile detail. We can then compare the request with the account record without asking you to place a password in a message.

Wallet record check

For a DANA, OVO, GoPay or QRIS privacy question, include the transaction date and visible reference only. We use that limited context to locate the payment status, while the wallet provider remains responsible for its own account records.

Correction request

Tell us which account detail appears incorrect and what it should say. We may ask for a phone verification step before changing it, because a correction to your legal4d profile can affect future account access and security checks.

DATA CARE DETAILS

Six Practical Privacy Commitments

The Privacy Policy is designed around the actions you take in the lobby rather than vague promises.

Account details

We collect the details needed to create and maintain your account, including contact data used for phone verification. We do not ask you to place your password in a support request, and we use the account path to connect a request with the correct profile.

Session signals

Your phone or browser can send device type, session time and security signals when you move from login to the lobby. These records help us spot an unfamiliar session and protect access without treating a device signal as proof of your identity by itself.

Cookie controls

Cookies and similar storage can keep a session working, remember selected settings and help us understand whether a page request completed. You can restrict cookies in your browser, although some account and wallet steps may then require another sign-in.

Payment records

A DANA, OVO, GoPay or QRIS request can create a reference, amount status and time record for matching. We use that operational trail to check pending receipts; wallet credentials are handled through the relevant payment route rather than placed in a support message.

Retention period

We keep account, security and payment records only while they serve the stated operational purpose or a period required by applicable law. When a record is no longer needed, our handling process removes it, anonymises it or restricts further use.

Changes and contact

You can ask for access, correction or deletion through the signed-in support path. We may verify your phone or account control first, explain any reason a record must remain, and tell you what changed after we process a valid Privacy Policy request.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and device questions we expect when you consider opening legal4d from Indonesia. Each answer points you toward the practical step that applies, whether you are checking a wallet record, reviewing a phone verification request or asking for a change. If your situation is not covered, use the account support path and include only the details needed to locate your record. Eligibility depends on local law.

It covers account details, phone verification, device and session signals, cookies, payment references and requests to access or change your records. It applies when you create an account, sign in, use the mobile lobby or check DANA, OVO, GoPay and QRIS status.

Phone verification helps us confirm that the person requesting account access or a profile change controls the contact route on the account. We may use that step when a new device appears or when you ask us to correct or remove account data.

It covers the legal4d-side record of a DANA or QRIS request, such as its reference, time and status. The wallet provider keeps its own records under its own rules. Do not send us a wallet password, PIN or complete credential.

Use the signed-in account support path and ask for a Privacy Policy data copy. Include the contact route connected to your account and a short description of the records you need. We may verify account control before releasing or explaining the requested data.

Yes. Send a correction request through account support and identify the field that is wrong and the accurate replacement. We may require phone verification because changing contact details can affect login security, wallet matching and future requests connected with your account.

Retention depends on the purpose of the record and any period required by applicable law. Account, security and payment records may remain while needed for access, receipt matching or a legal request. We remove, anonymise or restrict records when that purpose ends.

Yes. Mention the approximate sign-in time, device type and account contact route through support. We use those details to locate the session signal and explain the security action. Never include your password, wallet PIN or a complete payment credential in the request.