Reference

Privacy Policy For Your rp vip2 Account

rp vip2 Privacy Policy explains how we collect, use and protect the account details you provide before you enter our lobby.

Account dataWallet recordsDevice securityPolicy requests
rp vip2 Privacy Policy For Your rp vip2 Account
HELP WITH REQUESTS

Get Privacy Policy Help Through Your Account

A clear contact route matters when you need a copy, correction or explanation concerning personal data.

Account request Use your signed-in account path to ask about stored details, a phone verification record…
Wallet receipt For a DANA, OVO, GoPay or QRIS privacy question, attach the payment receipt or…
Access concern If a device check or phone verification blocks your policy request, tell us which…
DATA CONTROL POINTS

What Your Privacy Policy Covers

Privacy Policy choices should be understandable before you open an account. We separate account identity, wallet records, device signals and support messages so each category has a clear operational reason.

Account identity

We use your name, phone number and verification result to create, secure and locate your account. Phone verification happens before account access, so a Privacy Policy request can be linked to the correct record rather than handled against an unconfirmed identity.

Wallet activity

DANA, OVO, GoPay, QRIS, virtual account and bank transfer references help us trace a payment status or receipt. We use these records for processing, reconciliation and support checks, not as a reason to collect unrelated personal details.

Device signals

Your browser, device type and connection signals may be recorded when you log in. These signals help us notice an unusual access pattern, protect the phone-linked account and assess a security question without reading unrelated content on your device.

Cookies

Cookies and similar storage can keep your session active, remember account-flow choices and support security checks. You can manage cookie settings in your browser, although limiting them may interrupt sign-in, phone verification or a request submitted through the account path.

Retention

We keep account, payment and support records only for the operational, security or legal period connected with their purpose. A deletion request does not automatically remove records that must remain to resolve a transaction, prevent misuse or meet an applicable duty.

Your request

You may ask what personal data we hold, request an accurate correction or ask about deletion where local law permits. Send the request from your account path and include a clear subject, because we may need to verify ownership before changing or disclosing details.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions we expect before registration. Each response stays focused on personal data, account control and the steps needed to submit a request. If your circumstances involve a specific legal right or location, eligibility and available action depend on local law.

The rp vip2 Privacy Policy covers account identity, phone verification, wallet references, device signals, cookies, support messages and retention. It explains why we use each category, how security checks work and how you can ask about correction, restriction or deletion where local law permits.

DANA and QRIS references can be personal data when they connect a payment to your account. We use those references to process, reconcile and investigate a receipt or status question. The same approach applies to OVO, GoPay, virtual account and bank transfer records.

Sign in through your usual phone-verified account path and send a request stating that you want your account data checked. Add the linked phone number and the categories you need, such as device records or wallet references. We verify account ownership before responding.

Yes, you can submit a correction request through the account help route. Tell us which detail is wrong, provide the corrected value and identify the account with its linked phone number. We assess the request against the records and rules that apply where local law permits.

Retention depends on the purpose of the record. We assess account, payment and support data against operational, security and legal needs, then remove or de-identify it when it is no longer required where local law permits. A transaction under investigation may need longer retention.

Cookies can support login sessions, account-flow settings and device security checks. Browser controls let you limit them, but doing so may interrupt phone verification or a submitted request. Your cookie choice does not replace a direct Privacy Policy request about stored account data.

Yes. Account access and any data-related action depend on local law, including where local law permits. We use the location and account context needed to assess a request, and we may explain why a particular access, correction or deletion action is unavailable.