Reference

liga500 Privacy Policy for Your Account

liga500 Privacy Policy explains how we collect, use and protect the details needed for your account, phone verification and wallet activity, including DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

What We Collect Before Wallet Access

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

Our Privacy Policy starts with the account details you provide when you create an account and complete phone verification. We may handle your contact details, verification results, login records, device information, approximate technical location and activity connected with account protection. When you use DANA, OVO, GoPay

1
or QRIS, we retain the payment reference and status needed to match an account action, while the payment provider remains responsible for its own handling. Bank transfer and virtual account records can also be linked to your account for reconciliation and support. We use this data
2
to provide requested access, check unusual login or wallet activity, respond to account questions and meet obligations that depend on local law. Where local law permits, you can ask us to explain, correct or remove eligible details through the contact path below.

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

CONTACT YOUR WAY

Get Privacy Help Beside Account Support

A clear contact route matters when you want to ask about your Privacy Policy rights or a record connected with your account.

Account support path Use the support route attached to your account when you need a Privacy Policy answer. Include your account contact and the subject of your request, such as a DANA receipt, QRIS status or phone verification record, so we can direct it to the right handling step.

Cashier-linked questions If your request concerns a wallet or bank transfer record, mention the payment rail and reference shown in your account. We can use that detail to locate the relevant DANA, OVO, GoPay, QRIS, virtual account or bank transfer entry without requesting your wallet PIN.

Login and device help When a privacy question follows a login problem, tell us the device path you used, such as a mobile browser or desktop browser, and the time of the event. This helps us separate a security check from a request to change, access or delete personal data.

HOW WE HANDLE DATA

Privacy Controls You Can Ask About

We handle Privacy Policy requests through practical account steps rather than vague promises. Your account activity, cookie settings and payment references serve different purposes, so we assess each request against the record…

Account data use

We use your account details to create access, complete phone verification, maintain login security and respond to requests you make. We do not need your wallet password for a standard Privacy Policy enquiry, and we ask for only the account context needed to locate the record.

Cookies and browser signals

Cookies and similar browser signals can help us remember a session, protect login activity and understand whether a page loads correctly on mobile or desktop. You can ask what a cookie does and request a change where that choice is available under local rules.

Mobile device records

When you open the lobby through a mobile browser, technical details such as device type, browser version and security events may be recorded. These details help us investigate an unusual login or a failed account step without treating the device itself as your identity.

Payment references

A DANA, OVO, GoPay or QRIS reference can be retained to match a wallet action with the correct account. Bank transfer and virtual account records may serve the same reconciliation purpose. We handle the reference, while the relevant payment provider handles its own data.

Retention and deletion

We keep records only for the period needed for account operation, security checks, support history or legal duties. If you ask for deletion, we assess each category separately and explain when a payment, verification or access record must remain because local law requires it.

Changes to your details

You can ask us to correct an outdated contact detail or clarify a record connected with your account. Send the request through account support and identify the affected field. We may confirm your phone or account ownership before applying a change or sharing the result.

Answers About liga500 Privacy Policy

These Privacy Policy answers cover the questions we expect you to ask before opening an account or using a local wallet. Each answer points back to a practical account step, and you can contact support when your situation needs a record-specific response. Eligibility and access depend on local law.

The liga500 Privacy Policy covers account details, phone verification, login and device records, cookie use, payment references and support requests. It also explains how we assess correction, access and deletion requests, including cases where a record must remain because local law applies.

Phone verification helps us confirm account ownership and protect login access. It may also be used when you ask to change personal details or access a record. We use the verification result for that account purpose and do not ask for your DANA, OVO or GoPay PIN.

Yes. Our Privacy Policy explains how we handle the DANA or QRIS reference and status needed to match an account action. OVO, GoPay, bank transfer and virtual account records may be handled in the same way, while each provider controls its own data practices.

You can request access to eligible account data through the account support path. Tell us the contact detail linked to your login and the record you want, such as a device event or payment reference. We may confirm ownership first, and the outcome depends on local law.

Send a correction request through account support and identify the field that is wrong, such as a phone number or contact detail. Include the accurate replacement value, but do not send a wallet PIN. We may verify your account before changing the record.

Retention depends on the record and its purpose. Account, security, support and payment references may remain while needed for access, reconciliation or legal duties. If you request deletion, we review each category and explain any reason a particular record cannot yet be removed.

Use the account support route and describe the browser or device path involved, such as mobile browser access, plus the cookie or technical record you want clarified. We can explain its purpose and assess an available change or access request where local law permits.

liga500 Privacy Policy for Your Account

Get Privacy Help Beside Account Support

Privacy Controls You Can Ask About

Account data use

Cookies and browser signals

Mobile device records

Payment references

Retention and deletion

Changes to your details

Answers About liga500 Privacy Policy

01 What does the liga500 Privacy Policy cover?

02 Why does liga500 need phone verification?

03 Does the Privacy Policy cover DANA and QRIS payments?

04 Can I request a copy of my liga500 account data?

05 How do I ask liga500 to correct my personal data?

06 How long does liga500 keep privacy and payment records?

07 How can I contact liga500 about cookies or device data?

Related Pages