Reference

ligatoto Privacy Policy For Your Account

The ligatoto Privacy Policy explains how we handle the details connected with your account, device, wallet status and support requests in Indonesia.

Account clarityWallet data careCookie choicesRequest a change
ligatoto ligatoto Privacy Policy For Your Account
CONTACT THE DESK

Three Ways To Ask About Privacy

A clear contact route helps you control the data linked to your ligatoto account.

Account privacy request Ask us to locate the personal data connected with your account, explain its purpose…
Wallet record question For a DANA, OVO, GoPay or QRIS reference, provide the account identifier and the…
Security access concern Tell us when a login, phone verification attempt or device session looks unfamiliar.
DATA HANDLING

Six Privacy Controls We Explain Clearly

Privacy depends on practical controls rather than broad promises. We separate account details from payment references where the workflow allows, limit internal access to the records needed for…

Account collection

We collect details needed to create and maintain your account, including contact data and the phone verification result.

Payment references

DANA, OVO, GoPay and QRIS may return a reference, amount and status needed to reconcile an account request.

Cookies and storage

Cookies can keep a signed-in session, remember a device preference, or support security checks as you move from the account…

Account protection

Phone verification, session records and device signals help us investigate an unfamiliar login.

Retention reasons

We retain records only while they support account operation, payment reconciliation, security investigations, legal duties or an unresolved dispute.

Your requests

You can ask for access, correction, restriction or deletion of eligible personal data through support.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the searches we hear most often before an account is opened or a support request is sent. We keep the wording tied to real account steps, device behaviour and Indonesian wallet references, so you can decide what to share and how to ask for a change. If your situation is unusual, contact us with the account route and the specific record you want us to check.

The ligatoto Privacy Policy covers account details, phone verification, sign-in records, device and browser signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain, and how you can request access or correction for eligible data.

Phone verification helps connect the account to the person completing the account step and helps us respond to an unfamiliar login. We record the verification result and related security event, not a wallet PIN. Account access depends on local law and the applicable security checks.

Yes. The Privacy Policy covers the DANA, OVO, GoPay or QRIS reference and status needed to match a wallet request to your account. Bank transfer and virtual account references can also be handled for reconciliation. We do not require your wallet password for this purpose.

Cookies may keep your session active, remember a device preference or help identify an unusual sign-in while you move between account pages and the lobby. You can clear or restrict them in your browser. After clearing storage, you may need to complete phone verification again.

Contact our account support route and state whether you want access, correction, restriction or deletion of eligible data. Give the phone or email attached to your account and describe the record, such as a QRIS receipt or device event. We verify ownership before responding.

Retention depends on why the record exists. Account operation, payment reconciliation, security checks, legal duties and unresolved disputes can require different periods. When a reason ends, we delete, anonymise or restrict the record where applicable. We can explain the reason for a specific retained record.

Yes. Tell us the approximate date, device type and account contact route, without sending a password. We can check the relevant session or security event and explain the handling under the Privacy Policy. Any access decision remains where local law permits and after account ownership checks.