Reference

ligapedia Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use and protect the details connected to your ligapedia account, from phone verification to DANA, OVO, GoPay and QRIS status.

Account dataCookie choicesWallet recordsRequest access

Explore Our Lobby Read FAQ

How Our Privacy Policy Works

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

Our Privacy Policy covers the information needed to create and protect your account, including contact details, phone verification results, login activity, device signals and records linked to wallet actions. We use these details to keep your account path clear, confirm a payment status and investigate a

1
receipt when DANA, OVO, GoPay, QRIS, bank transfer or a virtual account is involved. We may also process technical data from the device and browser used to reach the lobby, such as session settings and security events. We do not treat a policy request as a
2
payment request; each follows its own account support path. Access and eligibility depends on local law. We retain records only for operational, security or legal needs described in this policy, then remove or de-identify them when those needs end. You can ask us what we hold,
3
request a correction or raise a question through support.

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

HELP WITH REQUESTS

Three Ways To Ask About Privacy

A privacy question should not leave you guessing which account route to use. We separate policy requests from wallet troubleshooting so your message reaches the right handling path.

Account request Ask us to confirm the personal data connected to your ligapedia account or explain why a phone verification detail appears in your record. Include the contact detail on the account so we can match the request without asking you to disclose a password.

Wallet context If your question involves DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, send the receipt reference and date rather than wallet credentials. We use that context to separate a payment-status query from a Privacy Policy data request.

Security concern Report an unfamiliar login, device event or account change through the support path linked to your account. We may ask for verification before discussing records, helping keep your profile private while we check the reported activity.

DATA HANDLING

Six Privacy Controls We Keep Clear

The Privacy Policy is practical because each control connects to something you can see in your account journey.

Data collected

We may collect contact details, account identifiers, phone verification results, login events and device or browser signals. Payment references can show that DANA, OVO, GoPay, QRIS, bank transfer or a virtual account action was checked, without requiring your wallet password.

Cookie settings

Cookies and similar session tools help keep you signed in, remember a selected path and identify unusual access. You can manage browser cookie controls, although limiting them may interrupt account navigation or require another sign-in check.

Account security

Phone verification and login checks help us protect account access. If you move between a mobile device and desktop, the security record may show both paths so we can investigate an unfamiliar session without exposing account details to another person.

Payment records

We keep the reference details needed to match a receipt, wallet status or transfer check with your account. The Privacy Policy does not ask you to send a PIN, password or full wallet credential when you contact support.

Retention period

We retain account, security and transaction-reference records only while they serve an operational, security or legal purpose described here. When that purpose ends, we remove the record or reduce it so it no longer identifies you where practical.

Changes and contact

You can ask for access, correction or clarification through the account support route. State the request, provide the account contact detail and tell us the affected record; we may verify ownership before making a change or sharing details.

Privacy Policy Questions Before Access

These Privacy Policy answers address the searches we hear before an account is opened or a wallet is connected. They cover what we collect, how device activity and cookies fit the account path, and how to request a copy or correction. If your situation is different, use the support route with the account contact detail and keep passwords, PINs and full wallet credentials out of the message.

The Privacy Policy covers account details, phone verification, login and device events, cookie use, payment references and support requests. It explains why we use each category, how retention works and how you can request access or correction. Eligibility and access depends on local law.

We may collect your account contact details, account identifiers, phone verification result, browser or device signals, login events and records needed to check DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Yes. The Privacy Policy covers payment references and status checks connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account actions. These references help us match a receipt or investigate a status without asking for your wallet password or PIN.

Cookies can keep a session active, remember a selected account path and help identify unusual access. You can change cookie controls in your browser, but restricting them may interrupt navigation or trigger another phone or login verification step.

You can contact support with the account email or phone detail, state whether you want access or correction and identify the record involved. We may verify account ownership first, then explain the available action under the Privacy Policy and local requirements.

We keep account, security and payment-reference records only for the operational, security or legal purposes described in the Privacy Policy. When a purpose ends, we remove or de-identify the relevant record where practical, subject to applicable local requirements.

Use the account support route and describe the concern, affected device or account event, and approximate date. Do not send a password, PIN or full wallet credential. For an unfamiliar login or change, mention that first so the security check can begin.

ligapedia Privacy Policy For Your Account

Three Ways To Ask About Privacy

Six Privacy Controls We Keep Clear

Data collected

Cookie settings

Account security

Payment records

Retention period

Changes and contact

Privacy Policy Questions Before Access

01 What does the ligapedia Privacy Policy cover?

02 What personal data does ligapedia collect?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How do cookies affect my ligapedia account?

05 Can I request a copy or correction of my data?

06 How long does ligapedia keep account information?

07 Where should I report a privacy or security concern?

Related Pages