Reference

harta111 Privacy Policy for Indonesian Accounts

The harta111 Privacy Policy explains what we collect when you open an account, use the mobile lobby, or check DANA, OVO, GoPay and QRIS status.

Account clarityWallet recordsCookie choicesContact access
harta111 harta111 Privacy Policy for Indonesian Accounts
CONTACT ROUTES

Get Policy Help Beside Your Account

A clear contact route matters when a Privacy Policy question concerns your account rather than a general query.

Account access If login stalls before you can open the policy page, use the account support path and identify the contact detail attached to your harta111 account. We may ask for an account step that confirms ownership, but we will not ask you to disclose a password or wallet PIN.
Wallet records For a DANA, OVO, GoPay or QRIS record, send the payment reference, approximate date and account contact detail through support. This lets us locate the relevant transaction record while limiting the personal data included in your request.
Policy requests You can ask us to explain, correct or remove personal data covered by the Privacy Policy. State exactly what you want changed and include enough account detail for verification. We will assess the request under applicable local law before taking action.
DATA PRACTICE

How We Handle Your Privacy Choices

We keep our Privacy Policy practical by linking each data use to an account action you can recognise: opening access, checking a wallet status, protecting a session or answering support.

Account details

When you open an account, we collect the details needed to create and maintain access, including your contact route and verification responses. We use these details for sign-in checks and account correspondence, not as a reason to request unrelated personal material.

Payment references

A wallet or bank record can contain a reference, amount status and processing time. We use the reference to reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet PIN to check a receipt.

Device signals

Signing in from a mobile browser or desktop can create technical signals such as session details, browser type and security events. We use these signals to protect account access and investigate unusual sign-in behaviour, while keeping the purpose tied to security.

Cookies

Cookies can keep a session active, remember a language or device preference and help us understand whether a page loads correctly. You can manage cookies through your browser settings, although changing them may require another sign-in or limit some policy-page functions.

Retention steps

We keep personal data for the period needed to operate an account, address a support request, protect access or meet a legal duty that applies where local law permits. When a retention reason ends, we remove, restrict or separate the data as appropriate.

Change requests

To request a copy, correction, restriction or removal, contact support with the account contact detail and a precise request. We may verify ownership before changing records, because changing the wrong account would create a security problem for you.

Privacy Policy Answers for harta111

These Privacy Policy answers focus on the account, device and payment questions you may have before opening access. They explain what to send, how verification works and when local law affects a request. If your situation is not covered, use the account support path and describe the specific record or action you want us to check.

The harta111 Privacy Policy covers account details, verification responses, device and session signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains security use, retention and requests to change or access your data.

We collect the contact and verification details needed to create account access and respond to you. Technical sign-in data may also be recorded when you use a phone or desktop. We ask you to provide only the details required for the account step you are completing.

Yes. The policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account activity. These records help us match a receipt to the correct account. Never send a wallet PIN or full secret credential.

Use the account support path and state whether you want access to a record or a correction. Include the contact detail linked to your account and describe the exact item. We may verify ownership first, then assess the request under applicable local law.

Cookies may keep your session active, remember a browser preference and help us identify loading problems. A mobile browser can store a different cookie record from your desktop. You can adjust browser cookie settings, but doing so may require another sign-in.

We retain data while it is needed for account access, security checks, support handling or a legal duty that applies where local law permits. The period can differ by record type. When the reason ends, we remove, restrict or separate the data as appropriate.

Yes. Sign in and use the account support route where possible. If login is unavailable, provide the account contact detail and a short description without sending a password or wallet PIN. We can then direct the Privacy Policy concern to the appropriate handling path.