Reference

hermes4d Privacy Policy for Your Account

hermes4d Privacy Policy explains how we handle your account details, phone verification and payment records when you use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record detailsMobile cookie choicesAccount contact route
hermes4d hermes4d Privacy Policy for Your Account
PRIVACY HELP

Contact Us About Privacy

A clear contact path helps you resolve a data question without guessing which team to reach. Use the account support route for access, correction or deletion requests, and include the phone number connected to your account so we can confirm ownership. If you are in Surabaya or elsewhere in Indonesia, the same request path applies through our available support channel and the contact route shown beside your account area.

Team online

Account request

Ask us to correct an account detail or explain a phone verification record through the account support route. We may request a matching account detail before discussing private records.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the receipt reference and date. We use those details to locate the relevant payment record without exposing another account.

Access concern

If a sign-in check or mobile cookie affects access to your privacy request, tell us the device path you used. We can explain the next account step through the available support channel.

DATA PRACTICES

See How Data Stays Account Bound

We handle privacy through practical account controls rather than broad promises. The records connected to your account help us verify access, match a wallet receipt and investigate unusual activity.

Collection

We collect account details, phone verification results, device signals and payment references when those records are needed for account access, wallet matching or a support request.

Cookies

Cookies can retain a sign-in preference and help us recognise a security event. You can adjust browser permissions on your phone or desktop, though a fresh check may follow.

Account security

Phone verification is completed before account access, while device and sign-in signals help us assess unusual entry attempts. We use these checks to protect the account tied to you.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a cashier receipt to the correct account. We use the reference for status checks, not for unrelated account messages.

Retention

We keep records only for the period needed for the stated account, payment or security purpose, unless a longer period is required where local law permits.

Your request

To ask for access, correction or removal, contact support from the account route and identify the relevant record. We confirm ownership before making a privacy change.

Find Privacy Policy Answers

These Privacy Policy answers cover the searches we hear most often before an account is opened. We keep the wording tied to real account steps, including phone verification, mobile cookies and wallet records from DANA, OVO, GoPay and QRIS. If your situation is not covered, use the privacy contact route and we will assess the request under the applicable local rules.

The hermes4d Privacy Policy covers account details, phone verification, device signals, cookies, payment references and support requests. It also explains your options for access, correction and removal where local law permits.

We use phone verification before account access to connect the request to the correct account and reduce unauthorised entry. The verification result is handled as an account-security record under this Privacy Policy.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references, including receipt dates and status details needed to match a payment question with your account.

Cookies can remember a sign-in preference and help identify an unusual device or access pattern. You can change browser permissions on your phone, but some account steps may need to be repeated.

You can contact us through the account support route and request access to records connected with you. We confirm account ownership first, then assess the request where local law permits.

Send a correction request through support and identify the account detail or wallet reference involved. We may ask for the phone number linked to the account before changing the record.

We retain account, payment and security records for the period needed for their stated purpose, unless a longer period applies where local law permits. Support can explain the relevant category.