Reference

Privacy Policy for Your pandawa 88 Account

Our Privacy Policy explains how we handle the details you provide when opening a pandawa 88 account, checking Secure Account Access, or using DANA and QRIS.

Account detailsWallet activityDevice sessionsYour policy choices

Browse Our Lobby Read FAQ

How DANA and QRIS Data Fits

pandawa 88 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We use account details to create and maintain your login, confirm the phone number linked to your account, and respond when a wallet status needs checking. When you choose DANA, OVO, GoPay or QRIS, we may receive transaction references, amount details, status updates and matching account

1
identifiers from the payment flow; we do not treat your wallet PIN as part of our account record. Bank transfer and virtual account references are handled for the same narrow purpose. Device signals, login time and browser details help us identify unusual sessions and keep Secure
2
Account Access working. We retain records for as long as needed for these purposes, dispute handling and legal duties. Access depends on local law, and any service eligibility applies where local law permits. We may update this policy when our data practices change, showing the effective
3
date on this page.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Three Ways to Ask About Privacy

A clear contact path helps you ask what we hold, why we use it, or how to correct an account detail.

Account support Use the account support channel for a copy of personal data linked to your pandawa 88 login, a correction request, or a question about why phone verification is needed before account access.

Wallet status For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the payment reference and date through account support. We can trace the status without asking you to share a wallet PIN.

Security concern If Secure Account Access shows a session you do not recognise, contact us through the account support route and change your password from the account settings path before sharing any further details.

DATA PRACTICES

Six Checks Behind Our Privacy Work

Privacy is handled through practical account steps rather than broad promises. We separate login details from wallet references where the payment flow allows, use device and session signals to investigate account security…

Data collection

We request account details such as your chosen login contact and phone verification result to create Secure Account Access. Payment records from DANA, OVO, GoPay and QRIS help us match a transaction status to your account.

Cookie controls

Cookies help keep your sign-in session and remember basic page settings. You can clear stored cookies through your browser settings, though doing so may require you to sign in again before reaching the lobby.

Session safety

We examine sign-in time, browser type and device signals when an account session appears unusual. These checks support account protection and may lead us to ask for phone verification before access continues.

Retention period

We keep account, wallet and support records only as long as needed for account operation, dispute handling, security checks or legal duties. When a retention reason ends, records are removed or separated from direct account use.

Correction requests

You can ask us to correct an inaccurate name, phone detail or account contact. Include the detail that needs changing and the account identifier used for Secure Account Access so we can match the request safely.

Policy contact

Questions about this Privacy Policy belong in the account support channel. Tell us whether your request concerns data access, deletion, cookies, a device session or a DANA, OVO, GoPay or QRIS record.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers focus on the account questions you may have before using the Indonesia lobby. We explain the data connected with Secure Account Access, local wallet references, cookies, device checks and contact requests. Where a request involves eligibility or continued access, the outcome depends on local law and applies where local law permits.

It covers account details, phone verification, device and session signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, correction requests, security handling and the account support route.

We use phone verification to help confirm that the person requesting Secure Account Access controls the account contact. The result records the verification status, not your private phone conversations. If access eligibility is involved, the decision depends on local law.

No. Our payment handling uses transaction references, status details and matching account identifiers for DANA, OVO, GoPay and QRIS flows. You should never send a wallet PIN, password or full payment credential through account support.

Contact us through the account support channel and state that you want a copy of the data linked to your account. Include your account contact or login identifier, but omit wallet PINs and passwords. We may verify ownership before preparing the response.

Yes. Send a correction request through account support with the inaccurate detail, the replacement detail and the account identifier used for Secure Account Access. We may request a verification step so a third party cannot alter your account record.

Cookies can keep your sign-in session active and remember basic page settings. You can clear or block them in your browser controls. If you do, some account steps may ask you to sign in again, and stored session preferences may no longer remain.

We retain personal data for the period needed to operate your account, trace wallet status, address disputes, investigate security events or meet legal duties. After that purpose ends, we remove the record or separate it from direct account use where practical.

Privacy Policy for Your pandawa 88 Account

Three Ways to Ask About Privacy

Six Checks Behind Our Privacy Work

Data collection

Cookie controls

Session safety

Retention period

Correction requests

Policy contact

Privacy Policy Answers for Indonesian Accounts

01 What does the pandawa 88 Privacy Policy cover?

02 Why does pandawa 88 need phone verification?

03 Does the Privacy Policy store my wallet PIN?

04 How can I request my pandawa 88 account data?

05 Can I ask pandawa 88 to correct my details?

06 How do cookies affect this Privacy Policy?

07 How long does pandawa 88 keep my personal data?

Related Pages