Reference

liga123 Privacy Policy For Your Account

The liga123 Privacy Policy explains how we handle your account details, phone verification, device sessions, and payment references for DANA and QRIS.

Clear data purposesWallet reference handlingAccount access choicesCookie controls
liga123 liga123 Privacy Policy For Your Account
POLICY HELP ROUTES

Get Help With Privacy Policy Requests

A clear support route matters when you want to ask about the Privacy Policy, correct an account detail, or understand a payment record. We direct privacy questions through the account support path, close to the cashier area, so you can include the relevant account step without posting sensitive credentials in a public message. Keep your receipt reference ready when your question concerns DANA, OVO, GoPay, or QRIS.

Team online

Policy questions

Use the support path linked to your account area and state which Privacy Policy section needs explanation. We can respond more accurately when you include your registered contact detail, without sending a password.

Data corrections

If your phone number or account detail is inaccurate, ask us to check the record through the account support route. We may request an account step that confirms the request belongs to you.

Payment records

For a DANA, OVO, GoPay, or QRIS reference, share the receipt code rather than wallet credentials. We use that reference to locate the status connected with your account and explain the record.

DATA CONTROL DETAILS

Cookies, Devices And Account Records

We apply the Privacy Policy to the practical moments you encounter: opening an account, confirming a phone number, signing in from a mobile browser, checking a wallet status, and asking for a…

Account details

We use the contact and verification details you submit to create your account, match sign-in activity, and send replies about a privacy request. Keep them current so an access check reaches you.

Mobile browser signals

When you sign in on a phone, we may record device and session signals used to recognise unusual access. These signals help protect the account without requiring us to read your private device files.

Cookies

Cookies can retain session choices and help the account area load correctly. Your browser settings let you remove or restrict them, although some sign-in steps may then need to be repeated.

Payment references

We retain payment references and status details for DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. These records help us answer receipt questions without requesting your wallet password.

Retention checks

We keep account and transaction records only for the period needed for account operations, dispute handling, security checks, or legal duties. Retention can vary by record type and applicable local requirements.

Change requests

To request access, correction, or removal where available, contact support from your account path and identify the record involved. We may verify your phone or account details before making a change.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account and payment questions we hear most often in Indonesia. They explain what you can ask us to do, which details help us locate a record, and why an identity check may appear before we disclose or change account data. Access remains subject to local law.

It covers account details, phone verification, login and device signals, cookies, lobby activity references, payment status records, retention, and the process for requesting access or corrections.

Yes. It covers references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer, and virtual account activity. We use them to match records and answer payment questions.

You can contact support through your account path and identify the incorrect phone number or account detail. We may verify your account before changing the record or confirming the result.

Cookies can keep your session and account choices working between pages. You can restrict or delete them in your browser, but some account access steps may need to be completed again.

Device and session signals help us identify unusual sign-in activity and protect your account. They are used for access checks, not to read private files stored on your phone or computer.

Retention depends on the record and the reason it is needed, such as account operation, receipt questions, security checks, disputes, or legal duties. We remove records when the applicable period ends.

Yes, where local law permits. Send the request through the account support path, name the data category involved, and complete any account check needed to protect your information.