Reference

webhoki Privacy Policy for Your Account

Our Privacy Policy explains how webhoki handles the account, device and payment details you provide before you enter the lobby.

Account dataWallet detailsDevice choicesPolicy requests
Explore Our Lobby Read FAQ
webhoki webhoki Privacy Policy for Your Account
POLICY HELP PATH

Where Your Privacy Questions Go

A clear contact route helps you ask about data without repeating your account story across several places. Our support path can connect a Privacy Policy question with the relevant phone verification, wallet reference or device session, while keeping the request tied to your account. If you are checking access from Denpasar or another Indonesian location, include the issue and the account step you reached; eligibility still depends on local law. We use the details you send only to identify and answer the policy request.

Team online

Account request

Send a request through the account support path when you want to know which profile details we hold. Include your registered contact detail and the account step involved, such as phone verification, so we can match the request without asking for a wallet password.

Wallet question

For a DANA, OVO, GoPay or QRIS privacy question, share the payment reference rather than a PIN or secret code. We use the reference to locate the status record, explain its use under this Privacy Policy and avoid collecting unnecessary wallet credentials.

Access concern

If a mobile login, desktop session or account verification raises a data concern, tell us the device path and approximate time. Our support desk can separate an access check from a policy request while keeping the submitted details limited to the matter you raised.

DATA HANDLING PRACTICE

What We Do With Your Policy Data

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

Account security

Phone verification connects an account to the contact detail you submit before access is completed. We may use sign-in and verification records to detect an unusual session, protect your profile and explain why an account check was requested under this Privacy Policy.

Payment records

A DANA, OVO, GoPay or QRIS reference can show that a payment event was sent, matched or still pending. We retain the minimum transaction details needed for reconciliation and support, while wallet PINs and secret authentication codes remain outside our request.

Cookies

Cookies can keep a sign-in path, language choice or session state working between pages. You can manage cookies through your browser settings; restricting them may affect account access, and our support desk may ask which setting changed when diagnosing a session issue.

Device sessions

Your mobile browser and desktop browser may create separate session records, including basic device and access timing details. We use these records to investigate sign-in confusion and account security, not to request private files, contacts or wallet passwords from your device.

Retention choices

We keep account and transaction records only for the period needed for account operation, security checks, dispute handling and legal duties. When a record no longer serves one of those purposes, our internal process marks it for removal or further restriction.

Change requests

You can ask us to correct account data, explain a data use, provide a copy where available or remove details that no longer need to be held. We verify ownership first, record the request, and tell you if local law requires a record to remain.

Privacy Policy Questions About webhoki

These Privacy Policy answers cover the account and payment questions you are most likely to have before opening access. They explain what we collect, why a device or wallet reference may appear in a support reply, and how to ask for a correction or removal. If your situation involves eligibility, access depends on local law, so include your location when contacting us.

The webhoki Privacy Policy covers account creation, phone verification, sign-in sessions, browser cookies, payment references and support requests. It explains how we use details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, subject to access where local law permits.

We may collect the contact and verification details needed to create and protect your account, plus sign-in timing, device session data and support messages. We use these details for access checks, account assistance and policy requests rather than asking for private files or wallet passwords.

No. A payment record may include a reference number, amount, timestamp and status so we can match a DANA or QRIS event to your account. We do not ask for or need your wallet PIN, password or secret authentication code to handle a policy question.

Use the account support path and state whether you want a copy, correction or explanation of a particular record. Add your registered contact detail and the relevant account step, such as phone verification or a QRIS reference. We check ownership before processing the request.

Cookies can preserve a session or language choice, while basic device records can help us identify an unusual mobile or desktop sign-in. The Privacy Policy describes these uses so you can adjust browser settings and understand why support may ask about your device path.

We retain account, security and payment records only while they support account operation, transaction matching, dispute handling or legal duties. When a record no longer serves those purposes, our process removes it or restricts its use. Some records may remain when local law requires.

You can submit a removal request through support, and we will verify that you control the account before assessing it. We remove or restrict data when no valid purpose requires retention. Access depends on local law, and we will explain any record that must remain.

Related Pages

webhoki Indonesia FAQ webhoki Casino About Us Live Roulette Elite