Reference

Open the liga1 Privacy Policy

The liga1 Privacy Policy explains how we handle the details connected with your account, device, login activity and wallet checks.

Account detailsDevice activityWallet checksPolicy requests
Explore Our Lobby Read FAQ
liga1 Open the liga1 Privacy Policy
DATA HELP PATH

Browse your Privacy Policy support routes

A clear support route helps you ask what data we hold, why a record appears or how to correct an account detail.

Account request Use the account help path for a copy, correction or clarification request about your profile, phone verification record or login activity. We may ask you to confirm the account detail before discussing it, so we do not disclose personal data to the wrong person.
Wallet record When your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, send the payment reference and approximate time. We use those details to locate the relevant account record without asking you to share a wallet password or security code.
Policy clarification Ask us to explain a Privacy Policy passage when the wording does not match your account experience. Tell us whether the question concerns cookies, device records, retention, access or deletion, and we will route the request to the appropriate policy contact.
HANDLING DETAILS

Explore how we protect policy choices

Privacy choices work best when the account steps are visible and specific. We separate profile details from payment references, use phone verification before account access and check device signals when a login…

Account collection

We collect details needed to create and maintain your account, including contact information and the phone verification result. Providing accurate details helps us match a policy request to the correct account and reduces confusion when you return from a mobile device.

Device signals

A browser or phone may send session details, device type, language setting and security signals when you sign in. We use these records to keep access functioning, identify unusual login patterns and investigate a request linked to a particular device path.

Cookies

Cookies and related storage can keep a login session active, remember a setting and support security checks. You can adjust cookie controls in your browser, but limiting them may affect account access or require you to repeat a verification step.

Payment references

For DANA, OVO, GoPay and QRIS, we may receive status or reference details needed to match an account action. Bank transfer and virtual account records can serve the same purpose, while wallet passwords and security codes should remain private.

Retention choices

We keep records for as long as needed for the stated account, security or support purpose, then assess whether removal is appropriate. Some records may remain longer for dispute handling or where local law permits or requires continued storage.

Security contact

If you suspect that your account details or device session were accessed by someone else, contact support through the account help path and change your password. Include the affected device and approximate login time, but never send a password or wallet security code.

Browse Privacy Policy answers for liga1

These Privacy Policy answers focus on the questions you may have before opening an account or asking us to change a record. They explain the practical steps for account access, device data, cookies, payment references and policy requests. If your situation is not covered, use the support route and include the account detail that lets us locate the correct record.

It covers account details, phone verification, login and device records, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and how to request access or correction.

Phone verification helps us confirm that an account request belongs to you before access is provided. It can also support login checks when a device or session looks unusual. We use the result for account security and policy handling, not as a substitute for your password.

Yes. The policy covers status and reference details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account actions. These references help match a transaction step to your account. Do not send wallet passwords, one-time codes or other private security credentials.

Use the account help path and state that you are making a Privacy Policy access request. Include the contact detail linked to your account and any relevant date or device. We may ask for account confirmation before releasing personal data to protect it from an unverified requester.

Yes. Send the incorrect detail, the replacement wording and the account contact used for verification. We may request an account check before changing it. If the detail appears in a payment reference supplied by DANA, OVO, GoPay or QRIS, the payment service may also need to be contacted.

Retention depends on why the record was collected. We assess account, device, cookie and support records when the relevant purpose ends, while some details may remain for security, dispute handling or where local law permits or requires continued storage.

You can ask us which cookie or account records relate to your request and whether removal is available. Browser cookie controls can limit storage on your device. Some account or security records may need to remain where local law permits or requires it, and access depends on local law.

Related Pages

liga1 Indonesia liga1 Casino Premier League Match Bet Live Blackjack Prestige Account information