Reference

Privacy Policy for bkhoki Accounts

bkhoki Privacy Policy explains how we collect, use, protect and retain the information connected with your account, wallet checks and lobby access.

Account dataWallet checksCookie choicesContact requests
bkhoki Privacy Policy for bkhoki Accounts
CONTACT THE TEAM

Reach Us About Privacy Policy

A direct contact route helps you ask about the Privacy Policy without explaining the same issue repeatedly.

Account request Use the support channel connected to your account when you want to ask what…
Wallet question For a DANA, OVO, GoPay or QRIS status question, share the transaction reference and…
Policy concern If you believe information was used outside the Privacy Policy, contact us through the…
DATA HANDLING

Explore How We Handle Your Data

The Privacy Policy is designed around the points where account information is actually created: phone verification, login, wallet matching, support contact and device access.

Account details

We use your phone number and account details to create access, send account-related messages and connect a verified session with…

Payment records

When you deposit or request a withdrawal through DANA, OVO, GoPay, QRIS, bank transfer or virtual account, we keep the…

Device sessions

Login time, browser or device signals can help us identify an unusual session and protect your account.

Cookies

Cookies and similar storage help remember a session, protect account forms and understand which policy page was opened.

Retention

We retain account, payment and support records only for the period needed for account operation, dispute handling, security checks or…

Your request

You can ask us to access, correct or delete eligible personal information, or ask why a record is being used.

Browse Privacy Policy Answers

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain what bkhoki needs for access, how Indonesian wallet records are handled and what to do when you want a copy, correction or deletion request. The full policy remains the controlling text, and access depends on local law.

The bkhoki Privacy Policy covers account details, phone verification, login and device records, cookies, support messages, payment references and retention. It also explains how we use information to protect access, match DANA or QRIS activity and respond to requests about your personal data.

We use your phone number to create and protect your account, complete the required verification step and connect support messages with the correct profile. We do not use phone verification as permission to read your contact book. Ask support if you need to correct the number.

The Privacy Policy covers the transaction reference, amount or status needed to match a DANA, OVO, GoPay or QRIS payment with your account. We use those records for reconciliation, receipt checks and support. Do not send a wallet password; a masked reference is sufficient.

Yes, you can contact us through the account support route and ask which personal information is held for your profile. Include your linked phone number and the scope of the request. We may verify account ownership before providing a copy or explaining any lawful restriction.

Send a correction request through support and identify the account field that is wrong, such as a phone detail or profile record. We may ask you to complete phone verification before changing it. Payment history cannot be rewritten, but an explanation can be added where appropriate.

We keep records for the period needed to operate your account, check security, resolve payment disputes or meet applicable legal duties. The Privacy Policy describes these purposes rather than promising one universal period. After that need ends, records are deleted, anonymised or restricted.

Use the account support contact shown on bkhoki between 09:00 and 22:00 WIB every day. Describe the page, device session or payment reference involved, and avoid sending passwords. Where local law permits, we will explain the relevant record and the request path available to you.