Reference

lx188 Privacy Policy for Your Account

lx188 Privacy Policy explains how we handle your account details, wallet records and device access when you use our Indonesia-facing lobby.

Clear data purposesWallet status recordsPhone verificationSupport request path
lx188 lx188 Privacy Policy for Your Account
CONTACT ROUTES

Open a Privacy Request Through Support

A clear contact route matters when your account record or wallet reference needs attention. We keep privacy questions close to the account-help and cashier-status paths, so you can explain the issue without sending sensitive details through an unrelated channel. Use the available support contact shown in your account area, identify the request type, and include only the minimum information needed for us to locate the record.

Team online

Account access

If you cannot sign in or complete phone verification, tell our support team that your request concerns Privacy Policy access. We may ask for account identifiers already linked to your profile, but never ask you to disclose a full password.

Wallet record

For DANA, OVO, GoPay or QRIS questions, use the cashier-status support path and state whether you need a correction, access copy or explanation. A transaction reference helps us locate the event without requiring unrelated account material.

Data request

To request correction, deletion or a copy of personal records, contact support from the account connected to the request where possible. We may verify ownership before changing or disclosing data, protecting your profile from an outside request.

DATA PRACTICES

Switch Through lx188 Privacy Controls

Privacy controls work best when they match the way you actually use the service. We separate account access records from the purpose that created them, use device signals to help identify unusual…

Account data

We may handle your name or account label, contact details, phone verification result and sign-in history to operate your profile. The Privacy Policy does not give us a reason to collect unrelated identity details, and you can ask support to confirm the categories linked to your account.

Cookies and devices

Browser cookies and device signals can remember a session, support fraud checks and show the right account state after you move from login to the lobby. If you clear browser data, you may need to verify access again; this does not erase records already required for account or payment handling.

Wallet handling

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can show that a cashier event belongs to your account. We use that link for status checks, reconciliation and support, not as a reason to inspect unrelated wallet activity outside our service.

Account security

Phone verification and sign-in checks help us distinguish your account from an unapproved access attempt. Keep your password and verification codes private, and report a suspicious session through account support so we can review the access record and guide the next account step.

Retention approach

We keep personal records only for the period needed for account operation, transaction reconciliation, security checks, dispute handling and applicable legal duties. When a record is no longer needed for those purposes, our process is to remove it or separate it from direct account identification where practical.

Changes and requests

You can ask for a copy, correction, deletion or explanation of relevant personal data through the support route linked to your account. We may limit a request when keeping the record is required for security, payment reconciliation or legal duties, and we will explain the next available step.

Browse lx188 Privacy Policy Answers

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the records created by login, phone verification, mobile browsing and local wallet activity, with a direct path to support when your question needs an account-specific answer. Access to the service remains where local law permits.

The lx188 Privacy Policy covers personal data created through account opening, phone verification, sign-in, mobile browser use, lobby activity, cashier events and support messages. It explains our purposes, security steps, retention approach and request process for correction, access, deletion or a policy explanation.

We use the phone verification result to help confirm that the person entering the account can complete the required account step. It also supports sign-in protection and account recovery checks. We do not ask you to place a password or verification code inside a support message.

Yes. The Privacy Policy covers payment references and status records connected to DANA, QRIS, OVO, GoPay, bank transfer and virtual account events. We use those records to match cashier activity, resolve a status question and maintain the account history needed for reconciliation.

When you use the mobile browser, we may handle technical signals such as browser session details, device type and sign-in events. These help keep the login-to-lobby path working and identify unusual access. Clearing cookies can end the session, but it does not remove required account records.

Contact support through the account-help route and state whether you want access, correction, deletion or an explanation. Use the account connected to the request where possible. We may verify ownership before responding, then explain what can be changed and whether any record must remain.

We retain records for the time needed to run your account, reconcile DANA or other cashier events, investigate security issues, handle disputes and meet applicable legal duties. The period can differ by record type. Ask support which category applies to your request and what action is available.

You can send a deletion request through the account support path. We assess the request against security, transaction reconciliation and legal duties before removing data. Some records may need to remain for a defined purpose, and we will explain that outcome rather than treating every request the same way.