Reference

data hk 2025 Privacy Policy Explained

Our Privacy Policy explains what data hk 2025 collects when you open an account, verify your phone and use wallet access through DANA, OVO, GoPay or QRIS.

Account dataPhone verificationWallet statusCookie choices
data hk 2025 data hk 2025 Privacy Policy Explained
ACCOUNT HELP

Where Privacy Questions Reach Us

A clear contact path matters when your personal data or wallet reference needs attention. Start from the account help area and choose the support route shown there; include the phone number linked…

Account data request Use the account help path to ask what personal details are connected with your account. We may ask you to complete phone verification before discussing account-specific data, so a request is not answered to the wrong person.
Wallet reference check For DANA, OVO, GoPay or QRIS questions, send the payment reference and approximate time shown in your record. We use those details to check status without requesting your wallet PIN or full login credentials.
Policy change request If a detail is wrong or you want a permitted correction, contact us through the account support route. State the field to change and keep your phone available because an identity check may be required before we act.
SECURITY PRACTICE

Six Practical Data Handling Commitments

Our Privacy Policy is applied through ordinary account steps rather than vague promises. We separate sign-in checks from wallet status work, keep support requests tied to the relevant account and use device…

What we collect

We may collect your account contact details, phone verification result, sign-in events, device or browser signals and payment references. For DANA, OVO, GoPay and QRIS, the record helps connect a wallet status to the correct account without requesting a wallet password.

Why we use it

We use account data to provide access, complete phone checks, investigate sign-in issues, match payment status and answer support requests. We do not use a payment reference as a substitute for your account verification when a request concerns personal details.

Cookie control

Cookies can keep a mobile-browser session available and help us detect unusual sign-in behaviour. If you clear cookies or site storage, you may need to sign in again and repeat the phone verification step before account details are shown.

Account protection

We may ask for phone verification before discussing account data or changing a linked detail. Do not send passwords, wallet PINs or one-time codes through support. If access looks unusual, we may pause the request until the account check is complete.

Retention approach

We keep personal data only for the account, security, support and legal purposes that require it. When a record is no longer needed for those purposes, our handling process removes it or separates it from direct account identification where appropriate.

Your correction path

To request a correction, use the account support route and identify the data field that needs attention. We may ask for the phone verification step again, then confirm the outcome through the contact detail already connected to your account.

Privacy Policy Questions Indonesian Accounts Ask

These Privacy Policy answers focus on the account and payment records you are most likely to ask about before opening an account. We explain the practical path for data access, corrections, cookies, phone checks and wallet references. If your situation involves local eligibility, access depends on local law, and the account support route can clarify which request path applies.

It covers details connected with your account, including contact information, phone verification, sign-in events, browser or device signals, cookies and payment references. It explains how we use those records for account access, security checks, wallet status work, support and policy administration.

DANA and QRIS references can help us match a payment status with the correct account when you ask for assistance. We may also handle OVO, GoPay, bank transfer or virtual account references, but we do not need your wallet PIN to investigate a status.

Open the account help area and submit a personal-data request through the support route shown there. Include the phone number linked to your account and a clear request. We may require phone verification before releasing account-specific details to you.

Yes. Use the account support route, name the field that is inaccurate and explain the correction needed. We may repeat the phone verification step before changing it, then use the existing account contact detail to confirm that the request was processed.

Cookies can keep your sign-in session available and help identify unusual access. If you clear cookies or browser storage, the account may ask you to sign in again and complete phone verification. Your browser settings control whether cookies are retained on that device.

We retain records for the account, security, support and legal purposes that apply to them. The period can differ by record type and purpose. When retention is no longer needed, we remove the record or separate it from direct account identification where appropriate.

Yes. Access and eligibility depends on local law, and some requests may require an additional account check before we respond. Where local law permits, use the support path shown in your account and provide the relevant reference without sending passwords or wallet PINs.