Reference

Open your hoki234 Privacy Policy path

Our Privacy Policy explains what we collect when you create an account, verify your phone, use DANA or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesPolicy requests

Explore Our Lobby Read FAQ

Browse how our Privacy Policy works

hoki234 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We use account details to open and maintain your hoki234 access, confirm your phone, protect the sign-in process, and match wallet activity to the correct account. A deposit request can include the selected rail, amount, reference, and status, whether you choose DANA, OVO, GoPay, QRIS, bank

1
transfer, or a virtual account. We may also receive device, browser, IP, session, and cookie data so we can detect unusual sign-in patterns and keep the policy page available. Game or table activity, such as a visit to Bingo, Fish Hunter, or Speed Baccarat, may be
2
connected to account records when needed for support, security, or legal duties. We keep records only for the operational or legal period that applies, then remove or de-identify them where practical. Access depends on local law. If a request needs identity checking, we will ask for
3
account details through our support path rather than disclose records to an unverified person.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

ASK ABOUT YOUR RECORDS

Contact us about Privacy Policy requests

A clear support route helps you ask what data we hold, why it is used, or how a correction request should be sent.

Account request Ask us to correct an account detail by stating the field that needs changing and the phone verification step you completed. We may confirm ownership before updating the record.

Wallet record For a payment record, share the rail name, reference, date, and status shown near the cashier path. We can then match the request without asking for your wallet password.

Access question If the Privacy Policy page or account path does not open, tell us your device type, browser, and region. Eligibility is handled where local law permits and may require a location check.

HOW WE HANDLE DATA

Explore the Privacy Policy controls

We keep the policy practical by linking each data use to an account action you can recognise.

Account details

We collect details needed for account creation, phone verification, sign-in checks, and support replies. A correction request should identify the inaccurate field, while access depends on confirming that the account belongs to you.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity can leave a reference, amount, time, and status record. We use those details to trace cashier questions and meet applicable duties.

Device signals

Your browser, device type, IP address, session timing, and security events may be recorded when you sign in. These signals help us spot unusual access without needing the contents of your private device.

Cookies

Cookies can remember a session, support page operation, and help us understand whether a policy page loads correctly. You can adjust browser cookie settings, although some account steps may then require another sign-in.

Account security

Keep your password and wallet credentials private, and contact us if a sign-in or payment status looks unfamiliar. We may ask for phone or account verification before discussing personal records.

Retention and changes

We retain records for operational, dispute, security, or legal needs, then remove or de-identify them where practical. Ask us to review a record, correct it, or explain the reason it remains stored.

Find answers in our Privacy Policy

These answers cover the questions we expect you to ask before opening an account or sending a policy request. They focus on account data, Indonesian wallet records, device behaviour, cookies, retention, and the checks we use to protect your privacy.

It covers account and phone details, wallet references, device and session data, cookies, game activity connected to support or security, retention, correction requests, and the contact path for privacy questions.

Phone verification helps us confirm account ownership before access and before discussing personal records. It also reduces mistaken changes when a request concerns DANA, OVO, GoPay, QRIS, or bank transfer activity.

Yes. We may retain the selected rail, reference, amount, time, and status for DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity so support can trace a request.

Use our support path and state the account detail that needs correction, the connected phone detail, and the reason. We may verify ownership first, and you should never send a password or wallet PIN.

The policy may cover your browser, device type, IP address, session timing, and security events. We use these signals to support sign-in protection and investigate unusual access, not to read private device content.

Cookies can keep a session active and help us check whether the page and account path operate correctly. You can change browser settings, but disabling cookies may require repeated sign-in steps.

You can ask us to assess removal or de-identification. We first verify the request, then consider operational, security, dispute, and legal retention needs. Access depends on local law and the record involved.

Open your hoki234 Privacy Policy path

Contact us about Privacy Policy requests

Explore the Privacy Policy controls

Account details

Payment records

Device signals

Cookies

Account security

Retention and changes

Find answers in our Privacy Policy

01 What does the hoki234 Privacy Policy cover?

02 Why does hoki234 need my phone verification?

03 Does the Privacy Policy include payment data?

04 How can I request a correction to my data?

05 What device data does hoki234 collect?

06 How do cookies work on the Privacy Policy page?

07 Can I ask hoki234 to remove my personal data?

Related Pages