Reference

Open ketua naga Privacy Policy Clearly

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

Account dataWallet referencesCookie choicesAccess requests
ketua naga Open ketua naga Privacy Policy Clearly
REQUEST HELP

Ask About Privacy From Your Account

A clear contact path helps you act on the Privacy Policy without guessing which team to reach.

Account access Use the support path attached to your account when you need to ask how…
Wallet reference For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account…
Policy request Ask us to access, correct or explain personal data through the available contact route…
DATA PRACTICES

Explore How We Handle Your Data

We keep our Privacy Policy practical by linking each data use to an account action you can recognise.

Registration details

When you create an account, we use the phone or contact details you submit to complete the account path and…

Device signals

A mobile browser or desktop session can create technical details such as device type, browser settings and sign-in timing.

Cookie controls

Cookies can keep a session available while you move from login to the lobby and can remember selected page settings.

Payment matching

A DANA, OVO, GoPay or QRIS receipt may create a reference used to check account status.

Retention choices

We keep personal data for the period needed to provide account access, investigate security events, resolve a payment-status question or…

Your request

You can contact us to ask for a copy, correction, explanation or other change permitted by applicable rules.

Browse Answers About Privacy Policy

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. We keep the wording tied to real steps, including phone verification, mobile sign-in, cookie controls and receipt checks for Indonesian wallets. If your situation is not covered, contact us through the account support route with the smallest useful amount of personal detail. Requests and access remain subject to local law.

It covers details you provide during account creation, phone verification records, device and session data, cookies, payment references and privacy contacts. It explains why we use each category for account access, security, status checks or legal duties, with availability depending on local law.

We use phone verification to confirm the account path before access and to connect account-related requests with the right record. If you ask us to correct or explain that data, we may verify account ownership before discussing it.

Yes. The Privacy Policy covers payment references created when you use DANA, OVO, GoPay or QRIS, along with bank transfer and virtual account status records. We use the reference needed to match a receipt or account status, not your wallet PIN.

Use the account support contact route and state that your request concerns the Privacy Policy. Provide the account phone or contact detail and name the records you want, such as registration data, cookies or payment references. We may verify ownership first.

You can ask us to correct inaccurate account information through the available support route. Describe the field and the requested change without sending a password or security code. We review the request against the account record and applicable local requirements.

Cookies can help keep your mobile browser session connected while you move from login to the lobby and can remember selected settings. You can restrict or remove them in your browser. Some account continuity features may work differently after that change.

You can contact us to ask whether a particular record can be deleted under the Privacy Policy. We assess the request by data type and purpose. Some records may need to remain for account security, payment-status checks or applicable legal duties.