Reference

Privacy Policy For Your ligalotus Account

Our ligalotus Privacy Policy explains what account, device and wallet details we handle when you use the service, why each detail is needed, and how you can ask…

Account dataWallet recordsCookie choicesAccess requests
Browse The Lobby Read FAQ
ligalotus Privacy Policy For Your ligalotus Account
HELP WITH REQUESTS

Get Clear Answers About Stored Data

A direct support route helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record. Start from the support area inside your account and include the phone number or reference connected with your request, but never send a password or full payment credential. If you are in Medan, Semarang or elsewhere in Indonesia, the same policy request path applies where local law permits.

Team online

Account support form

Use the support form reached from your account menu to ask which personal details are linked to your phone verification. We can request a matching account detail before discussing records, helping prevent disclosure to the wrong person.

Wallet status question

For a DANA, OVO, GoPay or QRIS record, include the visible reference and date from your account history. Our team can explain how that record connects to account activity without asking you to share your wallet password.

Policy change request

If a name, phone detail or contact preference needs correction, send the request through account support. We may ask for a verification step before changing data, and we will explain any legal reason a record must remain.

HANDLING YOUR DETAILS

How ligalotus Handles Privacy Requests

We keep this policy practical by connecting each data use to an account action you can recognise, such as phone verification, wallet status or a support request.

Account data

We may handle your phone detail, account identifiers and verification records to create and protect access. These details also help us match a support request to the correct account when you ask about Privacy Policy rights.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can appear in account records when you use those routes. We use the reference and status details to trace activity, not to request your wallet password.

Cookies and browser use

Our web pages may use cookies or similar browser storage for account continuity, security checks and page settings. You can inspect or clear these controls through your mobile or desktop browser, though some account steps may then need repeating.

Account security

Phone verification and account checks help us confirm that a Privacy Policy request comes from the right account. Keep your login details private, sign out on shared devices and contact support if an unfamiliar access event appears.

Retention choices

We retain account, support and wallet records for the operational, security or legal period connected to their purpose. When that period ends, we remove or anonymise records where the applicable rule allows, while explaining any required exception.

Your requests

You can ask for access, correction, deletion or clarification through the support route in your account. We may verify your identity first, then explain the result, timing and any restriction that depends on local law.

Privacy Policy Answers Before Account Access

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. Each answer follows the same account path used on mobile and desktop, so you can find the relevant setting or support route without leaving the service. Where a right or access step depends on local law, we will state that clearly.

The Privacy Policy covers account and phone verification details, browser records, cookies, support messages and wallet references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains security, retention and requests for access or correction.

Phone verification helps us create a distinct account, protect account access and match a support request to the correct person. We may ask you to confirm an account detail before discussing personal records, and access depends on local law.

Open the account menu on your mobile browser or desktop, choose the support route and ask for a data access request. Include the account phone detail or visible reference, but do not send passwords. We may verify your identity first.

Yes. Send a correction request through account support and identify the detail that appears wrong, such as a phone number or contact preference. We will check the account before making a change and explain any record that must remain.

We use payment references and status details to connect a wallet event with the correct account, answer receipt questions and investigate a stalled status. We do not need your wallet password for this process, and bank records follow the same purpose.

Use the cookie and site-data controls in your mobile or desktop browser to inspect, block or clear stored browser data. Clearing cookies can sign you out or require phone verification again, because account continuity and security checks may be affected.

Use the support route inside your account and state whether you need access, correction, deletion or clarification. Add the relevant account reference without sharing passwords. Our team will explain the next verification step and any limit that depends on local law.

Related Pages

ligalotus Indonesia About Us Boxing Betting FAQ Lightning Roulette