Reference

Privacy Policy for Your liga5000 Account

Our Privacy Policy shows how we handle the account details, wallet records and device signals connected with liga5000.

Account dataWallet recordsDevice choicesPolicy requests

How Wallet And Account Data Is Used

liga5000 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect details needed to create and protect your account, confirm phone ownership, answer support requests and match wallet activity with the correct account. That can include your contact details, verification records, login events, device type, browser settings and transaction references. When you use DANA, OVO,

1
GoPay, QRIS, bank transfer or a virtual account, we receive status and reference data needed to reconcile the account record; we do not present your wallet PIN as part of our account history. We use this material to operate the requested account service, detect unusual access
2
and meet obligations that depend on local law. Where local law permits, you can ask what we hold, request a correction or ask about deletion limits. This Privacy Policy applies to data connected with our website and account areas.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Get Privacy Help Beside Your Account

A clear contact path helps when a data request, login record or wallet status needs attention.

Account help path Open your account menu, choose the help route and state that your request concerns the Privacy Policy. We may ask for your registered phone detail or a recent account reference so we can confirm that the request comes from you.

Cashier-linked questions For a wallet record, use the help path beside the cashier area and mention DANA, OVO, GoPay or QRIS by name. A payment reference helps us locate the relevant status without requesting your wallet PIN or full banking credentials.

Data request follow-up If you ask for access, correction or removal, we keep the conversation attached to your account case. We may need one account step for identity confirmation, then we explain the available action and any limit that depends on local law.

HANDLING DETAILS

Six Practical Rules Behind This Policy

Privacy choices matter most at the points where you sign in, move between devices or check a wallet record. We therefore describe the handling steps rather than relying on broad promises.

Data we receive

We may receive your phone detail, account settings, verification result, login time, device type and support messages. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, we use transaction references and status details rather than collecting your wallet PIN.

Cookies on your device

Cookies can keep account pages working, remember selected settings and help us understand whether a page request belongs to an active session. Your browser controls cookie removal. Clearing them may require you to complete phone verification again before account access.

Account security checks

A phone verification step may be required before we disclose account records or process a change request. Login events and device signals help us spot an unusual sign-in. Never send a password, wallet PIN or complete bank credential through support.

Retention of records

We retain account, support and transaction references for as long as needed for the stated service purpose, dispute handling or a requirement that depends on local law. When a retention period ends, records are removed or separated from direct account use.

Requesting a correction

If your phone detail, account name or contact record is inaccurate, contact us through the account help path and describe the field that needs attention. We may request a matching account step before changing it, helping prevent another person from altering your record.

Requesting policy changes

You can ask how we use a specific data item, request a copy where available or ask about removal. Send the request through the support route linked to your account. We explain the result, timing and any restriction that depends on local law.

Privacy Policy Questions For Indonesia

These answers address the Privacy Policy searches we expect from someone checking liga5000 before opening an account. They cover wallet records, device behaviour, account access and requests for personal data. If your case involves a specific receipt or sign-in, use the account help path so we can identify the relevant record without exposing private details.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and transaction references. It also explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account status may connect with your account record.

Phone verification helps us confirm account ownership before access to certain account records or a data change. It also reduces the chance that another person can alter your details. Any access or eligibility step depends on local law.

Yes. The Privacy Policy covers the payment references and status details we need to match DANA or QRIS activity with your account. We do not ask you to send a wallet PIN, and a receipt reference is usually more useful than full banking credentials.

You can contact us through the account help path and ask which account, support or transaction records are available for access. We may confirm your phone detail first. We then explain the response and any limit that depends on local law.

Cookies help keep a mobile session working and remember selected page settings. If you clear them, you may need to sign in or complete phone verification again. Your browser provides the control for removing cookies from the device you use.

We keep records for the stated account purpose, support follow-up, transaction reconciliation or a period required by local law. The exact period can vary by record type. You can ask support which retention reason applies to a particular account item.

Send a correction or removal request through the support route connected with your account and identify the relevant field or record. We may complete one account verification step, then explain what can change and what must remain where local law permits.

Privacy Policy for Your liga5000 Account

Get Privacy Help Beside Your Account

Six Practical Rules Behind This Policy

Data we receive

Cookies on your device

Account security checks

Retention of records

Requesting a correction

Requesting policy changes

Privacy Policy Questions For Indonesia

01 What does the liga5000 Privacy Policy cover?

02 Why does liga5000 need my phone verification?

03 Does the Privacy Policy include DANA and QRIS records?

04 Can I request a copy of my liga5000 data?

05 How do cookies affect my account on mobile?

06 How long does liga5000 keep account records?

07 How do I correct or remove data in the Privacy Policy?

Related Pages