Reference

Privacy Policy for Your lego138 Account

We keep your Privacy Policy choices close to the account flow: the wallet asks only for the details needed for DANA, OVO, GoPay, and QRIS records, while your…

DANA recordsOVO checksGoPay matchingQRIS references
lego138 Privacy Policy for Your lego138 Account
CONTACT ROUTES

Privacy Help Through Local Channels

Policy questions move faster when you contact us from the same phone number on your account. Our live chat is staffed 09:00-23:00 WIB, WhatsApp handles follow-up screenshots, and email is used for longer privacy requests such as export or deletion. For your safety, we ask for a recent QRIS or wallet reference only to match the account, not to collect extra payment data.

Team online

Live Chat

Use live chat between 09:00 and 23:00 WIB for quick Privacy Policy questions, cookie concerns, or device alerts. We will ask you to confirm your account phone before discussing any personal record.

WhatsApp

Send WhatsApp screenshots when a DANA, OVO, GoPay, or QRIS reference needs matching to your account. Please cover unrelated balances or contacts before sending images to our privacy team.

Email

Use email for correction, export, or deletion requests because it creates a clear written trail. Include your registered phone, username, request type, and one recent payment reference for account matching.

DATA CARE

Inside lego138 Account Privacy Controls

Privacy handling is part of the account routine, not a separate promise on paper. We limit staff access by task, keep sign-in logs for security checks, and separate payment references from chat…

Data We Collect

We collect account phone, username, password status, device session, IP region, wallet reference, and support notes. Game activity such as Sic Bo or Pyramid Bonanza sessions is tied to account safety and dispute checks.

Payment Record Use

DANA, OVO, GoPay, and QRIS references are used to match deposits and withdrawals to your wallet. We keep the reference, time, amount, and account link so support can trace a payment issue.

Cookies and Devices

Cookies help us remember session status, language choice, and basic security signals. If a new phone or tablet appears, we may ask for a fresh sign-in check before showing wallet or profile details.

Account Changes

You can update basic details from Account > Profile and check active sessions under Account > Security. For phone number changes, support confirms the old number and a recent QRIS or wallet reference.

Retention Rules

We keep privacy records only for account safety, payment tracing, dispute handling, and lawful requests. When a record is no longer needed, we remove it from active tools or narrow staff access.

Request Handling

Privacy requests are handled by trained support staff, not public lobby agents. We log the request date, account match step, action taken, and reply channel so your case has a clear record.

Questions About Your Policy Rights

The FAQ below focuses only on Privacy Policy questions we receive before and after account creation. Each answer explains what we collect, why we keep it, and which support path to use. If your question involves local access, we will remind you that availability depends on local law where you are. Keep your registered phone ready because it helps us match your request without exposing extra data.

We collect the phone number, username, password status, device session, IP region, and wallet reference you provide. These details help us create the account, protect access, and match DANA, OVO, GoPay, or QRIS records.

No. We do not sell your account profile, wallet references, chat history, or device logs. We use them to run account checks, payment matching, security monitoring, support handling, and lawful request responses.

Contact live chat or email from your registered phone number and state what needs correction. For phone or wallet changes, we may ask for one recent DANA, OVO, GoPay, or QRIS reference.

Yes, you can request an export through email. Include your username, registered phone, and request type. We verify the account first, then send eligible account, payment, and support records through a safer reply channel.

Cookies help us keep your session active, remember language choice, and detect unusual sign-in patterns. You can clear browser cookies, but the site may ask you to sign in again and repeat device checks.

We keep payment references for account safety, payment tracing, dispute handling, and lawful requests. When those needs end, we remove records from active tools or limit access to staff with a clear task.

This policy explains data handling, not entry approval. Access and eligibility depend on local law and are available only where local law permits, so we may ask for account checks before showing wallet details.