Reference

Privacy Policy For Your panda99 Account

Our Privacy Policy explains how we collect, use and protect the details connected with your panda99 account, from phone verification to wallet records.

Clear data purposesWallet record controlsAccount access stepsCookie choices
panda99 Privacy Policy For Your panda99 Account
POLICY HELP PATH

Get Privacy Policy Help Through Support

A direct support request gives you a practical route when a Privacy Policy question concerns your own account.

Account request Use the support path linked with your account when you want to ask how we handle a phone number, sign-in record or verification detail. Include the account identifier we request, but keep your password, PIN and full wallet credentials private while we check the case.
Payment record For a DANA, OVO, GoPay or QRIS query, share the transaction reference and approximate date rather than a screenshot showing unnecessary personal details. We use the reference to compare the payment status with the account record and explain what data was used.
Policy change If you believe an account detail is inaccurate, ask us to review it through support and state the change clearly. We may need to verify that you control the account before changing a phone detail, access record or contact preference.
SIX DATA CHECKS

Six Ways We Handle Your Data

Our Privacy Policy is applied through ordinary account controls rather than vague promises. We separate the data needed for sign-in from payment references, limit support checks to the case you raise and…

Account setup

When you open an account, we use the details needed to create your profile and complete the clear phone verification step before account access. This lets us connect your sign-in activity with the correct account instead of asking you to repeat the same details at every visit.

Payment records

A DANA, OVO, GoPay or QRIS payment can create a reference, amount and status record beside your account activity. Bank transfer and virtual account records may be handled in the same way so support can trace a receipt without requesting your wallet password.

Cookies

Cookies can keep your session available while you move from the account page to the lobby on a phone or desktop. Device data may also show whether a page or payment status loaded correctly. Your browser settings provide a separate way to manage cookies.

Account security

We use sign-in and phone verification details to help identify account access and investigate unusual activity. Never send your password, PIN or one-time code in a support request. If your phone path changes, contact us through the account route before asking for an access adjustment.

Data retention

We retain account, support and transaction records for as long as they are needed for the purpose described in this Privacy Policy, account security or a legal requirement. A request to remove data may be limited where a record must remain available for those reasons.

Your request

To ask about access, correction or deletion of account data where local law permits, contact support with a clear description of the request. We may verify account control first, then explain the available action, any required record, and the expected next step.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account questions you are most likely to have before opening panda99. They cover what we collect, how wallet records work, how cookies affect a mobile session and how to request a change. If your case involves a specific receipt or access problem, use the support path with the smallest necessary set of account details.

The panda99 Privacy Policy covers data connected with account creation, phone verification, sign-in, support requests, cookies and payment records. It explains why we use each type of detail, how we protect account access and how you can ask about correction or deletion where local law permits.

We collect the account details needed to create your profile and complete phone verification before access. We can also receive sign-in activity, device or cookie signals, support messages and transaction references. We do not need your wallet password or PIN for a payment-status check.

When you use DANA or QRIS, the related payment reference, status and account connection may be retained so we can match a receipt and investigate a stalled status. Share only the reference requested by support. Wallet passwords, PINs and one-time codes should remain private.

Where local law permits, you can ask us what account data we hold through the support path. We may first verify that you control the account, then explain the available data and any limits caused by security, transaction records or a legal retention requirement.

Cookies can keep your session active as you move from sign-in to the lobby on a mobile browser. Device signals may help us identify a page-loading or status issue. You can manage cookies through your browser settings, although changing them may affect account access.

Send support a clear correction request describing the account detail that appears wrong, such as a phone number or contact preference. We may verify account control before making a change. Payment references can require a separate check because they document a transaction status.

Where local law permits, you can ask us to remove data that is no longer needed for its stated purpose. We may retain some account, support or payment records for security, dispute handling or a legal requirement, and support will explain the applicable reason.