Reference

Privacy Policy for Your haes4d Account

Our Privacy Policy shows how haes4d handles the details connected with your account, wallet activity and mobile access.

ACCOUNT DATAWALLET RECORDSDEVICE ACCESSPOLICY CONTACT

How DANA and QRIS Data Is Used

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

We use account details to create access, confirm your phone and connect the wallet choice you make during a transaction. A DANA, OVO, GoPay or QRIS request can produce payment status, reference and receipt records, while bank transfer or virtual account activity may carry a bank

1
reference needed for matching. We use these records for account administration, payment checks and support responses, not as a reason to collect unrelated device content. Your browser or mobile device may send technical details such as session time, device type and security signals when you sign
2
in. We retain records for the period needed for the stated purpose and applicable obligations. For access from Makassar or elsewhere in Indonesia, eligibility depends on local law; the Privacy Policy explains how to ask about your data, correction or deletion.

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

PRIVACY HELP DESK

Support When Privacy Questions Arise

A clear contact path matters when your account record or wallet reference needs checking. Use the support route inside your account and include the email or phone detail linked to your profile; this helps us locate the right record without asking you to send a full payment credential. We can also direct a question from the cashier path to the privacy team.

Team online

Account contact

Send a privacy request through account support after signing in. We use your verified phone or account detail to match the request, while you should never include a wallet PIN or full security code.

Wallet record

If a DANA, OVO, GoPay or QRIS reference appears in your account history, mention its date and status. That lets us investigate the relevant record without requesting unnecessary transaction details.

Cashier path

When a receipt or wallet status is part of your privacy question, start from account help beside the cashier area. We can separate payment support from a request to change personal data.

SECURITY IN PRACTICE

Account Security Across Mobile Devices

The way we handle privacy is visible in ordinary account steps, from phone verification to a signed-in session on your mobile browser.

Collected details

We may handle your account contact details, phone verification result, payment reference, device signals and support messages. We use each category only for the account, transaction or privacy purpose connected to it.

Cookies and sessions

Cookies and session markers help keep your sign-in and selected account path working. You can manage browser permissions, although limiting essential storage may affect secure access to your account.

Phone verification

Before account access, phone verification helps connect a request to the correct profile. We do not need your wallet PIN, card secret or one-time security code to answer a privacy request.

Payment matching

For bank transfer, virtual account and QRIS records, we use reference details to match status and receipt history. Withdrawal checks may create verification records, which remain subject to the retention period in this policy.

Retention choices

We keep personal data while it serves account administration, payment reconciliation, security or a required record. When a retention period ends, we remove, de-identify or restrict the relevant data where appropriate.

Change requests

Ask us to correct, access or remove eligible personal data through account support. Include the account contact used for verification; we may ask for limited proof before changing a protected record.

Privacy Policy Questions for Indonesia

These answers address the searches we hear most often about personal data, wallet records and account access. If your situation is different, use the account support route and describe the specific record or device involved.

It covers account details, phone verification, payment references, device signals, cookies, support messages, retention and requests to access, correct or remove eligible personal data.

Yes. The Privacy Policy explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be used to match payment status, receipts and account support.

When you sign in, we may receive technical signals such as device type, browser details, session time and security indicators. We use them to support account security and access checks.

Use the support path inside your account and identify the email or phone linked to your profile. We verify the request before sharing, correcting or changing protected account records.

We retain data while needed for account administration, payment matching, security, support or applicable obligations. After that need ends, we remove, de-identify or restrict records where appropriate.

Yes. Contact account support with the detail that needs correction and the contact used for phone verification. We may request limited proof so a protected record is not changed by another person.

Access and eligibility depend on local law. If you are in Indonesia, read the policy and contact support for a data question before opening an account or using wallet-linked services.

Privacy Policy for Your haes4d Account

Support When Privacy Questions Arise

Account contact

Wallet record

Cashier path

Account Security Across Mobile Devices

Collected details

Cookies and sessions

Phone verification

Payment matching

Retention choices

Change requests

Privacy Policy Questions for Indonesia

01 What does the haes4d Privacy Policy cover?

02 Does the Privacy Policy cover DANA and QRIS payments?

03 What device data does haes4d receive?

04 How can I request my haes4d data?

05 How long does the Privacy Policy allow data to remain?

06 Can I ask haes4d to correct my account details?

07 Does access under this Privacy Policy depend on location?

Related Pages