Reference

Open the lego4d Privacy Policy

lego4d Privacy Policy gives you a clear account of how we handle details linked to your account, device, login and wallet activity.

Account clarityWallet recordsDevice choicesContact access
lego4d Open the lego4d Privacy Policy
CONTACT ROUTES

Choose Your Privacy Support Route

A clear contact route helps you ask about the Privacy Policy without guessing which account team to reach. Send your request through the support contact shown on the lego4d site and include the account phone number or email connected to your profile. We use those details to locate the correct record, while you should avoid sending wallet passwords, verification codes or full payment credentials. Requests from Denpasar and other Indonesian locations follow the same privacy contact path where local law permits.

Team online

Account access

If you cannot open your account after phone verification, contact support with your registered contact detail and a short description of the issue. We may ask for additional account checks before discussing personal records, so an unknown person cannot use a login problem to obtain your data.

Wallet records

For a question about DANA, OVO, GoPay or QRIS records, share the transaction reference rather than your wallet PIN. We can use that reference to check the account event and explain what data is held, while keeping sensitive wallet credentials out of the support conversation.

Policy requests

To ask for a copy, correction or removal review under this Privacy Policy, state the request clearly and identify the account you control. We will explain the next verification step, any legal reason a record must remain, and the route for a further question.

DATA PRACTICES

Explore Our Account Data Practices

We keep this policy practical by linking each data category to an account action you recognise, such as login, phone verification or a wallet status check.

Account details

We may hold the contact details you submit when opening an account and the account identifier created for you. These records help us provide account access and respond to a privacy request. You can ask us to confirm, correct or explain the personal details attached to your profile.

Phone verification

Before account access, phone verification can connect a verified contact detail with your account record. We use that step to reduce mistaken access and to identify the right account during support. Never place a verification code in a public message or send it to another person.

Cookies and devices

Cookies and similar device records may remember session settings, support security checks and help the lobby load correctly on your phone or desktop browser. You can manage browser cookie settings, but blocking some cookies may affect login continuity or the way a privacy request is submitted.

Wallet activity

A payment reference, status and related account event may be retained when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use this record to match your request and resolve a status question; we do not need your wallet PIN for that check.

Security records

Login time, device type, browser details and unusual access signals can be recorded to protect your account. If you switch from a mobile browser to desktop and receive an extra check, that event may form part of the security record used to assess the request.

Retention and changes

We keep personal records only as long as needed for the stated account, security, support or legal purpose, subject to local requirements. Ask us to correct or remove eligible data through the support route; we will explain what can change and what must remain.

Browse Privacy Policy Questions

These Privacy Policy answers address the searches you may make before opening a lego4d account. They cover account records, device activity, local wallets, cookies, requests and access conditions. If your situation is not covered, contact us through the support path and include only the account detail needed to identify your request.

The lego4d Privacy Policy covers details you provide for an account, phone verification records, login and device signals, cookies, security events and payment references. It explains why we use each category, how retention works and how you can ask about access or correction.

DANA and QRIS can create account-linked payment references when you use those rails. Our Privacy Policy explains that we may retain the reference, status and related account event for support, security and record matching. We do not need your wallet PIN to answer a status question.

Yes. Contact us through the support route shown on the site, identify the account you control and describe the correction. We may complete an account check before discussing personal records. Our response will explain whether the requested change is possible under the Privacy Policy and local requirements.

Yes. It can cover device type, browser details, login events, cookies and security signals created when you use a mobile browser. These records help maintain account security and session continuity. You can adjust browser cookie settings, though some login functions may then behave differently.

We retain personal data for the account, security, support or legal purpose for which it is needed, subject to applicable local requirements. The exact period can differ by record type. Ask us about a specific account record, and we will explain the relevant retention position.

You can read this Privacy Policy without opening an account. A request for personal records generally requires an account or contact detail that lets us verify who is asking. Service access and eligibility remain where local law permits, and we will explain the available route.

Send the registered phone number or email, the request type and a short description of the record involved. For a DANA, OVO, GoPay or QRIS question, use the transaction reference. Do not send passwords, wallet PINs or verification codes with your Privacy Policy request.