Reference

Open harta11 Privacy Policy With Clarity

harta11 Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessPolicy requests
Browse the lobby Read FAQ
harta11 Open harta11 Privacy Policy With Clarity
REQUEST PATHS

Use Account Help For Privacy Requests

A clear request path helps you ask about your account data without explaining the same issue repeatedly. Start from the support route connected to your account and include the phone number or payment reference that needs attention. We use those details to locate the correct record, while access still depends on local law and reasonable identity checks.

Team online

Account access

If you cannot enter your account, use the account support route and identify the phone number attached to it. We may ask for an account step or device detail before discussing personal data, so another person cannot obtain your records.

Wallet status

For a DANA, OVO, GoPay or QRIS privacy question, share the payment reference rather than a wallet password or security code. We can check the matching account record and explain what data is retained for the transaction.

Policy changes

When you ask about a change, deletion or copy of your data, send the request through the account support path. We will confirm the request scope, apply identity checks where needed, and explain any legal reason a record must remain.

HANDLING DETAILS

Browse How harta11 Handles Your Data

Privacy depends on small operational choices, so we describe the account, wallet and device steps behind this policy.

Account records

When you open an account, we store the details needed to create and maintain access, including your phone number and verification result. Login events help us identify the correct account when you request a copy, correction or access change.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount status and account match. We use those fields to reconcile the cashier record, but we do not ask you to share a wallet PIN or one-time security code.

Device signals

A mobile browser or desktop session may provide device type, browser details, approximate network data and login time. These signals help us detect an unusual sign-in and protect your account; they are not used as a public identity label.

Cookie choices

Cookies and similar storage can keep a session active, remember a language or help us understand a sign-in error. You can manage browser storage through your device settings, although removing it may require you to verify your account again.

Retention period

We keep personal data only for the period needed for account operation, payment reconciliation, security checks, dispute handling and legal duties. If you request removal, we explain which records can be deleted and which must remain for a stated reason.

Change requests

To correct or ask about your data, use the support route inside your account and describe the specific field or record. We may confirm your phone verification before responding, then explain the action taken or the reason a restriction applies.

Check Privacy Policy Questions Before Opening

These Privacy Policy answers address the account steps Indonesian customers usually need before opening access. We explain what happens to payment references, mobile session data, cookies and requests for copies or corrections. If a question concerns eligibility or access, the answer remains subject to local rules and the exact wording where local law permits.

The harta11 Privacy Policy covers data used for account creation, phone verification, login security, wallet matching, device sessions, support messages, cookies and legal recordkeeping. It also explains how you can request access, correction or deletion, subject to identity checks and local law.

Yes. Privacy Policy applies to DANA, OVO, GoPay and QRIS references connected with your account. We use the reference and status to match a cashier event, while wallet passwords, PINs and one-time security codes should never be sent to support.

We may collect the phone number and account details you submit, your phone verification result, login time, device type, browser details and security signals. We use these records to provide access, identify your account and respond to a data request.

Use the support route connected to your account and name the exact record you want copied or corrected. Include the relevant phone number or payment reference, but never include a wallet PIN. We may verify your account before processing the request.

Payment and login records help us match deposits or withdrawals to the right account, investigate a disputed status, identify unusual access and meet legal duties. Retention varies by record and purpose, and we explain any continuing requirement when you ask.

Yes. Your mobile browser settings let you clear or restrict cookies and similar storage. This may sign you out, remove a saved preference or require phone verification again. The Privacy Policy explains why session storage supports account access and security checks.

Use the support path inside your account and state whether your request concerns access, correction, deletion, cookies or a payment reference. We will identify the relevant record, apply a reasonable account check and explain the available action where local law permits.

Related Pages

harta11 Indonesia Account information About Us harta11 Casino Access guide