Reference

Privacy Policy for dpr189 Accounts

dpr189 Privacy Policy explains how we handle the details you provide when opening an account, signing in on mobile, and using DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesContact requests
dpr189 Privacy Policy for dpr189 Accounts
PRIVACY CONTACT ROUTES

Get Help With Your Policy Request

A clear contact path helps when you need to ask what data we hold or why a wallet record appears in your account.

Account access If you cannot sign in after phone verification, contact support from the account help path. Tell us whether the issue appears on mobile or desktop, and we can separate an access problem from a request about the personal data attached to that account.
Wallet record For a question about a DANA, OVO, GoPay or QRIS entry, include the payment rail, date and receipt reference. We use those details to locate the status record without asking you to send a wallet password or private security code.
Policy request To ask for a copy, correction or removal of personal data, state the request clearly and provide the account phone number. We may ask for an account check before acting, so a request cannot be made for another person's account.
DATA HANDLING DETAILS

What We Do With Account Data

Privacy choices matter at each account step, from the first phone check to a later wallet status question.

Account details

We use the phone number and account details you submit to create access, complete phone verification and connect your account activity to the correct profile. Keeping those details accurate helps us answer a Privacy Policy request without confusing your record with another account.

Payment matching

When you choose QRIS, DANA, OVO, GoPay, bank transfer or virtual account, payment status and receipt references may be recorded. We use them to match a transaction to your account and resolve a missing or pending entry through the support path.

Device signals

A phone or desktop sign-in can create device and connection signals such as browser type or session details. We use these signals to protect account access and examine unusual activity; they are not a substitute for your phone verification step.

Cookies

Cookies can retain session settings and help us understand whether a page request belongs to the same visit. You can manage cookie settings through your browser, although changing them may require another sign-in before the account path works as expected.

Retention

We retain account, payment and support records for the period needed to operate the account, resolve disputes, meet security needs and handle lawful requests. When a record is no longer needed for those purposes, our process addresses removal or anonymisation.

Your requests

You can ask what personal data we hold, request a correction, ask about processing or request deletion through support. Include the account phone number and a useful reference, then complete any identity check needed to protect your account.

Privacy Policy Questions About dpr189

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. We keep the wording specific to dpr189, including phone verification, mobile sessions, local wallets and requests about stored personal data. Access remains subject to local requirements.

The dpr189 Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account. It also explains why we use those records, how long we retain them and how to contact us.

We use your phone number to create and identify your account, complete phone verification and help support locate the right record. It can also help us examine an unusual sign-in. We do not need your wallet password or private security code to handle a Privacy Policy request.

Yes. The Privacy Policy covers payment status and receipt references linked to QRIS, DANA, OVO and GoPay, as well as bank transfer and virtual account records. We use these details to match a payment to your account and investigate a missing or pending status.

You can contact support through the account help path and ask what personal data we hold. Include your account phone number and describe the records you want, such as account, device, cookie, support or payment data. We may complete an identity check before sending account-specific details.

You can request a correction or deletion by naming the account phone number and the data concerned. We assess the request against account security, payment reconciliation and any period for which records remain needed. We then explain whether the change can be completed and what follows.

Cookies may retain a session setting or help connect requests during one visit on your phone. Your browser controls cookie removal and blocking. If you clear them, you may need to sign in again before reaching the lobby or submitting a Privacy Policy contact request.

Account and policy access depends on local law. Before entering personal details, check the current page and any access notice shown for your region. If you need clarification, contact support with your location and account question; we will explain the available policy contact path.