Reference

Privacy Policy For Your harta328 Account

Our harta328 Privacy Policy explains how we handle the details connected with your account, phone verification, device access and wallet activity.

Account clarityWallet data careDevice access choicesDirect policy support
harta328 Privacy Policy For Your harta328 Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route helps when a privacy question appears beside a login or wallet status issue.

Account request Use the account support route to ask for a copy, correction or removal request involving your profile, phone verification record or login history. Include the account phone number so we can match the request safely.
Wallet receipt When your question concerns DANA, OVO, GoPay or QRIS, attach the payment reference rather than private wallet credentials. We use that reference to check the relevant status record and explain which data was used.
Access concern If a device or login event looks unfamiliar, contact support through the account path and mention the date, device type and affected session. We can guide security checks without requesting your wallet password.
DATA PRACTICE

Six Practical Privacy Commitments

Our handling process follows the account steps you can see: phone verification before access, payment reference checks at the cashier path and device records when a login is made.

Collection

We collect account details, phone verification results, login events and payment references when those records are needed for access, wallet status checks, security review or a request you send to our team.

Cookies

Cookies and device signals help keep your session connected while you move from login to the lobby. You can manage browser permissions, though changing them may affect saved access and session functions.

Account security

Phone verification and session checks help us distinguish your account activity from an unfamiliar device. Never share a password, wallet PIN or one-time security code through a support request.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use references and status details to match a transaction. We do not need your private wallet password to investigate a receipt.

Retention

We retain records only for the account, payment reconciliation, security checks or legal duties that require them. You can ask what category is held and why it remains connected with your account.

Changes and contact

To request access, correction or deletion, send the account phone number and a clear description through support. We may ask for an account check before changing records linked to your identity.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the searches we hear most often before account access: what we collect, why wallet references appear, how device records work and how you can request a change. If your question concerns eligibility, access depends on local law. For a record-specific answer, contact us with your account phone number and the relevant reference.

You can read the Privacy Policy on this page before opening an account. It explains account details, phone verification, device signals, cookies, wallet references, retention and the steps for requesting access, correction or deletion.

The policy covers details such as your name, phone number, verification result, login activity, device identifiers and payment references. We use only the records needed for account access, security, payment matching or support.

We do not ask for or need your private wallet password. For DANA, OVO and GoPay questions, we use a transaction reference or status detail, and you should never send a wallet PIN through support.

A QRIS payment can create a reference, amount status and related account event for matching and support. The policy explains why those records are used, while the payment provider may apply separate privacy terms.

Yes. Send a request through the account support path with your account phone number and the record you want checked. We may complete an identity check before providing a copy or changing account-linked details.

Retention depends on the purpose of each record, such as account access, payment reconciliation, security or legal duties. You can ask which category remains stored and why it is still connected with your account.

Yes. Tell support the device type, date and session concerned. We can explain the relevant cookie or login record and guide a security check. Access and any related action depends on local law.