Reference

rp888 login Privacy Policy Explained Clearly

rp888 login Privacy Policy sets out how we collect, use and protect the account, wallet and device details you provide when you open an account or sign in.

Account dataWallet recordsCookie choicesAccess requests
rp888 login rp888 login Privacy Policy Explained Clearly
PRIVACY HELP DESK

Get Help With A Privacy Request

A clear contact path matters when a name, phone number or payment reference needs attention.

Account support route Open the support path from your signed-in account and state whether you want access…
Payment record check For DANA, OVO, GoPay or QRIS questions, include the payment reference and date rather…
Device access concern If a mobile browser or desktop session shows an unfamiliar sign-in, tell our support…
DATA CONTROL DETAILS

What We Do With Your Personal Data

Our privacy process follows the account journey rather than treating every record the same. Sign-in details support authentication, payment references support reconciliation, and device signals help identify unusual access.

Account security

We use sign-in records, verification steps and device signals to help protect your account. If a login looks unfamiliar, contact support from the account path and avoid sending passwords or wallet PINs in a message.

Payment matching

A DANA, OVO, GoPay or QRIS reference is used to match a transaction with your account and resolve a status question. We record the reference needed for checking, not the private credential used inside your wallet.

Mobile browser data

When you sign in through a mobile browser, we may record browser type, operating-system signals and session time for access protection. These details help us investigate an unfamiliar device without reading unrelated phone content.

Cookies and sessions

Cookies can keep a session choice or help us understand whether a page loads correctly. You can manage browser cookie settings, although removing certain cookies may require you to sign in again on the next visit.

Retention periods

We retain account, payment and support records only as long as needed for account administration, security checks, dispute handling and legal duties. When a record is no longer needed, our process moves it toward deletion or secure disposal.

Requests and corrections

You can ask what personal data we hold, request a correction or question how a record was used. We may verify your account first, then explain what can be changed and what must remain for a stated legal or security reason.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you are most likely to have before opening or using an account. We explain the records connected with login, local wallets, cookies, device sessions and support requests in plain terms. If your question involves a particular DANA, OVO, GoPay or QRIS reference, use the account support route so we can check the correct record.

It covers personal details used for account creation, sign-in, verification, payment matching, support and device security. It also explains cookies, retention and your request options. The policy applies to access where local law permits, and eligibility depends on local law.

Device and browser signals help us identify unusual sign-ins, protect your account and investigate an access concern. We may record the device type, operating-system signal and session time, but this does not give us access to unrelated files or content on your phone.

No. We may retain a DANA or QRIS transaction reference, amount status and timing so we can match the record to your account. Your wallet password, PIN and private wallet credentials stay with the relevant payment service and should not be sent to support.

Use the signed-in account support route and ask for an access request. Include the account contact detail and the approximate period you want checked. We may verify your identity before responding, so personal records are not disclosed to someone else.

Yes, send a correction request through the account support path and identify the detail that needs changing. We may ask for an account verification step. If a record is required for security, payment reconciliation or legal duties, we will explain why it remains.

Cookies can remember session choices and help us measure whether pages load properly. You can adjust cookie controls in your browser. Removing necessary cookies may sign you out or require another login, but it does not delete account records by itself.

We keep records for the period needed to manage your account, check security events, reconcile DANA, OVO, GoPay or QRIS activity, resolve disputes and meet legal duties. A deletion request is assessed against those needs before any eligible record is removed.