Reference

raja panda Privacy Policy For Your Account

Your raja panda Privacy Policy explains how we handle your account details, phone verification, device access and wallet records from DANA, OVO, GoPay or QRIS.

Account dataWallet recordsDevice accessCookie choices
Explore Our Lobby Read FAQ
raja panda raja panda Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact path helps when your account record, phone check or wallet reference needs attention.

Account data request Ask us to explain the account details connected with your phone verification, login history or support conversation. We may request an account step or identity detail before responding, because privacy replies should reach the person who controls the account rather than a third party.
Wallet record question If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt reference through the account support path. We use the payment record to locate the issue, while keeping wallet details limited to the request and avoiding unnecessary disclosure.
Access concern Tell us when a phone, browser or mobile session shows account data that you do not recognise. We can check the relevant login event, ask for a verification step and explain the available account action where local law permits.
HANDLING DETAILS

How We Handle Your Privacy Choices

Privacy controls work best when they follow the same account path you already use. We separate contact details from payment references, record the reason for a data request and retain records only…

Account details

We may handle your name, contact details, phone verification result and account preferences to create and maintain access. We use those details for the account purpose you selected, not as a reason to send unrelated messages or expose your information to another account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference data linked to your account. We use it to match a receipt, check wallet status and resolve a transaction question without treating the reference as public profile data.

Cookies and sessions

Cookies can retain a session choice, support account access and help us identify unusual browser behaviour. Your browser settings provide a way to remove or restrict cookies, although some account functions may then need another login or verification step.

Mobile and desktop

When you move between a mobile browser and desktop, we may record device and session signals used to protect the account. These signals help us investigate unfamiliar access without assuming that a different device means your account details should change.

Retention period

We keep account, support and payment records for the period needed to operate the service, resolve disputes, protect account access or meet applicable legal duties. When a record no longer serves one of those purposes, our handling follows the deletion or restriction process available to us.

Changes and contact

You can ask about a correction, access request or privacy wording through the account support path. We may verify your phone or account details first, then explain the result, any limits and the next step where access depends on local law.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account records you are most likely to ask about before using raja panda. We explain what can connect to your phone verification, how wallet references are handled, how cookies affect a mobile session and how to ask for access or correction. If a question involves eligibility, the answer depends on local law and the account context shown to you.

The raja panda Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use those records, how we protect account access, how long records may remain and how you can ask about your personal data.

Yes. Privacy Policy handling can include a DANA or QRIS reference, as well as OVO, GoPay, bank transfer or virtual account records connected with your account. We use those references to match receipts, check status and respond to payment questions without publishing wallet details.

Use the account support path shown after login and ask for access to your account data. Include enough detail for us to locate the account, but avoid sending unrelated documents. We may complete a phone or account verification step before sharing records where local law permits.

You can request a correction through the account support route when your contact detail, phone status or another account record is inaccurate. We check that the request comes from the account holder, update the relevant record when appropriate and explain any restriction required by local law.

Cookies can remember a session choice and help us detect unusual access on your mobile browser or desktop. Your browser controls can remove or restrict them. If you block required cookies, we may ask you to log in again or complete a phone verification step.

We retain account, support and payment records only for operational needs, account protection, dispute handling or applicable legal duties described in the Privacy Policy. The period can differ by record type. You can ask support how a specific record is handled and whether a restriction is available.

Send your concern through the account support path displayed on the raja panda site, or use the site contact route when you cannot log in. Describe the privacy issue and the relevant account step. We may verify ownership before discussing personal data or changing access.

Related Pages

raja panda Indonesia maribola Access guide About Us Dragon Tiger