Reference

Privacy Policy for Your panda101 Account

Clear records for DANA, OVO, GoPay and QRIS start with a Privacy Policy you can actually follow.

Account clarityWallet contextMobile access
panda101 Privacy Policy for Your panda101 Account
HELP WITH PRIVACY

Where Your Policy Questions Go

A direct support path matters when you want to ask about a stored detail, a wallet reference or an account access record. We keep privacy requests tied to the account step that created the data, so you can explain whether your question concerns phone verification, a QRIS receipt, a device sign-in or a payment status. Use the support route shown in your account area and include only the details needed to locate the matter. Access remains subject to local law and our team can explain the next step.

Team online

Account privacy request

Ask us to locate the personal details connected with your panda101 account. Include your registered contact detail and the request type, such as access, correction or deletion, rather than sending a full wallet password or security code.

Wallet record query

For DANA, OVO, GoPay or QRIS questions, share the payment reference and approximate date through the account support path. We use that narrow detail to check a receipt or status without requesting unnecessary wallet credentials.

Device access concern

If a mobile or desktop sign-in looks unfamiliar, contact us through account help and describe the device path. We can review the access record, help secure the account and explain which policy data supports that check.

DATA HANDLING DETAIL

What Our Privacy Process Covers

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

Account creation

When you open an account, we handle the contact and verification details needed to establish access.

Payment references

A DANA, OVO, GoPay or QRIS reference can show that a cashier event belongs to your account.

Cookies and sessions

Browser cookies or similar storage may keep a session active, remember a technical choice or help us diagnose an access…

Device security

Sign-in details such as device type, browser signals and access time can help us assess an unfamiliar session.

Retention approach

We retain records for the period needed to operate the account, resolve payment or access disputes, and meet applicable legal…

Changes and contact

You can ask about the data connected with your account, request a correction, or raise a concern through the account…

Answers About panda101 Privacy Policy

These common Privacy Policy questions focus on the account and payment records you are most likely to encounter in Indonesia. We explain the practical route for checking data, changing an incorrect detail and raising a concern about device access. If your situation involves eligibility, remember that access depends on local law and is available only where local law permits.

The panda101 Privacy Policy covers account details, phone verification, device and browser records, cookies, payment references and support requests. It explains why we use each category, how retention works, and how you can ask about access, correction or removal.

Phone verification helps connect your account access with the contact detail you provide and supports account security checks. We may use the verification record when you ask support to locate account data or investigate an unfamiliar sign-in.

Yes. The Privacy Policy covers payment references linked to DANA, OVO, GoPay and QRIS activity. We use those references to check a receipt or cashier status, while you should never send a wallet password or security code to support.

Use the account support path and clearly request access to the personal details connected with your account. Include your registered contact detail and the record you want checked. We may verify account ownership before sharing account-specific information.

You can request a correction or ask whether a record can be removed through account support. Explain the detail and the reason for your request. Removal may be restricted when the record is needed for legal, security, payment or dispute purposes.

Cookies and similar browser storage may support session continuity, remember technical choices or help diagnose access issues. You can clear or manage them through your browser settings, but doing so may sign you out or require another account verification step.

Contact account support and describe the device type, approximate access time and sign-in route. Do not share a password or one-time security code. We can review the available access record, help secure the account and explain the relevant policy use.