Reference

harum4d Privacy Policy Explained Clearly

harum4d Privacy Policy explains what we collect when you open an account, use a mobile device, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
harum4d harum4d Privacy Policy Explained Clearly
CONTACT PATHS

Privacy Help Beside Account Support

A clear contact route helps you ask about Privacy Policy without searching through unrelated account pages. After login, use the available support path for a data question, wallet reference or access concern. Include the phone number attached to your account and the relevant date so we can locate the correct record without asking you to send a password.

Team online

Policy questions

Use the support path after login to ask which account details we hold, why a record is used, or where this Privacy Policy applies. We will keep the request tied to your verified account.

Wallet references

For DANA, OVO, GoPay or QRIS questions, share the transaction reference and date through support. We use those details to trace status without requesting your wallet PIN or private wallet credentials.

Access concerns

If phone verification or a device sign-in blocks your account, contact support with the registered phone number and device path. We may ask account questions before discussing personal data or changing access details.

HANDLING DETAILS

How We Manage Your Privacy Choices

Privacy work is part of the account flow, from the first phone check to a later request about stored data.

Data collection

We collect account details you submit, phone verification results, login activity, device signals and support messages. Payment references from DANA, OVO, GoPay, QRIS or bank rails help us match a transaction to the correct account.

Cookie controls

Cookies can keep a session connected and help us understand basic site access. You can adjust cookie settings in your browser, although blocking some cookies may require another login or limit policy-page functions.

Account security

We use the phone verification step before discussing account access or sensitive details. Never send a password, wallet PIN or one-time code through support, even when asking about Privacy Policy.

Retention periods

We retain account, access and transaction references only for the period needed for account operation, dispute handling, security checks or legal duties. When a record is no longer needed, our handling follows applicable requirements.

Correction requests

You can ask us to correct an inaccurate name, phone detail or account record through the policy support path. We may verify your account first so a change is not applied to the wrong person.

Deletion enquiries

You may ask whether account data can be removed by contacting support through the stated route. We will explain any records that must remain for security, transaction matching or legal duties.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the questions we expect before an account is opened or a data request is sent. They explain device records, wallet references, cookies, corrections and access checks in plain language, with the support route available when your situation needs account-specific attention.

The Privacy Policy covers details you enter, phone verification, login activity, device signals, support messages and payment references. We use them to operate access, answer requests, check security and meet applicable duties.

No. Our Privacy Policy distinguishes transaction references and status from wallet credentials. When you use DANA, OVO, GoPay or QRIS, do not send a PIN, password or one-time code through support.

Contact us through the policy support path after login, identify the registered phone number and describe the correction. We may complete phone verification before changing a name, phone detail or other record.

Yes. The Privacy Policy explains that cookies can maintain a session and record basic site access. You can adjust browser settings on your phone, though blocking cookies may require another login.

We keep payment references for the period needed for account operation, transaction matching, dispute handling, security checks or legal duties. The applicable retention period can depend on the record and local requirements.

You can send a deletion enquiry through support. We will assess the request and explain whether some account, security or transaction records must remain for legal duties or accurate payment matching.

Yes. Access and eligibility depend on local law. If you are in Indonesia, use the policy contact route for an account-specific question, and we will explain the applicable access position without requesting your wallet credentials.