Reference

pandawa4d Privacy Policy for Your Indonesia Account

Our Privacy Policy shows exactly how we handle the account details, device signals and wallet records connected with your pandawa4d access.

Account dataDevice choicesWallet recordsContact rights
pandawa4d pandawa4d Privacy Policy for Your Indonesia Account
CONTACT PATHS

Get Privacy Help Near Your Account

A clear contact path matters when you want to ask what we hold about you or correct an account detail. Start from the support route shown after login and include the account phone number, the relevant date and the payment reference if your question concerns DANA, OVO or QRIS. We use those details to locate the correct record while keeping the request tied to your account.

Team online

Privacy request

Use the account support route to ask which personal details we hold, why they are used and how a specific record is connected with your pandawa4d account.

Correction request

Tell us which account field needs changing and include the phone verification detail requested on the account path, so we can separate a genuine request from an unknown sign-in.

Wallet query

For a DANA, OVO, GoPay or QRIS concern, share the receipt reference and status shown in your account. We use that narrow record to trace the payment question.

DATA HANDLING

What Your Account Security Stores

We handle privacy through the same practical steps you see during account access: phone verification, device checks and payment matching.

Account details

We use your phone and account identifiers to verify access, connect your wallet activity and respond to a privacy request.

Device signals

Browser type, device information and login timing can support security checks.

Cookies

Cookies can keep your session working and retain selected settings.

Account security

Phone verification is part of the account access path.

Record retention

We retain account and payment records only for service, security, dispute handling or legal needs.

Change requests

Ask us to correct, restrict or clarify your personal data through the logged-in support route.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or linking a local wallet. We keep each response tied to a practical action, from checking device records to asking about a QRIS receipt. If your situation is not covered, use the support route after login and describe the account step or payment reference involved.

It covers account identifiers, phone verification, device signals, cookies, payment references and support records connected with your account. It also explains purposes, retention and ways to request clarification or changes.

Yes. When you use DANA or QRIS, we may handle the reference, amount, time and status needed to match the transaction with your account and investigate a receipt question.

Device and browser details help us recognise unusual access, protect the login path and decide when phone verification is needed. They are used for account security rather than unrelated profile building.

Open the logged-in support route and ask for the personal data connected with your account. Include your account phone detail so we can verify the request before discussing records.

Yes. Identify the field that is wrong and provide the account detail requested during verification. We can then assess a correction request and explain any record that cannot be changed.

Payment records are kept for account service, security, dispute handling or legal needs. The period can depend on the record type and local requirements, and support can explain the applicable purpose.

Yes. Privacy rights, account access and eligibility depends on local law. Where local law permits, we process requests for access, correction or restriction through the verified support route.