Reference

paito hk 4d Privacy Policy for Indonesia

The paito hk 4d Privacy Policy explains what we collect when you open an account, sign in on mobile, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessCookie choices
paito hk 4d paito hk 4d Privacy Policy for Indonesia
CONTACT PATHS

Privacy Help Beside Your Account Path

A direct support route helps you raise a privacy question without sending sensitive details through an unrelated channel.

Account support chat Use the support chat from your signed-in account when you need to ask about…
Wallet reference check For a DANA, OVO, GoPay or QRIS question, share the transaction reference rather than…
Correction request If your contact detail or account record needs a change, tell us which field…
HANDLING DETAILS

What We Do With Your Account Data

We keep this Privacy Policy practical by connecting each data use to a visible account action.

Account creation

When you open an account, we collect the contact details and verification result needed to create and protect that account.

Phone verification

A phone verification step confirms that an access request relates to your account.

Device signals

Your browser or mobile device can send practical signals such as session activity, screen type and sign-in timing.

Cookie controls

Cookies can keep a signed-in session working, remember a language choice or help us understand page errors.

Retention choices

We assess retention by purpose: account security, payment reference matching, support history or a legal requirement.

Your request route

You can ask what personal data we hold, request a correction, or ask about deletion through support chat.

Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the account actions you are most likely to search for before opening access from Indonesia. We explain the data connected with phone verification, mobile sessions, cookies, wallet references and support requests in plain terms. If your situation involves a legal restriction or an account record we cannot identify, contact support chat and use the same account detail attached to your request.

It covers account contact details, phone verification status, sign-in and device signals, cookie activity, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains your routes for access, correction and deletion where local law permits.

Phone verification helps us connect an account access request with the correct account and investigate unusual sign-ins. We retain the verification status and relevant event record for security and support; never send your verification code, password or wallet PIN in a message.

Yes. The Privacy Policy covers practical device and browser signals linked to a session, such as screen type, session activity and sign-in timing. We use them to protect account access and diagnose page issues, not to read unrelated files, photos or contacts on your device.

We may store the payment reference, amount status and account link needed to reconcile a DANA, OVO, GoPay or QRIS action. For bank transfer and virtual account steps, the matching reference may also be retained. We do not ask for your wallet password.

Open the account support chat and state whether you want access to your stored data or a correction. Include the account email or phone detail and describe the field clearly. We verify your identity first, then respond according to the Privacy Policy and local law.

Retention depends on the record's purpose, such as account security, payment reference matching, support history or a legal requirement. We remove or separate identifying details when the applicable period ends where local law permits. Support can explain why a particular record remains.

Yes. You can ask about cookie use through our support contact path without sharing a password or wallet credential. Browser controls can also remove session cookies, but doing so may sign you out and require phone verification again when you return to account access.