Reference

Open the rpvip10 Privacy Policy

rpvip10 explains how we collect, use and protect the details connected with your account, wallet activity and device access.

Account dataWallet recordsCookie choicesSecurity steps
rpvip10 Open the rpvip10 Privacy Policy
ASK OUR TEAM

Get Privacy Help Beside Account Support

A clear contact route helps you ask about personal data without explaining the same issue several times.

Privacy request Use support chat to ask what account details we hold or to request a correction. We may ask you to confirm the phone number linked to your account before discussing private records, so the request reaches the correct account.
Wallet record If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, share the visible transaction reference through the secure support path. We can compare the account record and payment status without asking you to disclose a password or one-time code.
Account access When login or phone verification stalls, contact support before opening another account. We can check the access trail, explain the next verification step and help keep your privacy request attached to the correct account.
DATA IN PRACTICE

See How We Handle Your Details

Privacy controls work best when they match the real account journey. We use information for account access, payment matching, security checks, support replies and legal duties that apply where local law permits.

Account information

We use your contact and verification details to create the account path, confirm access and respond to account questions. Keeping your phone details current helps us connect a privacy request with the correct account without relying on public information.

Payment references

A DANA, OVO, GoPay or QRIS record can include a reference, amount status and time needed to match the cashier event. Bank transfer and virtual account records serve the same matching purpose; we do not need your wallet password.

Device signals

Your browser, device type, language and sign-in events help us identify unusual account access and keep the mobile path consistent. These signals can also help support understand why a verification screen behaves differently on your phone.

Cookies and storage

Cookies and similar storage can remember a session, preserve a selected setting and help us understand technical errors. You can manage browser permissions, but disabling some storage may require you to repeat login or phone verification.

Retention and deletion

We keep account, security and transaction records for the period needed to operate the account, resolve disputes, meet legal duties or prevent misuse. A deletion request is assessed against those needs, so some records may remain where retention is required.

Changes and questions

You can ask us to correct inaccurate account details, explain a record or review a privacy concern through support chat or the listed contact email. We may verify your identity first, then confirm the action or explain why a limit applies.

Find Answers About Your Privacy Policy

These Privacy Policy answers address the searches we hear most often from Indonesian customers. They explain what we collect, why wallet references appear, how device data is used and where to send a request. If your situation is unusual, use the support path above and keep sensitive credentials out of messages.

It covers information linked to your account, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It also explains how we use, retain, protect and review those records when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

The Privacy Policy mentions DANA, OVO, GoPay and QRIS because a payment reference or status may be needed to match your cashier activity with your account. We use that operational detail for payment checks and support replies, not to request your wallet password or one-time code.

Yes. Send a correction request through support chat or the contact email shown on our site. Tell us which account detail is inaccurate, and complete the identity check we request. We will review the record, update it where appropriate or explain why a record must remain unchanged.

Cookies and similar storage can keep your session active, remember a setting and help us trace a technical problem on your phone. Browser controls let you remove or restrict them. If you disable required storage, you may need to repeat login or phone verification.

We retain information while it is needed for account access, security checks, payment matching, support, dispute handling or applicable legal duties. A deletion request does not automatically remove every record; we first assess whether a transaction or security record must remain.

Contact us through the support chat or listed privacy email and describe the account record you want to access. We may ask for phone verification or another account check before sharing details. This protects your information from a request made by someone else.

Yes. Account access and eligibility depend on local law. Our Privacy Policy explains how we handle information when you use the available account path, but it does not override rules that apply in your location. Contact support if you need help understanding a data request.