Reference

liga788 Privacy Policy: Your Data, Clearly Handled

Your account details, wallet records and device choices have a clear place in our Privacy Policy.

Account dataWallet recordsCookie choicesContact rights
liga788 liga788 Privacy Policy: Your Data, Clearly Handled
CONTACT PATHS

Get Privacy Help Near Your Account

A clear contact path matters when a data question appears beside a login or wallet event.

Account support Open the support route from your signed-in account when you need a copy, correction or explanation connected with your login details. We use the account path to match your request safely.
Wallet record help For DANA, OVO, GoPay or QRIS questions, include the payment reference and date rather than sending secret wallet credentials. We can trace the recorded status and explain the related data.
Privacy request Ask us to access, correct or remove eligible details through the available contact path. We may request account verification first so another person cannot alter your records.
HANDLING DETAILS

Security Choices Across Your Device Path

We handle privacy as an account process rather than a broad promise. Our controls connect the details you enter, the device session you use and the wallet event you create, while access…

Collected account details

We may record your phone number, account credentials, verification result and support messages. These details help us open the correct account, protect sign-in and answer a request about your records.

Cookies and sessions

Cookies can keep a browser session working, remember selected settings and help detect unusual sign-in activity. You can manage cookie controls in your browser, although some account functions may then behave differently.

Device protection

A phone or desktop session may create technical records such as browser type, operating system and security signals. We use these details to identify suspicious access without asking for your wallet PIN.

Record retention

We keep account, payment and security records only as long as needed for the stated purpose, account support or applicable legal duties. When no valid need remains, records are removed or protected from use.

Requesting a change

You can ask us to correct inaccurate account details or explain how a record is used. Send the request through the account support path and include enough context for us to find it.

Identity checks

Before disclosing, changing or deleting account data, we may compare your request with existing account details. This step reduces the chance that another person receives or changes your records.

Privacy Policy Answers For liga788 Accounts

These answers address the questions we hear most often about the liga788 Privacy Policy. They cover account creation, mobile sessions, local wallets, cookies, record requests and the point at which local rules affect access or handling.

It covers account details, verification records, device and session data, cookies, support messages and wallet references connected with DANA, OVO, GoPay, QRIS or bank transfer activity.

We use your phone number to create and secure your account, support sign-in checks and connect a privacy request to the correct record. We do not ask you to share your password.

Yes. It covers technical details from a phone or desktop session, including browser type, operating system and security signals used to protect account access. Access depends on local law.

We may retain payment references, status and dates so we can match a DANA or QRIS event to your account and answer a receipt question. Wallet PINs should never be sent to us.

You can contact us through the support route inside your account and ask for access or correction. We may verify account ownership before disclosing, changing or removing eligible details.

Use the cookie controls in your browser or the choices presented on the site. Restricting cookies can affect sign-in sessions and other account functions, so the result may differ by device.

Local rules can affect which data requests we can complete, how long records remain available and whether account access is allowed. We apply the relevant rule where local law permits.