Reference

Open pg dewa Privacy Policy for your account

Our Privacy Policy explains what pg dewa collects when you open an account, sign in from a mobile browser, verify your phone or use DANA, OVO, GoPay and…

Account dataWallet recordsMobile cookiesPrivacy requests
pg dewa Open pg dewa Privacy Policy for your account
CONTACT ROUTES

Switch to support when privacy questions arise

A clear contact path helps when you cannot identify a wallet record or want to ask about your personal data. We direct privacy questions through account support so we can confirm the right account before discussing details. Include your registered phone number, the relevant date and the request you want us to process; never send a wallet PIN or password.

Team online

Account access

Use our support chat when you need to confirm which phone number is attached to your account or ask why an identity check is needed before a privacy request can proceed.

Wallet records

Send the payment reference and method, such as QRIS, DANA or bank transfer, through support when a receipt appears on your account and you want its data use explained.

Privacy requests

Ask support to correct account details, provide a copy of stored data or explain retention. We may request account verification before sharing records or changing personal information.

DATA PRACTICE

Browse how we protect account data

We handle this policy area through practical account controls rather than broad promises. Sign-in checks, phone verification and device-session records help us separate your activity from an unfamiliar browser.

Collection

We collect details you enter for account creation and phone verification, along with sign-in time, device type and security events needed to maintain a safe account session.

Cookies

Cookies and similar browser storage help remember a mobile session and protect account access. You can manage browser permissions, although changing them may require another sign-in.

Account security

We use phone verification and session checks before discussing account records. If a browser or device looks unfamiliar, we may ask for another account step before responding.

Wallet separation

DANA, OVO, GoPay and QRIS references identify a transaction record, not your wallet password. We use the reference to match status and support requests with the correct account.

Retention

We keep account, support and payment references for operational, security, dispute and legal needs. When a record is no longer needed, our process removes or anonymises it.

Your request

Contact account support to ask for access, correction or deletion details. Tell us the request clearly, and we will explain verification, timing and any local-law restriction.

Check Privacy Policy answers before opening

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover phone verification, mobile browsing, wallet references, cookies, retention and requests for personal data, so you can choose the right support path.

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

Phone verification helps connect a request to the correct account and reduces mistaken disclosure. We may ask for it before discussing stored data, changing details or handling an access request.

The policy covers device type, browser settings, IP address and session cookies used for access and security. You can change browser permissions, but this may require signing in again.

We retain payment references and status details needed to match an account record, resolve support questions and meet legal needs. We do not ask us to store your wallet PIN or password.

Contact account support with your registered phone number and a clear request for access, correction or deletion. We verify account ownership first, then explain the records and available next step.

Retention depends on why the record exists, including account operations, security, disputes and legal duties. After that need ends, we remove or anonymise the relevant record through our process.

Yes. Access and eligibility depends on local law, and where local law permits, we process data requests through support. We explain any restriction that affects your particular account request.