Reference

Privacy Policy for Your hah4d Account

hah4d Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and cashier.

Account dataWallet referencesCookie choicesAccess requests
hah4d Privacy Policy for Your hah4d Account
HELP WITH PRIVACY

Get Clear Answers Through Account Support

Privacy questions should not leave you guessing about a wallet receipt or a sign-in record.

Account help Use the account help path when your phone verification, session history or privacy request…
Payment records For DANA, OVO, GoPay or QRIS questions, send the payment reference and its visible…
Privacy contact When you want access, correction or deletion details, choose the privacy contact shown in…
DATA HANDLING

What We Do With Account Information

We handle privacy as part of the account path rather than as a separate promise.

Account details

We collect the details you enter during account creation and phone verification so we can provide access to the correct…

Payment references

A wallet or bank payment can create a reference, status and reconciliation record.

Cookies and sessions

Cookies can keep your signed-in session, language choice and consent setting available when you move from mobile login to the…

Device protection

We may record device type, browser details, approximate connection signals and sign-in events to protect account access.

Retention choices

We remove or anonymise records when they are no longer needed for the stated account, payment, security or legal purpose.

Your requests

You can ask what account data we hold, request a correction, ask about deletion or withdraw a permitted consent.

Privacy Policy Answers for hah4d

These Privacy Policy answers address the searches we hear most often before account access. They cover what is collected, how local payment references are handled, how cookies affect a mobile session and where to send a request. If your question concerns eligibility or access, the answer depends on local law and the account details available to our support team.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, payment references and retention. It explains how we use those records for access, security, reconciliation and legal duties, and how you can request access, correction or deletion where local law permits.

Our Privacy Policy does not require your DANA, OVO, GoPay or QRIS password or wallet PIN. We may retain a payment reference, visible status and reconciliation details so support can match an event to your account without receiving your private wallet credentials.

Phone verification helps connect the person requesting access with the correct account and reduces mistaken or unfamiliar sign-ins. We may use the verification event and related security record for account protection. Access and eligibility depend on local law and the details supplied during the account step.

Cookies can preserve your session, language and consent choice when you move from mobile login to the lobby. Browser settings let you remove or restrict them. If session cookies are cleared, our account flow may ask for phone verification again before access is restored.

Yes, you can send a correction request through account support or the privacy contact shown on our site. Include the account phone number and describe the field that needs changing. We verify ownership first, then update the record where local law permits.

You can ask us to explain deletion options for your account data. We assess the request under local law and may retain payment, security or support records needed for reconciliation, disputes or legal duties. We will identify what can be removed and what must remain.

Open the account help area and use the privacy contact or support email displayed there. Include your account phone number, request type and any relevant payment reference, but never send a password or wallet PIN. We use the submitted details to verify ownership and respond.