Reference

rpvip5 Privacy Policy For Your Account

The rpvip5 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice cookiesAccess requests
rpvip5 rpvip5 Privacy Policy For Your Account
CONTACT ROUTES

Where To Send A Privacy Request

A clear contact path helps you ask about the Privacy Policy without searching through account screens.

Account support Use our site support route for questions about the Privacy Policy, phone verification or…
Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account receipt question, send…
Access concerns If a privacy request follows a sign-in problem, tell us whether you used a…
HANDLING DETAILS

How We Apply The Policy

Our Privacy Policy is applied during ordinary account actions rather than kept as a separate promise.

Account collection

We collect account details when you enter them, including your phone number and verification response. Login events and account changes can be linked to that profile so we can identify the correct record when you ask about access or request a correction.

Payment matching

A DANA, OVO, GoPay or QRIS reference may be stored with the related account event. Bank transfer and virtual account records can be handled in the same way. We use these references to confirm status, trace errors and answer receipt questions.

Cookie choices

Cookies can support sign-in continuity, device preferences and basic page operation. Your browser settings can remove or restrict them, although some account steps may then require you to sign in again or repeat a verification action.

Account security

We use phone verification, sign-in signals and account checks to reduce access by someone who does not control your account. Never share a password, PIN or verification code with another person, including anyone claiming to contact you for support.

Retention period

We retain account, support and transaction records for the period needed to operate the account, resolve a payment question, protect access or meet a legal duty. Retention can vary by record type and local requirements, so support can explain the applicable route.

Change requests

You can ask us to correct account details, explain stored records or close access by contacting support through the site. We may verify your identity first, then confirm which data can be changed, removed or retained under local law.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. We keep the wording practical: what is collected, why a receipt is linked, how cookies behave on mobile, and how to contact us. If your situation is not listed, use the support path with your registered phone number and a short description of the request.

The Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It also explains how we use those records for security, account administration and receipt checks involving DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We do not ask you to send a wallet PIN or account password through support. We may keep a transaction reference connected to your account so we can match a DANA or QRIS receipt and investigate a status question without receiving your secret wallet credentials.

Contact support through the site and identify the phone number linked to your account. State that you are asking for a data copy under the Privacy Policy. We may complete an identity check before confirming the records and format that can be supplied.

Yes, you can ask support to correct an inaccurate account detail. Include the registered phone number and explain which field is wrong. We will verify that you control the account, assess the requested change and confirm whether any record must remain under local law.

Cookies can keep browser preferences and sign-in continuity on your phone. If you block or clear them, you may need to sign in again or repeat phone verification. The Privacy Policy still applies, and support can help distinguish a cookie setting from an account check.

The period depends on the record and the reason it was created. We retain details needed for account operation, payment reconciliation, security, dispute handling or a legal duty. Ask support for the retention route connected to a specific receipt or account event.

You can contact support to request account closure and ask which linked records may be removed. We may retain selected transaction, security or support records when required for a legal or dispute purpose. Any access or eligibility decision depends on local law.