Reference

pandawin Privacy Policy For Your Account

The pandawin Privacy Policy explains how we use details linked to your account, including your phone verification, device activity and wallet records from DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record handlingAccount access rightsCookie choices
pandawin pandawin Privacy Policy For Your Account
HELP PATHS

Privacy Questions Reach The Right Team

A clear support route helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record. Sign in first when possible, then use the account support path so we can connect your request with the right phone verification and payment reference. If you are in Bandung or elsewhere in Indonesia, include the affected device and date to reduce back-and-forth.

Team online

Account support path

Use the support route inside your signed-in account for Privacy Policy questions, access requests or corrections connected with your phone verification.

Cashier status check

For DANA, OVO, GoPay or QRIS records, share the receipt reference through the account support path so we can locate the relevant transaction data.

Device access details

Tell us whether you used a mobile browser or desktop browser, plus the sign-in time, when a privacy request follows an unusual access alert.

DATA PRACTICES

Six Practical Privacy Commitments

We handle this policy area through defined account steps rather than vague promises. Phone verification helps connect a request to the correct account, while device and sign-in records help us investigate access…

Account data

We may hold your contact details, phone verification result, sign-in history and account messages so we can provide access and answer account-related requests.

Cookie controls

Cookies and similar device markers can remember sign-in choices and help us understand account access. You can manage browser cookie settings, though some account functions may need them.

Security checks

We compare sign-in and device signals when access looks unusual. If a wallet request needs confirmation, we may ask for account details already linked to your verification step.

Retention periods

We keep records for as long as needed for the stated purpose, account support, dispute handling or applicable legal duties, then remove or de-identify them where appropriate.

Data access

You can ask which personal details we hold and request a copy or correction through the signed-in support path, using the phone or account detail linked to you.

Request changes

If your name, phone detail or contact route needs correction, describe the change clearly. We may verify your account before updating records or closing the request.

Privacy Policy Answers For pandawin

These Privacy Policy questions address the account, device and payment-record issues you are most likely to consider before opening an account. Each answer points you toward a practical step, including how to contact us when a request concerns access, cookies or wallet data.

It covers account and contact details, phone verification, sign-in and device records, support messages, cookies, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us connect account access and privacy requests to the correct person. It also supports checks when an unfamiliar device signs in or a wallet receipt needs matching.

Yes. The Privacy Policy applies when you use a mobile browser or desktop browser. We may process device and sign-in signals needed to maintain account access and investigate unusual activity.

Sign in and use the account support path, then ask for access to your personal data. Include the account phone detail or relevant reference so we can verify and locate the request.

Yes. Send the requested correction through account support and explain which detail is wrong. We may confirm your account before changing contact, phone or payment-reference records.

We use payment references and receipt details to connect a DANA or QRIS request with the correct account, investigate status questions and respond to support requests. We do not need unrelated wallet details.

Use the signed-in account support path and mention cookies or retention in your request. We will explain the relevant purpose, available choices and any legal reason a record must remain.