Reference

panda138 Privacy Policy For Your Account

panda138 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsDevice awarenessContact options
panda138 panda138 Privacy Policy For Your Account
CONTACT ROUTES

Ask About Privacy Near Your Account

A clear contact path helps when you want to understand a Privacy Policy choice or check a wallet record. We ask you to contact us from the account connected to the request where possible, because that lets us confirm who is asking without exposing personal data to the wrong person. Include the relevant date, payment rail, and request type, but do not send a full password or one-time code. We can then explain the next account step and any local-law condition.

Team online

Account privacy request

Use the support route beside your account area to ask for a copy, correction, or deletion review. We may request a phone verification step before discussing personal data, especially when the request concerns sign-in details.

Wallet record query

For DANA, OVO, GoPay, or QRIS records, provide the payment date and visible reference rather than private wallet credentials. We use that context to locate the correct account event and explain its privacy treatment.

Receipt and status help

If a bank transfer or virtual account receipt appears beside the wrong account status, contact support through the cashier-linked path. We can check the record connection while keeping your password and verification code private.

Access concern

When sign-in or policy access stalls on your phone, tell us the device type and the time of the attempt. We use those details to investigate access without asking you to share private account credentials.

HANDLING DETAILS

What Our Privacy Process Covers

Privacy Policy decisions affect your account from the first phone verification through later wallet checks. We separate the purpose of each record: account security, payment matching, service communication, or legal handling.

Account data

We use your account details to create access, complete the clear phone verification step, and respond to requests connected with your account. We do not need your password in a support message, and you should never include a one-time code.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference helps us match a payment event to the right account. We use the reference for status checks and record handling, not as a reason to request wallet credentials.

Cookies and devices

Cookies can keep a session working and help us recognise unusual sign-in behaviour. Your phone and desktop may produce different device signals, so review browser settings and sign out on shared equipment after using your account.

Account security

We may compare sign-in time, device context, and phone verification before releasing account details through support. This extra check helps prevent a stranger from receiving personal data when a request comes from an unfamiliar device.

Retention choices

We keep records only for the period needed for account security, payment disputes, service duties, or legal requirements. When a record no longer has a valid purpose, we remove it or separate it from direct account details.

Change requests

You can ask whether your personal data is accurate, request a copy, or ask about deletion and restricted use. We verify the requester first, explain any local-law limit, and tell you what account step follows.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions you may have before opening access. We keep the wording practical: what is collected, how device activity is used, how payment references are handled, and how you can contact us. If your request involves another person’s account or a legal restriction, we may need more detail before responding. Account access remains subject to local law.

The panda138 Privacy Policy covers account details, phone verification, device signals, cookies, support requests, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It explains why we use each category, how long records may remain, and how you can request a change.

Phone verification helps us confirm that the person opening or accessing an account is connected to the submitted details. We may also use it before discussing a Privacy Policy request through support. Never send your password or one-time code in a message.

Yes. The Privacy Policy covers the reference and status details needed to connect DANA or QRIS activity with your account request. We do not need your wallet password. For a correction, provide the date and visible reference so we can locate the right record.

We use device and browser signals to keep a session working, recognise unusual sign-in patterns, and investigate an access concern. A phone and desktop can produce different signals. If you use a shared device, sign out and avoid saving account credentials after your session.

You can contact us through the account support path and ask for a copy or correction of eligible personal data. We first verify the request, then explain the available account step and any restriction that depends on local law before handling it.

We retain records for the period needed for account security, payment matching, dispute handling, service duties, or legal requirements. After that purpose ends, we remove the record or separate it from direct account details where local law permits.

Yes, you can ask whether deletion or restricted use is available for a particular record. Send the request from the connected account where possible and identify the record without sharing credentials. We will verify you, explain any legal limit, and confirm the next step.