Reference

Privacy Policy for Your Account

Our Privacy Policy explains how liganusa handles the account details connected with Live Roulette, Medusa, Aviator and your wallet activity.

Account recordsWallet activityCookie choicesAccess requests
liganusa Privacy Policy for Your Account
CONTACT DATA SUPPORT

Ask About Your Data Path

A clear contact route matters when a wallet record or account detail looks unfamiliar. We keep policy questions separate from game requests so your message can be directed to the right account…

Account access If phone verification blocks your account, contact support through the channel shown in your liganusa account area. Include the affected login detail, but never send your password or full wallet security code.
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, share the transaction reference and date through our support route. We use those details to locate the relevant record without asking for unnecessary personal data.
Policy requests To ask for a copy, correction or removal of personal data, send the request through the policy contact path in your account area. We may ask for account details to confirm that the request comes from you.
HOW WE HANDLE IT

Switch Through Each Privacy Detail

Privacy choices are easier to use when each part of the account journey is explained in plain terms.

Data collection

We collect details you enter during account creation, such as contact information and verification data, plus records created when you sign in, contact support or request a wallet action. We explain the purpose before the data is used where a notice is required.

Device signals

When you move from a mobile login to the lobby, device and connection signals can help us recognise unusual access and protect your account. These signals support security checks; they do not replace the phone verification step needed for account access.

Cookies

Cookies can keep your session working, remember selected settings and show whether a page loads correctly. Your browser controls can remove or restrict them, although changing cookie settings may affect sign-in continuity or parts of the policy page.

Account security

We use account checks around sign-in, phone verification and wallet-related actions to reduce unauthorised access. Keep your password private, review unfamiliar login activity and contact support promptly if a DANA or QRIS record does not match your action.

Data retention

We retain account, support and transaction records for as long as needed for the stated service, security, dispute and legal purposes. The period can differ by record type, and the Privacy Policy explains when information is removed or made no longer linked to you.

Your requests

You can ask us to access, correct or delete eligible personal data, or question how it is used. Send a specific request through the policy contact path; we confirm your identity first and explain any legal reason a request cannot be completed.

Browse Answers About Privacy Policy

These Privacy Policy answers focus on the account and wallet questions you are most likely to ask before opening access. If your situation is not covered, use the policy contact path and include only the details needed to locate your account.

The liganusa Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and transaction references. It explains why we use each category, how we protect it, how long records may remain and how you can request access or correction.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account actions. We use those records to identify the requested wallet step, answer status questions and protect the account from unusual activity.

Phone verification helps connect account access to the contact detail you supplied and provides an account-security check before you enter the lobby. The Privacy Policy explains how verification data is handled. If access is discussed, it depends on local law and the applicable account conditions.

You can ask for a copy of eligible personal data through the policy contact path shown in your account area. Tell us which account detail or activity you need. We confirm your identity before responding and explain the format, timing or legal limits that apply.

Send a correction request through our policy support route and identify the detail that needs changing, such as a contact field or verification record. We may ask for confirmation before editing it. The Privacy Policy explains how we assess the request and notify you.

You can submit a removal request through the contact path in your account area. We review the request against service, security, dispute and legal record needs, then explain what can be removed and what must remain. Eligibility depends on local law.

On mobile, cookies can support sign-in continuity, remember page settings and help us check whether the lobby and policy page function correctly. Your browser lets you restrict or clear them. If a setting interrupts access, support can explain the account step involved.