Reference

Explore dorahoki Privacy Policy

The dorahoki Privacy Policy explains how we handle your account details, phone verification, device access and payment records when you use our Indonesia lobby.

Account clarityWallet recordsDevice controlsPolicy requests
Explore Our Lobby Read FAQ
dorahoki Explore dorahoki Privacy Policy
CONTACT ROUTES

Find Support for Privacy Requests

A clear contact route helps you ask what we hold, why we use it or how to correct an account detail. Use the support path connected to your account and include the relevant phone number, payment reference or device detail without sending a full wallet password. We use the same request context to distinguish a privacy question from a stalled cashier status.

Team online

Account access

When your phone verification or sign-in detail looks wrong, contact support through the account path. Tell us the affected phone number and the step that stopped, so we can locate the correct record without asking you to repeat private wallet credentials.

Wallet receipt

For a DANA, OVO, GoPay or QRIS privacy request linked to a receipt, provide the payment reference and date shown in your account. We can use that narrow context to check status while avoiding unnecessary transaction details in the conversation.

Data change

If your personal details need correction or removal, state the exact field and the reason for the request. We may ask for an account check before changing it, because a privacy update must not move control of your account to another person.

HANDLING DETAILS

Browse How We Handle Your Data

Privacy work is easiest to understand when each data use has a clear account purpose. We separate sign-in checks, payment references, device signals and browsing choices so a request can be handled…

Account records

We use the details submitted during account opening to create your account, complete phone verification and respond to access questions. If you ask what is held, we can use the account path to match the request with the correct record before discussing any personal detail.

Payment references

A cashier event may create a reference for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use that reference to match a status or receipt, not as a reason to collect unrelated wallet credentials or extra account details.

Cookies and devices

Cookies and device signals can help keep a session connected as you move from phone verification to the lobby. On mobile, they may remember a permitted session path; you can manage browser cookie settings, although changing them may interrupt account access.

Account security

Phone verification and sign-in records help us detect an access attempt that does not match your account pattern. Never send a full password in a support message. If a device is shared, sign out after checking pages such as Football Goal Rush.

Retention choices

We retain information only while it supports account operation, security, dispute handling or a legal requirement. When a record no longer serves one of those purposes, we aim to delete or anonymise it, subject to any restriction that still applies.

Request handling

You can ask for access, correction, deletion or an explanation of a data use through support. Include the account phone number and request type, but not a password. We may verify ownership before acting, then explain any limit on the requested change.

Check Privacy Policy Questions

These answers address the privacy searches we hear most often before account opening. They cover account creation, local wallet references, cookies, device access, corrections and deletion. If your situation involves a specific receipt or sign-in event, use the support route above and share only the details needed to identify that event.

The dorahoki Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, lobby actions and payment references. It explains why we use each category, how we protect account access, when records may be retained and how you can ask about your data.

DANA and QRIS can appear in a payment reference connected to your account, along with OVO, GoPay, bank transfer or virtual account details. We use the reference to check a receipt or status. We do not need your full wallet password for a privacy request.

Yes. Send a correction request through the account support path and identify the field that is wrong, such as a phone detail. We may verify that you control the account before changing it, then confirm whether the correction was made or explain why a record must remain.

Cookies can keep a permitted session connected while you move from phone verification to the lobby on a mobile browser. You can change cookie settings in that browser. Some changes may interrupt sign-in or require you to repeat the account step before access continues.

We keep personal data while it is needed for account operation, security checks, payment questions, dispute handling or a legal requirement. We do not promise one fixed period for every record. When the purpose ends, we aim to delete or anonymise the data where practical.

You can ask us to delete or anonymise personal data through support, explaining which account detail the request concerns. We may first verify account control. Some records can remain when needed for security, payment reconciliation, dispute handling or a legal duty.

Yes, access and eligibility depend on local law. You can still contact us about the data linked to your account, and we will assess the request against the applicable rule. If a limit applies, we will explain the reason and the available contact path.

Related Pages

dorahoki Indonesia About Us Football Goal Rush FAQ Live Roulette Prestige