Reference

rpvip1 Privacy Policy For Your Account

Our Privacy Policy explains what account details we collect, why we use them, and how you can ask about them before opening an account.

Clear data purposesWallet record clarityAccount access choicesCookie controls
rpvip1 rpvip1 Privacy Policy For Your Account
CONTACT ROUTE

Get Privacy Policy Help Through Your Account

A clear support route helps you ask about the Privacy Policy without sending sensitive details to an unrelated address. Sign in, open the account support area, and include the phone number linked to your account plus the subject of your request. If wallet status stalls after a DANA or QRIS payment, mention the receipt reference rather than sharing a password. We use the same route for access questions where local law permits.

Team online

Account data request

Ask us to explain the personal data connected with your account, including phone verification records, login events, device signals, and the reason each category is used.

Payment record query

Send a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference through account support so we can locate the related payment record.

Access clarification

If sign-in or eligibility is unclear, contact us from the account support path. We can explain the relevant Privacy Policy wording, while access depends on local law.

HANDLING DETAILS

How We Handle Your Personal Data

Your account data follows practical controls rather than an unclear blanket promise. We limit internal access to information needed for account service, payment tracing, security checks, or support.

Account details

We use your phone number and account identifiers to create your sign-in path, complete verification, respond to account requests, and connect a request with the correct account record.

Device signals

Browser type, device indicators, and login times can help us spot unusual access. These signals support account security and are not treated as a public profile about you.

Cookie choices

Cookies can remember sign-in preferences, maintain session continuity, and help us understand whether a page works correctly. You can manage browser cookie settings, though some account functions may change.

Payment references

We record references needed to trace DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. We use these references for status checks rather than requesting your wallet password.

Retention timing

We retain personal data for the period needed to provide account service, resolve payment questions, protect access, and meet applicable legal requirements. Deletion timing can vary by record type.

Change requests

You can ask us to correct outdated account details or explain how your data is used. Send the request through signed-in support so we can verify account ownership first.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the questions we expect before an account is opened or a wallet record is checked. They explain the practical route for data access, corrections, cookies, account security, and requests connected with rpvip1. If your situation is different, use the signed-in support path and include only the details needed to identify your request.

It covers account details, phone verification, login and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity.

We use your phone number to create the account path, complete phone verification, support sign-in checks, and connect account requests with the correct record. Access depends on local law.

Yes. Send a data request through signed-in account support. We may verify ownership before responding, then explain the data categories connected with your account and the relevant handling purpose.

The Privacy Policy allows us to retain payment references and status details needed to trace DANA or QRIS activity. We do not need your wallet password to investigate a receipt.

You can request a correction through the account support route. Include the outdated field and the replacement detail, but avoid sending passwords or unrelated payment credentials.

Cookies can maintain a signed-in session, remember selected settings, and help us identify technical faults. Browser controls can limit them, although some account functions may then behave differently.

Use the support contact route inside your account and state that your request concerns the Privacy Policy. For eligibility or regional access, the applicable position depends on local law.