Reference

harta138 Privacy Policy for Your Account

Our harta138 Privacy Policy explains what we collect when you open an account, verify your phone, use the lobby or check wallet status through DANA, OVO, GoPay and…

Clear data purposesCookie choicesPhone verification contextRequest support path
harta138 harta138 Privacy Policy for Your Account
HELP WITH REQUESTS

Privacy Questions Through Your Account

A clear support path helps when you want to ask about personal data, a cookie setting or a phone check. Sign in, open the account support area and include the email or phone linked to your profile; we use that step to reduce mistaken disclosures. If a wallet receipt or status is part of your question, keep the DANA, OVO, GoPay or QRIS reference ready.

Team online

Account support

Use the support area after sign-in for a Privacy Policy question. We can first confirm your account details, then explain which data record or phone-verification event your request concerns.

Cashier reference

For a privacy question involving DANA, OVO, GoPay or QRIS, provide the payment reference rather than a wallet password. This lets us trace the relevant record without asking for secret credentials.

Access concerns

If account access stalls after phone verification, contact support from the account path and describe your device and time of attempt. We use those details to separate a security check from a data request.

DATA HANDLING

What We Do With Account Data

Privacy Policy choices matter most when they match the account steps you actually take. We limit internal access to records by operational need, protect sign-in activity with account checks and use transaction…

Account details

We use your contact and account details to create the profile, send account messages and connect support replies to the right record. Phone verification helps us confirm control before account access continues.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile your account activity. We do not need your wallet password to investigate a receipt or status question.

Device signals

Login time, browser or device signals can help identify unusual account activity. On mobile, these checks support the path from sign-in to the lobby without asking you to repeat private details unnecessarily.

Cookies and storage

Cookies can keep your session active, remember a selected setting and help us understand page errors. You can manage browser storage through your device settings, though some account functions may then need another sign-in.

Retention approach

We retain records only for the operational, security or legal purpose connected to them, then remove or anonymise them when that purpose ends where applicable. A support request can ask which period applies.

Change requests

To request access, correction or deletion of eligible personal data, contact support from your account path and identify the record involved. We may ask for phone confirmation before making any change.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions that commonly arise before you open an account or continue using the mobile path. They cover data collection, cookies, payment references, account security and how to contact us when a record needs attention.

It covers data connected with your account, phone verification, sign-in activity, device signals, cookies and payment references. It also explains how to request access, correction or deletion where applicable.

We use your phone number for account creation, contact and verification before account access. The check helps connect the request to you and reduce mistaken disclosure of private account details.

It covers the account-side references used to match DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity. Each payment provider may keep separate records under its own policy.

Sign in, open the account support area and ask for a copy of eligible personal data. Include your linked phone or email; we may verify ownership before responding.

Yes, you can request a correction through the support path when a profile detail is inaccurate. Tell us which field needs changing, and complete any phone confirmation needed for account security.

Cookies and browser storage can keep your session and selected settings available on mobile. If you clear them, the next visit may require another sign-in or renewed account checks.

Retention depends on why the record exists, such as account security, payment reconciliation or a legal requirement. You can ask support to explain the applicable period for a specific record.