Reference

Privacy Policy for Your panda 1001 Account

Your DANA, OVO, GoPay and QRIS activity is handled under the panda 1001 Privacy Policy, with clear account steps before any wallet action.

Indonesia accountsWallet data contextPhone verification
panda 1001 Privacy Policy for Your panda 1001 Account
HELP PATHS

Contact Us About Privacy Questions

A clear contact path helps when your Privacy Policy question concerns a wallet reference, phone check or account record.

Account route Use the support contact connected to your panda 1001 account for a Privacy Policy…
Wallet query For DANA, OVO, GoPay or QRIS records, share the transaction date, visible reference and…
Access request If you want a copy, correction or deletion assessment, state the request plainly and…
SIX CONTROLS

Six Controls Behind Our Privacy Policy

Privacy work is part of the account path rather than a separate promise. We limit collection to details needed for sign-in, phone verification, wallet matching, security and support…

Data handling

We collect account contact details, verification results, device signals and payment references for defined operating purposes.

Cookie choices

Cookies and similar browser records can help keep a session active, remember selected settings and identify unusual sign-in behaviour.

Account security

Phone verification supports account protection before sensitive account actions.

Retention

We retain account, security and payment-reference records only while they support service operation, dispute checks or legal duties.

Your requests

You can ask what account data we hold, request a correction, raise an objection or ask about deletion where local…

Policy contact

For a Privacy Policy request, use the account support route and describe the record or purpose in question.

Privacy Policy Questions Indonesian Accounts Ask

These Privacy Policy answers focus on the account details you are most likely to notice when using local wallets, a phone-verified login or a mobile browser. We keep the wording practical so you can decide what to ask before opening an account or contacting support. If your situation is not covered, send the specific account or payment reference through the available support route.

It covers account details, phone verification, login and device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security controls and how to request access or correction.

Phone verification helps us confirm that an account action comes from the person controlling the registered contact detail. It can support sign-in protection and requests involving account data. We do not ask you to send a phone password or wallet PIN to support.

No. Our Privacy Policy distinguishes payment references from wallet credentials. We may need a visible reference, date or status to match a DANA or QRIS event, but you should not send a wallet password, PIN or complete secret credential through support.

Yes, you can contact support with the registered phone or email and identify the field that appears wrong. We may request a verification step before changing it. Requests are assessed where local law permits, while some records may remain for security or legal duties.

We keep payment references for the period needed to match cashier events, investigate disputes, protect accounts or meet legal duties. The period can differ by record type. Once a reference no longer serves those purposes, it follows the applicable removal or restriction process.

Use the account support route and ask for an account-data copy, naming the contact detail and date range involved. We may need to confirm your identity before releasing anything, and the response can explain any information that cannot be shared for security or legal reasons.

Yes, the Privacy Policy applies when you sign in through a mobile browser or desktop path in a supported Indonesian region. Device and session signals may help protect access. Availability and eligibility depends on local law, including where local access is permitted.