Reference

liga20000 Privacy Policy Explained

liga20000 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS for wallet activity.

Account dataWallet recordsCookie choicesAccess requests
liga20000 liga20000 Privacy Policy Explained
HELP WITH PRIVACY

Where To Ask About Your Data

A clear contact route matters when you want to understand a record, correct an account detail or ask why a security check appears. Start from the support path connected to your account and include the email or phone detail used during verification. We can then locate the relevant sign-in, wallet or cookie question without asking you to send unnecessary account material.

Team online

Account access

When a phone verification step blocks access, use the account support path and identify the contact detail attached to your account. We use that reference to discuss access records without requesting your password or a full payment credential.

Wallet record

For a DANA, OVO, GoPay or QRIS record, send the payment reference shown in your account rather than a wallet password. We can check the status connected to your account and explain what information the Privacy Policy permits us to retain.

Policy request

Questions about deletion, correction or cookie choices can follow the same support route. Tell us which request you are making and which account contact was verified, so we can confirm ownership before discussing personal data.

DATA HANDLING

What We Do With Account Details

Your account should give you a practical way to understand data handling before you use the lobby.

Account creation

When you open an account, we use the submitted contact details to create your profile and send account-related messages. A clear phone verification step helps us connect the person requesting access with the account record before the lobby becomes available.

Device signals

We may record browser type, device identifiers, approximate technical location and sign-in time to detect unusual access. These signals help us separate a normal phone return from a session that needs an additional account check.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can leave a reference connected to your account. We use that reference to reconcile a status or receipt, while avoiding requests for your wallet PIN or banking password.

Cookies

Cookies can remember a session, support account security and retain a choice you make on the site. You can manage cookies through your browser settings, although removing essential cookies may require you to sign in again.

Retention period

We retain personal data for the time needed to operate the account, answer a support request, resolve a payment record or meet a legal duty. When a purpose ends, we review whether the record can be deleted, anonymised or restricted.

Changes and contact

You can ask us to correct an inaccurate detail, explain a processing purpose or change a cookie choice through the account support route. We may verify ownership first, then record the request and respond using the contact detail on file.

Privacy Policy Answers For liga20000

These Privacy Policy answers address the account and access questions that matter before you continue. We keep each response tied to a real action, such as phone verification, a QRIS receipt, a cookie setting or a request to change personal data. Access remains subject to local law.

The liga20000 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support requests and payment references. It explains why we use each category, how we protect access to it and when we may retain or remove it where local law permits.

Phone verification helps us connect an account request with the contact detail supplied during registration. We may use the verified status during a sign-in or support request, especially when a device changes. We do not need your phone password to complete this account check.

Yes. The Privacy Policy covers payment references created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account records. We use those references to match a status or receipt with your account, not to request your wallet PIN.

We may collect technical details such as browser type, device signals, sign-in time and approximate network location. This helps us identify unusual access and protect your account. The data is handled for security, operation and support purposes rather than as a general profile of your activity.

Use the support route connected to your account and state whether you want a correction, deletion, restriction or explanation of a data use. Include the verified account contact, but never send a password or wallet PIN. We may need to confirm ownership before processing the request.

Cookies can keep a session active, support account security and remember a choice made on the site. You can adjust them in your browser. Removing essential cookies may sign you out or make a later phone verification step necessary when you return.

Send the request through the account support path and identify the subject clearly, such as a QRIS receipt, device record, cookie choice or account detail. We use the verified contact on file to discuss the request and provide a response where local law permits.