Reference

Privacy Policy for Your Account Data

DANA, OVO, GoPay, and QRIS wallet records, login checks, cookie choices, and support messages are covered here so you know what we collect before you open an account.

DANA data contextCookie choice logAccount access checksSupport request path
hermatoto Privacy Policy for Your Account Data
CONTACT ROUTES

Three Privacy Contact Paths

Privacy requests need a clear route, so hermatoto keeps separate contact paths for account data, wallet traces, and cookie questions.

Live Chat Use live chat after login when you need a quick privacy check, such as confirming which phone number is linked or whether a QRIS payment trace is attached to your account.
WhatsApp Support WhatsApp is useful when you cannot enter the account page. We ask for limited identity checks, then move sensitive requests back to the account channel when access is restored.
Email Desk Email works for correction or deletion requests that need a written trail. Include your username, registered mobile number, and the payment rail involved, but do not send passwords.
ACCOUNT CONTROLS

Six Data Handling Checks

Account privacy works only when collection, access, storage, and correction are handled in a repeatable way.

Account opening data

When you join, we collect the details needed to create and protect the account, including username, mobile number, password record, and contact channel used for recovery checks.

Payment records

DANA, OVO, GoPay, and QRIS activity is logged with time, amount, sender reference, and account match so our wallet team can trace credits and resolve disputes.

Cookie controls

Cookies help keep you signed in, remember language choices, and detect repeat device activity. You can clear browser cookies, but we may ask for login checks again.

Device checks

A new phone, browser, or network can trigger extra verification. This protects your account when someone attempts access from a device we have not seen before.

Retention windows

We keep records while they are needed for wallet reconciliation, dispute handling, security checks, and legal duties. Older records are restricted or removed when those needs end.

Correction requests

If your mobile number, email, or payment detail is wrong, contact us from the registered channel. We verify the account first before editing any stored record.

Privacy Questions Before You Join

Before you open an account, you should know how your data is collected, checked, stored, and corrected. These answers focus on the Privacy Policy only: account details, wallet traces, cookies, device logs, support messages, and the steps we use when you ask us to make a change. If a request involves access, eligibility still depends on local law and is available only where local law permits.

We collect the details needed to create and protect your account, such as username, mobile number, password record, contact channel, device signal, and the payment rail you choose.

Yes, we store wallet transaction records linked to your account, including time, amount, reference, and status. These records help us reconcile payments and answer disputes you raise.

Cookies keep your session active, remember basic preferences, and help detect unusual access. If you clear them, you may need to log in again and pass extra checks.

Yes. Contact us through live chat, WhatsApp, or email with your username and registered mobile number. We verify the request before changing profile, contact, or payment-related records.

Only support staff assigned to account help, wallet traces, or privacy requests can access your messages. We use those records to answer your case and keep an audit trail.

We keep records while they are needed for account security, wallet reconciliation, dispute handling, and legal duties. When the reason ends, records are restricted or removed.

Go to Account > Security and change your password, then contact support during 09:00–23:00 WIB. Tell us the device used and any payment rail involved.