Reference

Privacy Policy for raja panda88 Accounts

Your raja panda88 Privacy Policy explains how we handle the details needed for phone verification, DANA and QRIS status checks, and access from your mobile browser.

Phone verificationWallet recordsCookie choicesPolicy requests
raja panda88 Privacy Policy for raja panda88 Accounts
PRIVACY HELP

Where To Ask About Your Data

A clear contact route matters when a phone check, wallet record or deletion request needs attention. We direct privacy questions through the account help area, where you can identify the account concerned and describe the action you want. If your question relates to DANA, OVO, GoPay or QRIS, include the payment name and visible status rather than sending a full wallet password.

Team online

Account help route

Open account help while signed in and choose the privacy subject. Include your registered phone number in the protected form so we can match the request without asking you to post account details in a public message.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, provide the payment rail, approximate date and account reference shown on your side. We use those details to locate the relevant status entry without requesting your wallet PIN.

Access concern

If a privacy request is blocked by a login or phone check, say which step stopped you and whether you used a mobile browser or desktop. That device path helps us separate an account issue from a policy request.

DATA HANDLING

Six Practical Privacy Commitments

We handle privacy through the same account steps you already use: phone verification, sign-in checks, wallet matching and access to the policy page.

Account details

We use your registered phone number and account identifiers to confirm who is requesting access. A clear account path reduces mix-ups between two accounts, especially when one person checks casino sections and local wallet records from the same device.

Device signals

A mobile browser or desktop session may create security signals such as device type, browser details and login timing. These signals help us notice unusual access without treating your handset as a permanent identity.

Cookies

Cookies can remember sign-in preferences, policy choices and page settings. You can adjust cookie controls through the available browser settings or account privacy route, although changing them may affect how the policy page or lobby loads.

Wallet matching

When you use QRIS, DANA, OVO, GoPay, bank transfer or a virtual account, we may retain reference and status details needed to match the payment event. We do not need your wallet PIN to answer a status question.

Security checks

Phone verification and sign-in checks protect account access before private details are shown. If you move from a mobile browser to desktop, we may ask for the same account step again when the session needs confirmation.

Retention requests

We retain records only as long as needed for account operation, payment tracing, security work or a lawful request. You may ask why a record remains, request a correction, or ask whether a deletion request can be handled.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the account questions Indonesian customers usually ask before opening access. We explain what may be collected, how payment references are used, how to reach us and what changes when you switch devices. Where access or eligibility is discussed, the answer depends on local law.

The Privacy Policy covers account details, phone verification, device signals, cookies, wallet references, payment status records and requests about stored data. It explains why we use each category and how you can ask for access, correction or another privacy action through the account help route.

We do not need your DANA or QRIS PIN to match a payment status. We may retain the payment rail, account reference, amount status and timing needed to locate the transaction record. Never place a wallet PIN in an account help request or message.

Phone verification links a private request to the correct account and helps protect details from an unverified session. We may ask for this step before showing account data or changing access settings. The phone number is handled as account data under this Privacy Policy.

A mobile session may provide device type, browser details, login timing, cookie choices and pages opened during the account session. These records help us check unusual access and preserve settings. Switching to desktop can trigger another sign-in confirmation when the session requires it.

Open the account help route and describe the data you believe is wrong, such as a phone detail or account identifier. Include enough information to locate the account, but not a wallet PIN. We may complete a phone verification step before discussing private records.

You can send a deletion request through account help and explain which record you want removed. We assess the request against account security, payment tracing and any lawful retention need. If a record must remain, we will explain the relevant reason through the available contact route.

The Privacy Policy is available from the privacy link before and after account access. Read it on your phone or desktop, then check the account steps for phone verification and local wallet status. Any access or eligibility question depends on local law.