Reference

Privacy Policy for Your liganusa88 Account

Our Privacy Policy explains how we collect, use and protect the details connected with your liganusa88 account.

Account dataWallet referencesCookie choicesAccess requests
liganusa88 Privacy Policy for Your liganusa88 Account
CONTACT PATH

Get Privacy Help Before Account Access

Our support path is designed to keep a privacy question separate from a general lobby request. Tell us whether you need a copy of account data, a correction, a cookie explanation or help with an unfamiliar device entry. Include the phone number linked to your account and the relevant payment reference, but never send a wallet password or one-time verification code. We use those details to locate the right record and may ask for an account step to confirm that the request comes from you.

Team online

Account privacy request

Use our account support contact path when you want to ask what personal details we hold or request a copy. Include your registered phone number and the subject Privacy Policy so we can route the request without exposing account details in a public message.

Wallet reference check

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the date, amount reference and account phone number through support. We can check the account record while keeping your wallet password, verification code and full payment credentials out of the request.

Device access concern

When your account opens differently on mobile or desktop, contact us with the device path and approximate access time. We can explain the security record, help you secure the account and tell you which Privacy Policy request applies to the event.

HANDLING DETAILS

What We Do With Your Account Data

We keep the Privacy Policy practical: each data category has a reason connected with account access, security, payment matching or support.

Account identity

We use your registered phone number and verification status to connect an access request with the correct account. Before discussing private account details, we may ask you to complete an account step so a third party cannot receive your records by mistake.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a payment event with your account. We use the reference and status for checking, support and reconciliation, not as a substitute for your wallet credentials.

Cookies and storage

Cookies and similar storage can record technical preferences, session conditions and device behaviour needed for the account path. Our Privacy Policy explains their purpose, and you can ask support which cookie category relates to a particular access event.

Security controls

Phone verification, session checks and device signals help us identify unusual account access. Keep your password and one-time code private, and contact support promptly if the mobile path or desktop session shows activity you do not recognise.

Retention approach

We keep account, support and payment-reference records for the period needed to provide the requested service, investigate security events or meet requirements that depend on local law. We can explain the category and purpose when you send a retention question.

Changes and questions

You can ask us to correct inaccurate account details, explain a data use or clarify a Privacy Policy section. Send the request through the account support contact path, identify the relevant record and complete any verification step we reasonably need.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and device questions we expect from Indonesian customers before they open an account. They also explain what to include when you contact us about wallet references, cookies, corrections or access. Where a request depends on regional rules, our response follows the requirement that depends on local law.

The Privacy Policy covers account details, phone verification, device activity, cookies, support records and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains why we use each category and how you can ask about, correct or access your data.

Our Privacy Policy does not treat your DANA, OVO, GoPay or QRIS wallet password as an account record we need for payment matching. We use payment references and status details instead. Never send a wallet password or one-time verification code in a support request.

Send a request through our account support contact path with the phone number registered to your account and the words Privacy Policy. State whether you want a copy, correction or explanation. We may ask you to complete phone verification before sharing account-linked details.

Device and session details help us understand how an account was accessed and investigate activity that does not match your usual path. The same record can explain why mobile and desktop sessions differ. Contact support with the device type and approximate access time.

Cookies can retain technical session choices and help the website recognise the account path on your device. They do not replace phone verification or give support permission to disclose private records. Ask us which cookie purpose applies if you want a clearer explanation.

Yes. The Privacy Policy lets you ask us to correct an inaccurate account detail or clarify a record. Provide the registered phone number, identify the field that needs attention and complete the requested account check. Handling follows the requirement that depends on local law.

We retain account, device, support and payment-reference records only for the period connected with access, security, reconciliation or a requirement that depends on local law. The period can differ by record type. Contact us with the category you want explained, and we will describe its purpose.