Reference

haka4d Privacy Policy for Your Account Data

The haka4d Privacy Policy explains how we use account details, device signals and payment records when you move from login to Live Baccarat, Pyramid Bonanza or another lobby.

Account detailsWallet recordsCookie choicesPolicy requests
haka4d haka4d Privacy Policy for Your Account Data
CONTACT PATHS

Privacy Questions, Account Help, Clear Routes

A clear contact route helps when a privacy request and an account issue arrive together. Sign in first when you can, then send the relevant account email, phone number and transaction reference without sharing your password or wallet PIN. If login stalls, use the account help route and state whether the question concerns DANA, OVO, GoPay, QRIS or another record. We can then direct the request to the right check.

Team online

Account privacy request

Use your signed-in account path to ask for a copy, correction or explanation of personal details held for your haka4d account.

Wallet record question

Include the payment rail, date and reference when asking about DANA, OVO, GoPay, QRIS, bank transfer or virtual account records.

Access concern

Tell us if a phone check, device sign-in or account-access decision affects your privacy request; access remains where local law permits.

DATA PRACTICE

Six Ways We Handle Your Personal Data

We keep privacy tied to real account events rather than vague statements. A login from a new phone, a QRIS receipt check and a request to update your contact details each create…

What we collect

We may receive your contact details, phone verification result, login history, device signals, support messages and payment references needed for account activity.

Why we use it

We use personal data to provide account access, match wallet receipts, respond to privacy requests, detect unusual sign-ins and maintain required records.

Cookies and devices

Cookies and browser storage can remember session settings on your phone or desktop; clearing them may require another login and phone check.

Account security

We use account credentials, phone verification and sign-in checks to reduce unauthorised access; never send us your password, PIN or one-time code.

Retention approach

We retain records for operational needs, account status, dispute handling and applicable legal duties, then remove or restrict them when they are no longer needed.

Your requested changes

You can ask us to correct inaccurate details, explain processing, provide available records or address a concern through the account privacy contact path.

Privacy Policy Answers for Indonesia Accounts

The questions below cover the points you are most likely to check before opening an account or linking a local wallet. We keep each answer focused on the Privacy Policy, including account access, device behaviour, payment references and ways to ask for a change. Where a request needs identity confirmation, we explain the reason without asking for your password or wallet PIN.

It covers account details, phone verification, login and device signals, cookies, support messages, payment references and requests to access or correct personal data connected with your account.

Phone verification helps connect the correct person with an account and reduce unauthorised access. We record the verification result for account security, and access remains where local law permits.

Yes. The policy covers payment references and status checks linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account routes, without requiring your wallet PIN.

A new phone or browser may create a fresh sign-in signal and ask for account verification. Cookies may also be reset, so you could need to log in again.

Yes. Send a privacy request through the account contact path with enough detail to locate your account. We may confirm identity before providing records or changing inaccurate details.

Retention depends on the purpose, account status, payment dispute needs and applicable legal duties. We remove or restrict records when they are no longer required for those purposes.

Use the signed-in account help route and identify the privacy issue, such as a cookie question, device sign-in, wallet reference or correction request. Do not include passwords or PINs.