Reference

Privacy Policy For Your rp55v Account

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

Account detailsWallet recordsDevice controlsRequest process
rp55v Privacy Policy For Your rp55v Account
REQUEST A RESPONSE

Three Ways To Ask About Privacy

Questions about the Privacy Policy should reach us through a path that leaves enough context for a useful reply.

Account contact Use the support contact shown after sign-in to ask about personal data, a correction or an access request. Include the account contact detail you used and the subject of your Privacy Policy question so we can locate the right record without asking for your wallet password.
Wallet receipt For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the receipt reference and date through our support path. We use those fields to check payment status while avoiding requests for your wallet PIN, password or full private credential.
Sign-in concern If a new device or browser causes an account check, contact support from the account route shown on the site. Tell us the device type and approximate sign-in time; never place a password or one-time code in a support message.
CONTROL YOUR RECORD

Six Practical Privacy Controls

We keep the Privacy Policy practical by connecting each data purpose with an account action you can understand.

Data collected

We may collect account contact details, verification results, sign-in timestamps, device and browser signals, selected pages and payment references. A visit to Live Roulette Wheel or Solo Live Table can appear as a session event, but that record is handled for account operation and security rather than unrelated advertising.

Cookies

Cookies can keep a session recognised, remember a language or help us detect unusual access. Your mobile browser and desktop browser may present different controls. You can check the browser privacy menu and the site prompt before continuing, then contact us if a cookie question remains.

Account security

We use sign-in checks, device signals and phone verification before sensitive account access or important changes. A request involving DANA, QRIS or a withdrawal record may require an additional account step. We will not ask you to disclose a password or wallet PIN.

Retention

We retain records only for the period needed for account operation, payment reconciliation, security checks and applicable legal duties. When a record is no longer needed for those purposes, our handling process moves it toward deletion or a form that no longer identifies your account.

Your requests

You can ask what personal data we hold, request a correction or ask how a payment reference was used. Send the request through the signed-in support route with enough detail to identify the account. We may verify ownership before releasing or changing any record.

Policy contact

Use the support contact displayed in your account for Privacy Policy questions, including cookie choices, retention or a data copy. If access is unavailable, provide the account contact detail and a safe description of the issue, without sending passwords, one-time codes or wallet PINs.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account, device and payment questions we expect before you open an account. They also explain the safest way to contact us when you need a record checked or changed. For any access or eligibility matter, the applicable position depends on local law.

It covers account details, phone verification, sign-in events, device and browser signals, cookies, selected pages and payment references. It also explains retention, security checks and how to request access or correction. The policy applies when you use the site from Indonesia where local law permits.

No. We use a payment reference, receipt detail or status response to reconcile DANA, OVO, GoPay or QRIS activity. Your wallet password, PIN and one-time code should remain private. Send only the reference needed for a support check.

Device and browser signals help us recognise a normal sign-in and identify unusual access. A mobile browser may create a different session from your desktop browser, so an extra phone verification step can appear before account access or a sensitive change.

Sign in and use the support contact shown in your account, then ask for a personal data copy under the Privacy Policy. Include your account contact detail and the records you need. We verify ownership first and will not ask for your password.

Yes, you can request a correction through the signed-in support route. State which detail is wrong and what should replace it. For a change connected to phone verification or a wallet reference, we may ask for an additional account step before updating the record.

We keep payment references and related account records for as long as needed for reconciliation, security checks, account operation and applicable legal duties. After that need ends, our process moves the record toward deletion or removes identifying links where appropriate.

Use the account support contact for cookie choices, data access, correction or retention questions. If you cannot sign in, describe the issue and provide a safe account identifier without a password or wallet PIN. We will use the available verification path before discussing private records.