Reference

Privacy Policy for your webhoki account

Our webhoki Privacy Policy explains what account, device and wallet details we use when you open an account, sign in and check payment status.

Account dataWallet recordsCookie choicesDevice access
webhoki Privacy Policy for your webhoki account
HELP WHEN NEEDED

Get a clear privacy support path

A direct support route matters when a Privacy Policy question affects your account or wallet record.

Account data request Ask us to locate the personal data connected with your account by using the support route beside account access. Include your registered phone detail and the request you want handled, so we can check identity before releasing or changing account records.
Wallet record check If a DANA, OVO, GoPay or QRIS reference looks wrong, send the transaction reference through the account support path. We use the receipt and status record to investigate the specific event, while keeping your wallet password and private authentication details out of the request.
Cookie and device help For cookie choices, repeated sign-in prompts or an unfamiliar device session, tell us which phone or desktop path you used. We can explain the relevant Privacy Policy purpose and help identify the session without asking you to disclose a password.
ACCOUNT DATA CARE

See how we handle your privacy choices

Your Privacy Policy questions are handled around the actual account steps you take, from phone verification to a wallet status check.

Collection at account entry

We collect the contact and verification details needed to create and protect your account. A phone verification step can confirm that an access request belongs to you. We do not need your DANA, OVO, GoPay or QRIS password for this account process.

Cookies on web pages

Cookies can keep a session connected, remember a selected setting and help us understand which Privacy Policy page was opened. You can ask support about a cookie choice or clear cookies in your browser, though a fresh sign-in may then be required.

Device and session signals

We may record device type, browser details, sign-in time and related session signals to spot an unusual account request. This helps us distinguish your phone path from a new desktop path without treating the device signal as your wallet credential.

Payment references only

A payment receipt can show a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference and its status. We use that record to connect a cashier enquiry to the right account event, not to request or store your private wallet password.

Retention by purpose

We retain account, access and payment records for as long as the service purpose or applicable legal duty requires. When a record is no longer needed, we remove it or separate it from direct account identifiers where the applicable process permits.

Requests and corrections

You can ask us to access, correct or clarify personal data held for your account through the support path. Include the registered phone detail and requested change; we verify the requester first, then explain any limit that depends on local law.

Find answers about Privacy Policy

These Privacy Policy answers focus on the account, device and payment records you are most likely to ask about before opening access. If your situation is specific, use the account support path with a reference rather than sending a wallet password.

The webhoki Privacy Policy covers account creation, phone verification, sign-in activity, device signals, cookies, support requests and payment references. It explains why we use each category, how retention works and how you can ask for access or correction where local law permits.

You provide the account and contact details needed for registration and phone verification before account access. We may also receive device and session details when you sign in. We do not need your DANA, OVO, GoPay or QRIS wallet password.

Yes. Our Privacy Policy covers the payment reference, status and receipt details connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use those records to match a specific cashier event with your account and resolve a support request.

You can request access, clarification or correction through the support path linked to your account. Include your registered phone detail and describe the requested change. We verify your identity before responding, and the available action depends on local law and any required retention.

We use cookies to keep a web session connected, remember selected settings and understand which policy page was opened. Clearing them may sign you out or remove a setting. You can ask support about cookie choices and browser-based Privacy Policy requests.

We keep account, device and payment records for the time needed for their stated service purpose, account protection or an applicable legal duty. After that period, we remove or separate direct identifiers where the applicable process permits. Ask support about a particular record.

Use the account support path and mention the phone or desktop device, approximate sign-in time and any related payment reference. Do not include a password. We can check the session record, explain the Privacy Policy basis and help secure the account where local law permits.