Reference

HOKILUCK Privacy Policy for Indonesia

HOKILUCK Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and browse from a mobile device.

Account dataWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

DANA and QRIS Privacy Rules

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

Our Privacy Policy covers the details needed to create and protect your account, including your contact information, login activity, device signals and verification results. When you choose DANA, OVO, GoPay or QRIS, we record the payment reference, selected rail, status and related account action so we

1
can match a wallet event to the correct account. Bank transfer and virtual account records may include a reference linked to BCA, BRI, Mandiri or BNI processing. We use these records to check status, resolve a missing transaction and meet applicable legal duties; we do not
2
ask for a wallet password through support. Cookies help keep your session active and show relevant account settings. Access to HOKILUCK and any data request depends on local law, and our policy applies where local law permits.

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

HELP WITH PRIVACY

Privacy Support Beside Your Account

A clear support route helps when a privacy request and an account issue arrive together. Sign in and use the support contact shown near the cashier area, or follow the account-access route if login blocks you. Include your account identifier and the specific request, while leaving wallet passwords and full payment credentials out of your message.

Team online

Data access request

Ask us to confirm the personal data connected with your account through the support route shown after login. We may request account details before sending a response.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, provide the transaction reference and date rather than a password. We use those details to locate the relevant account entry.

Locked account contact

If your mobile browser cannot reach the account, use the contact path linked beside the cashier area. Explain that your request concerns Privacy Policy access or data handling.

DATA CONTROL POINTS

Cookies, Devices and Account Safety

We keep this Privacy Policy practical by connecting each data practice to an account action you can recognise.

Data we receive

We may receive account details, contact data, login events, device information and verification results when you create an account or use its security controls.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions create status references. We use them to match activity, investigate errors and maintain account records.

Cookie settings

Cookies can keep your session available and remember selected account settings. Your browser controls cookie removal, while our support route can explain their role in the account flow.

Account protection

We use login checks, phone verification and account activity signals to reduce unauthorised access. Never send a wallet password or full payment credential through support.

Retention approach

We retain account and payment records for the period needed to operate the account, resolve disputes and meet applicable legal duties. Ask support which record your request concerns.

Changes and corrections

If your name, phone detail or account record needs correction, contact us through the stated support path. We check the request against the account before changing stored data.

Privacy Policy Questions for Your Account

These Privacy Policy answers focus on the account steps Indonesian customers ask about most: mobile access, wallet records, cookies, corrections and deletion. If your situation is unusual, use the support route connected to your HOKILUCK account and describe the data request clearly.

It covers account details, phone verification, login and device activity, cookies, payment references, support requests, retention and the steps for asking about or changing stored data.

We record the payment reference, rail, status and related account action so we can match a DANA or QRIS event, resolve a missing status and keep accurate account records.

Yes. Use the support contact shown in your account and request access under the Privacy Policy. We may confirm account ownership before preparing the relevant data.

Cookies can keep your mobile browser session active and retain selected account settings. You can manage or remove them through browser controls, though some account steps may change.

Send a correction request through the account support path, naming the detail that is wrong. We compare the request with your account before updating the stored record.

You can ask about deletion through support. We assess the request against account, payment and legal record needs, so some records may need to remain for those purposes.

Account access and any data request depends on local law. The Privacy Policy applies where local law permits, and support can clarify the route available for your account.

HOKILUCK Privacy Policy for Indonesia

Privacy Support Beside Your Account

Data access request

Wallet record question

Locked account contact

Cookies, Devices and Account Safety

Data we receive

Payment references

Cookie settings

Account protection

Retention approach

Changes and corrections

Privacy Policy Questions for Your Account

01 What does the HOKILUCK Privacy Policy cover?

02 Why does HOKILUCK record DANA or QRIS details?

03 Can I ask for a copy of my account data?

04 How do cookies affect HOKILUCK on mobile?

05 How can I correct a phone or account detail?

06 Can I request deletion of HOKILUCK data?

07 Does the Privacy Policy apply in every Indonesian region?

Related Pages