Reference

harta 11 Privacy Policy For Your Account

harta 11 keeps this Privacy Policy focused on the data behind your account, mobile access and wallet activity, including DANA, OVO, GoPay and QRIS records.

Account clarityWallet dataMobile accessContact path
harta 11 harta 11 Privacy Policy For Your Account
CONTACT ROUTE

Get Help With Privacy Requests

A clear contact path helps you ask about the Privacy Policy without sharing more than needed.

Account access Use the account help route when you need to ask which contact details are…
Wallet records For a Privacy Policy question about DANA, OVO, GoPay or QRIS activity, send the…
Data changes Ask us to correct account data, clarify retention or explain a cookie setting through…
SECURITY PRACTICE

How We Handle Your Personal Data

The Privacy Policy is supported by practical controls rather than broad promises. We separate account details from routine browsing signals, limit access to records needed for account and…

Account records

We use the details supplied during account creation to maintain your profile, confirm requested changes and connect support replies to…

Payment references

A DANA, OVO, GoPay or QRIS reference can help us reconcile a wallet status with your account.

Cookies and device use

Cookies may retain necessary session settings, while device and browser signals help identify repeated sign-in patterns.

Account security

We record sign-in events, failed access attempts and session changes so that unusual activity can be checked.

Retention choices

We retain personal data only for the period needed for account operation, payment checking, security review and legal duties that…

Policy updates

When our data practices change, we place the revised Privacy Policy on this page and update its wording before the…

Privacy Policy Questions From Indonesia

These answers address the Privacy Policy points most relevant when you open or maintain an harta 11 account from Indonesia. They cover account creation, mobile access, wallet references, cookies, retention and requests to change or receive your data. If your situation is unusual, use the account contact route and mention whether your question concerns login, payment status or a personal-data request.

It covers account details, phone verification records, device and browser signals, session events, cookie settings and payment references connected with DANA, OVO, GoPay or QRIS. We use these records for access, security, payment checking and support where local law permits.

Device and browser signals help us recognise normal sign-in patterns, detect unusual session changes and protect your account. They can also keep necessary settings available when you move from phone login to the mobile lobby. You can manage cookies through your browser.

Yes. The Privacy Policy includes payment references linked to your account, including DANA and QRIS, as well as OVO and GoPay status details. We use those references to check a wallet event without asking you to share passwords or full security codes.

Use the account contact route and describe the correction clearly. Write from the contact detail attached to your profile where possible, include the relevant account identifier and avoid sending passwords. We may complete phone verification before changing account-linked data.

Retention depends on why the data was collected. Account operation, security checks, payment reconciliation and legal duties can require different periods. The Privacy Policy lets you ask for the reason behind a retention period, subject to duties that apply where local law permits.

You can contact us to ask what account, device, cookie or wallet-reference data is associated with your profile. Include enough detail for ownership checking, and use the secure account route. We may limit a response where disclosure would affect security or legal duties.

Contact support with the account identifier, the affected date and a masked DANA, OVO, GoPay or QRIS reference if relevant. Do not send your password or full security code. We will check the account record and explain the next step under this Privacy Policy.