Reference

Open pph21 Privacy Policy Before Account Access

pph21 Privacy Policy explains what we collect when you open an account, use the lobby, contact support or connect DANA, OVO, GoPay and QRIS.

Account detailsWallet recordsCookie choicesContact route
pph21 Open pph21 Privacy Policy Before Account Access
ASK OUR TEAM

Contact Support About Privacy Policy Questions

A direct question is easier to resolve when it includes the account phone number and the subject of your request.

Account access If you cannot complete phone verification or reach your account, contact support through the…
Wallet records For a DANA, OVO, GoPay or QRIS record question, include the payment date, status…
Privacy request Ask for a copy, correction or removal review by stating the exact record involved…
DATA CONTROL

Browse pph21 Privacy Policy Data Handling

We keep account security and data handling connected to practical account events rather than collecting details without a stated use.

Account security

We use phone verification before account access and may compare sign-in timing, device details and security events when activity appears unusual. Never send a password, wallet PIN or one-time code to support. A security question should contain only the account detail needed for identity confirmation.

Cookies

Cookies can keep a session active, remember a language or help us understand whether an account page loads correctly. You can manage or clear them in your browser. If you remove session cookies, signing in again may be required before opening the lobby.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account event may leave a reference, amount status and time in our records. We use these fields to match a cashier event to the correct account, not to request your wallet PIN or banking password.

Access requests

You can ask what personal data we hold, where it came from and why it is used. Include the account phone number and a precise request. We may need to verify control of the account before releasing details, so another person cannot obtain them.

Corrections

If your phone number or account detail is inaccurate, tell support which field is wrong and provide the corrected value. We compare the request with the account record before making a change. Some historical payment or security records may remain where local law permits.

Retention contact

For a retention question, ask which category you mean: account data, payment reference, cookie record or support message. We will explain the applicable handling route and any reason a record must remain. Privacy Policy questions should stay in the private support channel shown on pph21.

Find Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the account and payment questions you may have before opening the pph21 lobby. They explain how to ask for access, how wallet records are handled and what happens when account security requires an extra check. If your request concerns a particular DANA, OVO, GoPay or QRIS event, keep its reference ready and use the private support path.

The pph21 Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how to ask for access, correction or other handling details.

We use account data to create and secure your access, confirm phone verification, connect a payment status with the correct account and respond to support. Device and sign-in signals can help us investigate unusual access. Eligibility and access depend on local law, not on this policy alone.

Yes. Privacy Policy handling includes DANA and QRIS references, as well as OVO, GoPay, bank transfer and virtual account events. A record can include a status, time and reference used to reconcile the cashier step. Do not send wallet PINs or banking passwords in a request.

You can contact support and ask for the account data connected with your phone number. State whether you want account, cookie, payment or message records. We may verify that you control the account before responding, and the response can depend on legal duties that require some records to remain.

Send support the account phone number, the field you believe is wrong and the corrected value. We check the request before changing a record. If the detail is tied to a payment or security event, the original history may be retained while the current account field is corrected.

Ask support which cookie or session behaviour concerns you, or manage cookies through your browser settings. Clearing them may sign you out and require another phone verification step. We can explain the purpose of a cookie record, but some session functions may not work after removal.

Use the private support contact displayed on pph21 and include a short subject such as access, correction, deletion or retention. Add your account phone number, but never include a password, wallet PIN or one-time code. We will explain the next identity check and the available route.