Reference

Privacy Policy For Your rprp Account

Our Privacy Policy explains what we collect when you open an rprp account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesSecurity steps
rprp Privacy Policy For Your rprp Account
HELP WITH REQUESTS

Account Help Beside Wallet Status

A clear support path helps you ask about Privacy Policy rights without explaining your account history from scratch.

Policy request Ask us to explain, correct or remove eligible account data through the account support path. Include your registered contact detail so we can check the request against the right profile before making a change.
Wallet record For a DANA, OVO, GoPay or QRIS question, send the payment reference and approximate date with your account contact. We can then distinguish a wallet-status query from a request about stored personal data.
Access concern If a sign-in or phone verification issue affects your Privacy Policy request, tell us which device path you used, such as mobile browser or desktop. This gives support a safer way to confirm context.
SIX DATA CONTROLS

Six Privacy Controls In Your Account

We handle this policy area through practical account controls rather than vague promises. Your data is tied to the account step that created it, cookies support the device session, and security checks…

Collected details

We collect contact and verification details when you open an account, plus sign-in and account activity needed to protect access. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account help us match a transaction.

Cookie use

Cookies help keep your mobile or desktop session active, remember a selected setting and identify repeated sign-in risk. You can adjust browser cookie controls, although changing them may affect the account path or policy display.

Account security

Phone verification is checked before account access, while sign-in signals help us spot unusual device activity. If you contact us from a different device, we may ask for registered account details before discussing private records.

Retention approach

We retain account and payment references for the period needed to provide account support, reconcile DANA Fast Transfer or other wallet activity, address disputes and meet applicable legal duties. Retention can vary with the record type.

Your changes

You can ask us to correct contact details, explain stored records or remove eligible data through support. State the exact change you want, and we will confirm what can be changed after checking account ownership.

Policy contact

Use the account support route for Privacy Policy questions and include your registered phone or email. We keep the request attached to the relevant profile, so you do not need to send full wallet credentials.

Privacy Policy Questions For rprp

These answers address the Privacy Policy searches we expect when you are deciding whether to open an account. Each answer points you toward a practical account step, data request or wallet record check. If your situation is not covered, use the support route with the smallest useful set of account details.

It covers account creation, phone verification, sign-in events, cookies, device signals, support requests and payment references. It also explains how we use those records for account access, wallet reconciliation, security checks, retention and eligible requests to correct or remove data.

Phone verification helps us confirm account access and reduce the chance that another person receives private account details. We use the registered contact detail when you ask about Privacy Policy records, including a request connected to DANA, OVO, GoPay or QRIS.

Yes. The policy covers payment references and status records connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use those references to match an account event without requesting your wallet password or full credentials.

Use the account support path and state whether you want a correction, an explanation of stored data or removal of eligible data. Include your registered phone or email, but do not send a wallet password. We confirm account ownership before processing the request.

Cookies and similar device signals help maintain your mobile browser session, remember a setting and identify unusual sign-in behaviour. You can change cookie controls in your browser. If cookies are blocked, parts of the account path or Privacy Policy display may not work as intended.

Retention depends on the type of record and the reason it is needed. We keep account, security and payment references for support, reconciliation, dispute handling and applicable legal duties, then apply our retention rules. Ask support about a specific record and its status.

Access depends on local law. We make the Privacy Policy available so you can understand data handling before opening an account, but account access and eligibility apply only where local law permits. Contact support if you need the policy path for your situation.