Reference

pandapetir88 Privacy Policy: Your Data Path

Your phone verification, wallet status and lobby activity follow a clear data path under the pandapetir88 Privacy Policy.

Clear collection purposesWallet data boundariesRequest support pathCookie choices
pandapetir88 pandapetir88 Privacy Policy: Your Data Path
REQUEST SUPPORT

Privacy Help From Account Support

A privacy question should not require guesswork. We give you a direct route through the account support area for access requests, correction requests and questions about…

Access request Ask for the account data linked to your verified phone number through the account…
Correction request If your contact detail or account record is inaccurate, tell us which field needs…
Wallet query For DANA, OVO, GoPay, QRIS or bank transfer questions, share the transaction reference and…
SIX DATA CONTROLS

Six Controls Behind Our Privacy Policy

We apply the Privacy Policy at each point where your account creates a record: phone verification, sign-in, lobby access, wallet status and support contact.

Account details

We collect details needed to create and maintain your account, such as your phone number and verification result. We use them for access checks, account notices and requests tied to your own record.

Device records

When you sign in, we may record device type, browser details, approximate network location and session times. These signals help identify unusual access without reading unrelated files on your phone.

Cookie controls

Cookies can keep a session active and remember selected settings. You can clear them in your browser settings, although doing so may require phone verification again before account access.

Payment separation

DANA, OVO, GoPay, QRIS, bank transfer and virtual account checks create status records for reconciliation. We use references and outcomes, not wallet passwords, when checking a payment.

Retention choices

We retain records for account operation, dispute handling or legal duties, then delete or restrict them when the relevant need ends. A retention question can be sent through account support.

Withdrawal checks

A withdrawal may require matching account and payment details before processing. We use the check to reduce misuse, and we explain a requested clarification through the account support route.

Privacy Policy Questions Before Account Access

The questions below address the points we hear before an account is opened or a wallet is connected. Each answer stays focused on personal data, account verification and the ways you can contact us. If your situation is not listed, use the account support path and describe the specific record or transaction reference involved.

It covers account details, phone verification, device and session records, cookies, payment references, support requests and retention. It applies when you access our pages or account areas where local law permits.

We use phone verification to connect access with the correct account and reduce mistaken or unauthorised entry. The verification result can also help us confirm an access or correction request.

No. Our payment records are limited to details such as a reference, amount, status and time for reconciliation. Wallet credentials remain outside our policy records and should never be sent to support.

We may record device type, browser details, approximate network location and session time. These records help identify unusual access and maintain a working session without examining unrelated phone content.

Use the account support path and state whether you want access, correction or deletion. Include your verified phone detail and the relevant record date, but do not send a password or complete wallet credential.

We keep records while needed for account operation, payment reconciliation, dispute handling or legal duties. When the relevant need ends, we delete or restrict the record according to the applicable requirement.

Yes, the same data handling terms apply to access from Yogyakarta when local law permits. Your mobile browser, account step and QRIS reference are handled under the purposes stated in this policy.