Reference

Open ligacor Privacy Policy for wallet data

The ligacor Privacy Policy explains how we use account, device, cookie and payment data when you open an account or enter the lobby.

Account dataWallet recordsCookie choicesContact path

Explore Our Lobby Read FAQ

Check DANA data in our Privacy Policy

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

Our Privacy Policy sets out the data used to open, secure and maintain your ligacor account. We may record the account details you submit, the verification step completed before access, device and browser signals used to protect the account, and payment references needed to match a

1
wallet action. For DANA, OVO, GoPay and QRIS, that can include a transaction reference, status, amount and time, rather than your wallet password. Bank transfer and virtual account records are handled for the same matching purpose. We use this material to confirm account ownership, investigate a
2
stalled status and respond to a request. Access or eligibility depends on local law, and we may update this policy when our data practice changes. The current wording remains available through the policy link in your account area.

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

HELP DESK

Ask about your policy records

A clear support route helps when a Privacy Policy question meets a real account event. From your account area, send a request about a wallet reference, cookie choice, device record or account-access concern. Include the email or phone detail tied to your account and the relevant transaction time, but never send a password or one-time code. We use the submitted context to locate the right record and explain the next step.

Team online

Account request

Use the support path inside your account when you need a copy of data linked to your login, clarification about a verification record or help identifying the correct Privacy Policy section.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the reference and status shown in your account. We can then match the payment entry without requesting your wallet password.

Access concern

If your mobile browser shows an unexpected login prompt or your policy page does not load, tell us the device path and account email. We use those details to separate access issues from policy requests.

DATA PRACTICE

Protect your account data clearly

We handle Privacy Policy questions through the same account controls used to protect your records.

Account data

We use the details you enter during account opening to create access, confirm ownership and respond to policy requests. A clear account step helps us avoid sending private records to the wrong person.

Payment references

DANA, OVO, GoPay and QRIS entries can carry a reference, status and time so we can match an account action. We do not need your wallet password to investigate that record.

Cookie controls

Cookies can support login continuity, security checks and page preferences. When you use a mobile browser, your choice applies to that browser path and can be raised with our support route.

Device security

We may use browser, device and sign-in signals to identify unusual account access. These signals help us ask for an ownership check before changing account-linked data.

Retention period

We keep account, payment and support records only while they serve the purpose described in this Privacy Policy or a legal need. When no valid need remains, we remove or restrict them.

Change requests

You can ask us to correct, access or restrict account-linked data through the support path in your account. We may request a phone or email check before carrying out the change.

Find Privacy Policy answers quickly

These Privacy Policy answers focus on the searches we hear most often from Indonesian account holders. They explain the records behind login, wallets, cookies and contact requests without asking you to guess which team handles your question. If your case involves a particular DANA, OVO, GoPay, QRIS or bank transfer reference, include that reference through the account support path.

The ligacor Privacy Policy covers account details, ownership checks, device and browser signals, cookies, payment references, retention and requests to access or change data. It also explains how to contact us about those records.

We use account data to create your login, confirm ownership before account access, protect the account from unusual sign-ins and answer a request about your records. We do not ask for a wallet password to match payment activity.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references, including status, amount and time where needed to match an account action. Bank transfer and virtual account records follow the same stated purpose.

Open the support path inside your account and ask for the account-linked data described in the Privacy Policy. Add your account email or phone detail, but leave out passwords and one-time codes.

You can request a correction through the account support path. Tell us which record is wrong and what should change. We may check the phone or email connected with your account before editing it.

Cookies may support login continuity, security checks and page preferences. On a mobile browser, your choice stays tied to that browser path. The Privacy Policy explains the purpose, and support can help with a related request.

Account access or eligibility depends on local law. Where local law permits, you can read the Privacy Policy through the account area and contact us about data connected with your login or payment reference.

Open ligacor Privacy Policy for wallet data

Ask about your policy records

Account request

Wallet question

Access concern

Protect your account data clearly

Account data

Payment references

Cookie controls

Device security

Retention period

Change requests

Find Privacy Policy answers quickly

01 What does the ligacor Privacy Policy cover?

02 Why does ligacor need my account data?

03 Does the Privacy Policy include DANA and QRIS data?

04 How can I request a copy of my ligacor data?

05 Can I ask ligacor to correct my data?

06 How are cookies handled on a mobile browser?

07 Can I access ligacor under this Privacy Policy?

Related Pages