Reference

lego138 Privacy Policy For Your Account

Our Privacy Policy explains how lego138 handles the account, wallet and device data needed for your access.

Account dataWallet recordsDevice choicesPolicy requests

How Your Wallet Data Is Used

lego138 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect details you submit when opening or using an account, such as your contact details, phone verification result and selected account settings. We also receive operational records from payment steps, including DANA, OVO, GoPay, QRIS, bank transfer and virtual account references, so we can match

1
a transaction to the correct account. Device details, login times and security events help us identify unusual access and keep sessions working across mobile and desktop paths. We use this data to provide account access, process requests, answer policy questions and meet applicable legal duties. We
2
do not describe access as available everywhere: eligibility depends on local law. Where local law permits, you can ask us to explain, correct or remove data, subject to records we must retain for security, dispute handling or legal reasons.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST A HAND

Get Policy Help Near Your Account

A clear contact path matters when you need to ask about Privacy Policy choices or a wallet record. Start from the support route connected to your account and include the phone or email used for access, without sending a password. We can then locate the relevant account step, payment reference or device event and direct your request to the right policy contact.

Team online

Account support path

Use the support path inside your account to ask how lego138 stores contact details, phone verification records or login events linked to your Privacy Policy request.

Wallet record query

For DANA, OVO, GoPay or QRIS records, provide the transaction reference and date. We use those details to locate the payment entry without requesting your wallet password.

Access request

If you cannot open the account route, request help through the contact path shown with account access. Eligibility and any data request outcome depends on local law.

HANDLING YOUR DATA

Privacy Choices That Stay Practical

Our Privacy Policy is designed around the actions you actually take: opening an account, verifying a phone, signing in from a device and checking a wallet record.

Account data

We use contact details and phone verification results to create your account path, confirm that a sign-in request matches your record and respond to account-related Privacy Policy requests.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a wallet action to your account. We do not need your wallet password to investigate a status.

Cookies and sessions

Cookies and similar session data help remember sign-in state, protect account actions and maintain the mobile path to the lobby. You can adjust browser controls, though some account functions may stop working.

Device security

We may record device type, browser signals, login time and security events to detect unusual account access. These checks support account protection without turning device data into a public profile.

Retention period

We keep account, payment and security records only as long as needed for service operations, dispute handling, fraud checks or legal duties. When a period ends, deletion or de-identification follows our internal process.

Changes and contact

Ask us to correct account data, explain a processing step or address a permitted removal request through the account support route. Include the email or phone linked to your record for verification.

Privacy Policy Answers For lego138

These Privacy Policy answers cover the questions we expect before you open an account or connect a local wallet. They explain the data linked to access, how requests are checked and where local rules affect the response. For a case-specific answer, use the support path attached to your account.

It covers account details, phone verification, payment references, cookies, device signals, security events, retention and requests to correct or remove data. It also explains how we respond to policy questions.

Phone verification helps connect a sign-in or account request to the correct record and reduces mistaken access. We use the result for account operations and security checks described in the Privacy Policy.

Yes. The Privacy Policy covers payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. These references help us match a wallet action without asking for your wallet password.

We may record device type, browser signals, login timing and security events. The purpose is to maintain sessions and identify unusual account access, not to create a public profile about you.

You can request a correction through the account support route. Include the phone or email connected to your record so we can verify the request. The available remedy depends on local law.

Retention depends on the type of record and its purpose. We keep account, payment and security details for operational, dispute or legal needs, then follow deletion or de-identification procedures.

Use the support path shown inside your account, or the contact path provided when account access is unavailable. Do not send a password; provide only the identifying details needed for verification.

lego138 Privacy Policy For Your Account

Get Policy Help Near Your Account

Account support path

Wallet record query

Access request

Privacy Choices That Stay Practical

Account data

Payment references

Cookies and sessions

Device security

Retention period

Changes and contact

Privacy Policy Answers For lego138

01 What does the lego138 Privacy Policy cover?

02 Why does lego138 need my phone verification data?

03 Does the Privacy Policy cover DANA and QRIS records?

04 What device data does lego138 collect?

05 Can I ask lego138 to correct my account data?

06 How long does the Privacy Policy keep my records?

07 Where can I ask about a Privacy Policy request?

Related Pages