Reference

agenhoki Privacy Policy for Your Account

Speed Blackjack and Fish Hunter may appear in your agenhoki account history, while this Privacy Policy explains how we handle the details connected to that activity.

Account dataWallet recordsCookie choicesPhone checks
agenhoki agenhoki Privacy Policy for Your Account
CONTACT YOUR WAY

Where to Ask About Privacy Policy

A clear contact path helps you question a record without explaining your concern repeatedly. From your signed-in account, use the support route near the cashier area and state whether your request concerns login details, a wallet reference, cookies or an account correction. We may ask you to confirm the phone linked to your account before discussing private records. If you are in Medan or elsewhere in Indonesia, send the same request through the contact path shown on our site, where local law permits access.

Team online

Account contact path

Use the support route beside your account and cashier area for a Privacy Policy question. Include your registered phone number, the date of the relevant DANA, OVO, GoPay or QRIS record, and the change or explanation you want us to assess.

Privacy request details

Tell us whether you want to see, correct or remove personal data. We may request an account step, such as phone confirmation, so a private record is not sent to a different person using the same device or browser.

Status follow-up

If a privacy request relates to a pending bank transfer or virtual account reference, keep the receipt and account date available. Our support team can compare the record with your account history without asking for a wallet password or one-time code.

OUR DATA PRACTICE

What We Keep, Protect and Change

Our handling process separates account identity, device signals and payment references so a privacy request can be checked against the right record.

Account details

We use your registered phone and account details to create access, confirm ownership and answer a data request. If a correction is needed, send the accurate replacement through the account contact path rather than sharing credentials in a message.

Payment references

A DANA, OVO, GoPay or QRIS reference may be stored with an account event so we can match a receipt or investigate a status mismatch. We do not need your wallet password, card secret or one-time code for that check.

Mobile browser signals

When you move from a mobile browser to desktop, we may record browser type, session details and connection signals for account-security checks. These signals help us spot unusual access without treating your device data as a public profile.

Cookies and sessions

Cookies can keep a signed-in session working and remember choices made on the site. You can clear cookies through your browser settings, although doing so may require you to complete phone verification again before account details are shown.

Retention requests

We keep selected records for the period needed to operate the account, resolve a payment question or meet a legal requirement. Ask us which record is involved and why it remains; we will assess correction or removal where local law permits.

Security concerns

If you notice an unfamiliar sign-in, device change or account event beside a game such as kapak88 or bola2289, contact us through the account support route. We may pause discussion until phone ownership is confirmed and the account record is matched.

Privacy Policy Questions for agenhoki

These Privacy Policy answers cover the questions we expect you to ask before opening an account or requesting a data change. They explain what we collect, how wallet references and cookies are handled, what happens when you change devices, and how to contact us from Indonesia. For a personal request, use the account contact path so we can verify the correct record.

It covers account details, phone verification, sign-in and device signals, cookies, game activity records and payment references such as DANA, OVO, GoPay and QRIS. It also explains how you can ask us to access, correct or remove personal data where local law permits.

We use your phone number to create an account path, confirm ownership and protect private account discussions. Before we disclose a record or process a correction, we may ask you to complete phone verification so another person on your device cannot receive your details.

Yes. A DANA or QRIS reference may be linked to an account event so we can compare a receipt, investigate a status mismatch or answer a payment-data request. We do not ask for your wallet password or one-time code to perform that comparison.

We may record browser type, session details, approximate connection signals and cookie choices when you use a mobile browser. These details support account-security checks and session handling. Clearing browser cookies can sign you out and may require phone verification before private account data appears again.

Send a request through the signed-in account support route and identify the field that needs correction. Include your registered phone number and the accurate replacement value. We may confirm account ownership first, then assess the change against operational and legal record needs.

You can request removal through the account contact path and explain which record you mean. We assess the request against account operation, payment reconciliation, dispute handling and legal retention needs. Where local law permits removal, we will explain the action and any remaining record.

Contact us from the account support route as soon as you notice an unfamiliar sign-in, device change or wallet reference. Mention the date and account activity, but never send a password or one-time code. We may use phone confirmation before discussing the event.