Reference

ligawon Privacy Policy for Your Account

Our Privacy Policy explains how ligawon handles your account details, device signals, cookies and wallet records when you use our site.

Account detailsWallet recordsDevice controlsPolicy requests
Explore the lobby Read FAQ
ligawon ligawon Privacy Policy for Your Account
REQUEST HELP

Browse Support Paths for Privacy Requests

A clear request path helps you correct account details or ask how your data is handled. Start from the support link in your signed-in account area and include the email or phone number attached to your profile. If wallet status is part of the question, name the relevant DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. We use those details to locate the right record without asking you to send a password or full wallet credentials.

Team online

Account support

Use the support link after login to ask about a privacy request, account record or phone verification detail. We may ask you to confirm the account contact before discussing personal data, so the request stays connected to the correct profile.

Wallet reference

For a DANA, OVO, GoPay or QRIS question, provide the transaction reference and approximate date shown in your payment record. For bank transfer or virtual account matters, the reference helps us separate your request from another account.

Access concern

If you cannot reach the policy page or account area, tell us the device type, browser path and error message through the available support route. Do not send your password, wallet PIN or one-time verification code with the request.

DATA HANDLING

Explore How We Handle Your Records

We keep privacy work close to the account flow rather than treating it as a separate promise. Our controls cover sign-in activity, phone verification, device behaviour, cookie choices, wallet references and requests…

Account details

We use the contact details you provide to create your profile, confirm phone access and respond to account requests. Check your account details before sending a correction request, because an accurate contact route helps us verify that the request comes from you.

Device signals

Login time, browser type, operating system and related security signals can help us identify unusual access. We use these details to protect your account and investigate a sign-in concern, not to request your device password or private wallet code.

Cookies

Cookies can keep a session working, remember selected settings and help us understand whether a page loads correctly. You can manage cookie choices through your browser controls, although changing them may affect login continuity or the way policy pages display.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create a reference, amount, status and time record. We use this limited payment context to match account actions and resolve status questions without storing a wallet PIN.

Retention period

We retain each category only for the period connected to its purpose, account security, dispute handling or a legal duty. When a record is no longer needed, we remove it or separate it from direct account identification where our process allows.

Change requests

Ask to access, correct or delete personal details through the signed-in support route. Include the request type and account contact, but leave out passwords and one-time codes. We may verify your identity before making a change or sharing a record.

Ask About ligawon Privacy Policy

These Privacy Policy answers focus on the account and wallet questions you may search before joining. They explain what we collect, how to request a change and what to do when device or payment details appear in a support case. Where a question concerns eligibility, access depends on local law.

The ligawon Privacy Policy covers account details, phone verification, login and device signals, cookies, payment references, support requests and retention. It also explains how you can ask for access, correction or deletion of personal details connected with your account.

We do not ask you to send a wallet PIN through support. Our records can include a payment reference, status, amount and time for DANA, OVO, GoPay or QRIS activity so we can match an account action and investigate a status question.

Use the support link in your signed-in account area and state that you want an account data request. Include the email or phone attached to your profile. We may confirm your identity before describing or sending personal details linked to that account.

Yes, you can ask us to correct inaccurate account details through the same support route. Tell us which field needs changing and provide the correct value. We may request account-contact confirmation before updating the record or discussing its contents.

Device signals such as browser type, operating system and login time help us check unusual access. Cookies can maintain a session and remember settings. You can adjust cookie controls in your browser, though login continuity or page display may change.

Retention depends on why a record exists. We may keep account, payment-reference, security or support records for account protection, dispute handling, accounting or a legal duty. When the purpose ends, we remove the record or separate it from direct identification where possible.

Start with the support link inside your account and describe the access, correction or deletion request. If you cannot sign in, provide the available account contact and the device path that failed. Never include your password, wallet PIN or one-time code.

Related Pages

ligawon Indonesia Thunder Zeus Slots About Us Esports Dota 2 FAQ