Reference

panda89 Privacy Policy For Your Account

panda89 Privacy Policy explains how we handle the details linked to your account, including phone verification, wallet records and device access.

Clear data purposesWallet record contextCookie choicesContact path
panda89 panda89 Privacy Policy For Your Account
CONTACT YOUR WAY

Get Privacy Policy Help Beside Your Account

A clear contact route matters when you want to understand a record or correct an account detail. We keep privacy questions separate from general lobby browsing, so you can identify the request and include the phone number connected to your account. Our team may ask for a transaction reference or verification detail before discussing personal data. That step helps us avoid sharing account information with the wrong person, including when a DANA receipt or QRIS status is part of the question.

Team online

Account contact route

Open the contact path from your account area and state that your request concerns the Privacy Policy. Include your registered phone number, the subject of your request and any relevant date. We use those details to locate the correct record without asking you to send a full wallet password.

Payment record questions

If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, share the transaction reference rather than private wallet credentials. We can explain which payment record is linked to your account and why a verification step may be needed before disclosure.

Access and correction

Tell us whether you want to access, correct or remove information held for your account. We check account ownership first, then assess the request under local requirements. If a record must remain for a stated legal or security reason, we explain that point in our reply.

OUR DATA PRACTICE

What Your Privacy Policy Covers In Practice

We apply the Privacy Policy to the account journey rather than treating privacy as a separate page with no operational meaning.

Account details

We may hold your phone number, account identifiers, verification result and messages sent through the account contact route. These details let us confirm which account is involved when you ask about access, a correction or a Privacy Policy request.

Device and login signals

When you move from a mobile login to the lobby, we may record device and session signals such as access time, browser context or failed attempts. We use these signals to protect account access and examine unusual activity, not to request your device contents.

Cookies and storage

Cookies or similar browser storage can keep a session active, remember a selected setting or help us understand whether a page loads correctly. You can clear or restrict them in your browser, although some account functions may then require another login.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can show that a payment event belongs to your account. We use the reference for matching, status checks and support, while wallet credentials remain with the payment service.

Security controls

We may compare phone verification, login activity and device signals before discussing account data or changing a sensitive detail. This additional check can take place when you contact us about Live Roulette access, a wallet status or an unfamiliar login.

Retention and requests

We keep records for the period needed for the stated account, security, payment or legal purpose, then assess whether they can be removed. You can contact us to ask what we hold, request a correction or ask how retention applies to your case.

Privacy Policy Answers For panda89 Accounts

These Privacy Policy answers address the account and payment questions you may have before opening access. We keep the wording practical: what we collect, how we use it, what happens on a mobile device and how you can contact us. The same account contact route can be used for a data request, a correction or a question about retention.

It covers information connected with your account, including phone verification, login and device signals, support messages, cookies and payment references. It also explains why we use those details for access, security, transaction matching and support, plus how you can request access or correction.

We use your phone number to create and identify your account, complete the clear phone verification step before access and help confirm ownership during support. We do not treat your phone number as permission to use unrelated personal data or share it for an unrelated purpose.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account matching. These references help us confirm status and answer support questions; they are not your wallet password or private payment credentials.

On mobile, we may process session, browser and device signals needed to keep your login active and identify unusual access. We do not request your device contents. Browser cookie controls remain available to you, though restricting storage can require another login before opening the lobby.

Use the account contact route and say that your request concerns the Privacy Policy. Include your registered phone number, the detail you believe is wrong and any helpful transaction reference. We verify ownership before changing records, and we explain if a record must remain for security or legal reasons.

We keep information only while it serves the stated account, security, payment, support or legal purpose. Retention can differ by record type. You can ask us what applies to your case, whether a record can be removed and why a particular detail still needs to remain.

Yes, you can contact us with an access, correction or deletion question. Any account access or eligibility depends on local law. We assess your request under the rules that apply to your location and explain the available path rather than promising a result that local requirements do not allow.