Reference

ligahokie Privacy Policy for Your Account

Our ligahokie Privacy Policy explains what we collect when you create an account, verify your phone and use wallet options such as DANA or QRIS.

Account dataWallet recordsCookie choicesRequest access
ligahokie ligahokie Privacy Policy for Your Account
HELP PATHS

Check Privacy Help When Login Stalls

A clear support route matters when a phone check, wallet record or privacy request needs attention. We keep account assistance close to the relevant help path, so you can explain the issue without sharing a wallet password or sending unnecessary personal details. If you are in Jakarta or Yogyakarta, the same account privacy process applies where local law permits.

Team online

Account access

Use the account help route when phone verification or sign-in details look incorrect. We ask for the minimum information needed to locate your account and confirm that the request comes from you.

Wallet records

For DANA, OVO, GoPay, QRIS or bank transfer questions, include the transaction reference shown in your account. We use that reference to check status without requesting your wallet password.

Privacy requests

Ask through the privacy contact path for a copy, correction or deletion request. We may verify your account details first, then explain the action, timing and any legal reason a record must remain.

DATA PRACTICE

Browse How We Handle Account Data

Our handling process follows the account steps you actually take: create access, verify a phone, use a payment rail and contact support.

Account details

We use your submitted contact and verification details to create access, respond to account requests and protect the account from unauthorised changes. We do not ask for a wallet password during routine support.

Cookies and storage

Cookies and similar browser storage can keep your session recognised, remember selected settings and support security checks. You can manage browser storage through your device settings, though some account steps may then need repeating.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference, status and amount records. We use these details to match your account activity and investigate a payment question.

Account security

Phone verification, sign-in records and device signals help us review unusual access. Keep your sign-in details private and contact account help if a device, phone number or session no longer belongs to you.

Data retention

We keep account, payment and security records only for the period needed for account operations, dispute handling, fraud checks or legal duties. When a record is no longer needed, our process addresses its removal or protection.

Changes and contact

You can request access, correction or deletion through the privacy contact path. Tell us which account detail or record concerns you; we may verify ownership before changing or releasing personal data.

Find Answers About Privacy Policy

These questions cover the privacy points you may check before opening an account or connecting a local wallet. We keep each answer tied to the actual account path, including phone verification, browser storage, payment references and requests for access or correction.

The ligahokie Privacy Policy covers account details, phone verification, sign-in events, browser storage, payment references, support requests, security records and the ways you can ask to access or change your data.

We collect the contact and account details you submit, phone verification status, sign-in activity and selected settings. Device and browser signals may also be used to help protect account access from unusual activity.

No. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we handle transaction references and status details needed to match activity, not your wallet password.

Cookies and browser storage can maintain your session, remember settings and support security checks. You can clear or manage them through device settings, but some sign-in or verification steps may need to be repeated.

Use our privacy contact path and describe the account detail or record involved. We may verify that you control the account before providing a copy, correcting information or explaining the available action.

You can submit a deletion request through the privacy contact path. We assess the request against account needs, payment disputes, security checks and legal duties, then explain what can be removed and what must remain.

Yes. Account access and eligibility depends on local law. Our Privacy Policy still explains data handling for permitted access, including phone verification, wallet references, browser storage and requests sent to our support path.