Reference

hoki 236 Privacy Policy For Your Account

The hoki 236 Privacy Policy explains what we collect when you create an account, open Baccarat or Sportsbook pages, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesSecurity checks
hoki 236 hoki 236 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Beside Wallet Records

A clear contact route helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record. Start from the support path connected to your account and describe the exact issue, such as a QRIS receipt, a device sign-in or a request to change stored contact details. We use the account context to route your question without asking for unnecessary payment secrets.

Team online

Policy questions

Use the account support path to ask how the Privacy Policy applies to your sign-in history, cookie settings, contact details or records connected with Baccarat and Sportsbook pages.

Wallet records

If a DANA, OVO, GoPay or QRIS receipt needs checking, include the visible reference and account identifier only; never send a wallet PIN, password or one-time security code.

Change requests

Ask through the same support route to correct your contact details, question a stored device entry or request access to personal records held for your account.

DATA PRACTICE

QRIS Records And Account Security

We handle privacy through ordinary account controls rather than vague promises. The policy distinguishes account details, payment references, device activity, cookies and support correspondence, so you can ask about a specific record.

Data collected

We may record account contact details, verification entries, sign-in times, device signals, selected lobby pages and support messages when those details are needed to operate or protect your account.

Cookie controls

Cookies can help keep a sign-in path consistent between the account page and lobby. Your browser settings provide a practical way to remove or restrict them, although some account steps may then need repeating.

Wallet references

For DANA, OVO, GoPay and QRIS, we keep the payment reference and status needed to match an account record; we do not ask for your wallet PIN in a privacy request.

Account security

A clear phone verification step can be used before account access or a sensitive change. If a new device signs in, we may check account details before discussing stored records.

Retention approach

We retain different records for different periods based on their purpose, account needs and local legal requirements. You can ask which category applies to a particular record through the support route.

Your requests

You can ask for access, correction or clarification about personal data connected with your account. We may confirm your identity first so a request does not expose records to another person.

Privacy Policy Questions From Indonesia

These answers address the privacy searches we hear most often before account access. They cover the records connected with local wallets, mobile sign-in, cookies, corrections and contact requests, so you can decide what to share and where to ask for clarification. If your situation is unusual, use the account support path with only the details needed to identify it.

It covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity.

Device signals help us recognise an account access pattern and investigate unusual sign-ins. They can also explain why a phone verification step appears before you reach account pages from a different device.

We do not ask you to send a DANA, OVO, GoPay or QRIS PIN through support. The policy concerns payment references and status records needed to match activity with your account.

Use the account support path and state which contact detail or record appears incorrect. We may confirm your identity before making a change, which helps prevent another person from altering your account.

Yes. Ask through support for clarification about cookies connected with sign-in continuity and account pages. You can also adjust cookie settings in your browser, though some steps may need to be repeated.

Retention depends on the record type, its operational purpose and local legal requirements. The Privacy Policy explains the approach, and support can identify the relevant category when you ask about a specific record.

Use the support route attached to your account and describe the request without sending passwords or wallet codes. Account context lets us direct questions about access, correction, cookies or deletion where local law permits.