Reference

rp666 Privacy Policy for Your Account

Our Privacy Policy explains what account, device and wallet details we collect when you open an rp666 account, browse Live Roulette Grand or use DANA and QRIS.

Account clarityWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
rp666 rp666 Privacy Policy for Your Account
CONTACT YOUR WAY

Where To Ask About Privacy

A clear contact path helps you resolve a Privacy Policy question without sending sensitive details to the wrong place. Start from the signed-in account support route when you need a copy request, correction or deletion question. If your concern follows a QRIS receipt, wallet reference or login event, include only the details needed to locate it. We may ask you to confirm account ownership before discussing personal records, and access remains where local law permits.

Team online

Account support route

Use the support link inside your signed-in account for Privacy Policy requests. We can locate your profile using the account step and a safe contact detail, rather than asking you to post identity documents in an open message.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, share the payment date, amount reference and account contact only through our support path. We use that narrow set to trace the record without requesting your wallet password or PIN.

Login data concern

If a mobile-browser session, phone verification event or desktop login looks unfamiliar, tell us through account support promptly. We can check the related access record and explain the next account-security step without exposing another person’s details.

DATA HANDLING

What We Keep And Why

We keep this policy practical by linking each data category to an account task you can recognise.

Account details

We use the details you provide at account opening, including contact information and phone verification status, to identify your profile and answer account requests. Keeping these fields current helps us send a correction response to the right account contact.

Device signals

A mobile browser or desktop session may create technical records such as device type, browser path, login time and security events. These signals help us investigate an unfamiliar sign-in; they are not a substitute for your account verification step.

Wallet references

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account can remain linked to transaction status. We use them to reconcile a receipt and respond to a wallet question, while your wallet PIN stays outside our request.

Cookies

Cookies and similar browser storage can remember a session choice, preserve sign-in flow and help us understand whether a page opened correctly. You can manage browser storage through your device settings, although clearing it may require a fresh account login.

Retention checks

We retain records only as long as needed for the purpose described here, account security, payment matching or a legal duty. When a retention reason ends, our handling process can remove, anonymise or restrict the record where local law permits.

Request changes

You can ask us to correct an inaccurate account field, explain a data category or address a lawful deletion request through support. We may verify ownership first, and a request may be limited when retaining the record is required.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the account steps that create the most questions: phone verification, mobile access, wallet references, cookies and requests for changes. We keep the wording tied to rp666 records rather than describing unrelated site functions. If your situation involves a payment reference or an unfamiliar session, use the account support route and avoid sharing a wallet PIN or full password.

The rp666 Privacy Policy covers account details, phone verification, login and device records, cookies, support messages and payment references. It explains why we use each category, how retention works and how you can ask about correction, access or deletion where local law permits.

At account opening, we may collect the contact details you submit, phone verification status, login events and technical device signals. If you use DANA, OVO, GoPay, QRIS or bank transfer, related payment references can also connect to your account activity.

Phone verification helps us match an account request with the correct account contact and investigate access events. We record the verification result and related event details, not your private wallet PIN. We may ask for another ownership check before discussing the record.

Yes. The Privacy Policy covers technical records from a mobile browser or desktop session, such as device type, browser path, login time and security events. These details help us identify an unfamiliar sign-in and keep the account access trail understandable.

We use DANA or QRIS references to match a receipt with the correct account and clarify payment status. The same principle applies to OVO, GoPay, bank transfer and virtual account records. We do not need your wallet password or PIN for that check.

You can contact account support to ask what personal records we hold, request a correction or ask about a copy. We may verify ownership before responding. The available scope and timing depends on local law and any security or payment retention duty.

Send a deletion question through the signed-in account support route and identify the account contact you used at opening. We will assess the request against security, payment matching and legal duties. Where local law permits, eligible records may be removed, anonymised or restricted.

Related Pages

rp666 Indonesia rp666 Casino Access guide Indonesia QRIS Help 514 FAQ