Reference

rp555 Privacy Policy, Clearly Explained

rp555 Privacy Policy shows what account, wallet, device and support details we collect when you open an account or enter the lobby.

Account dataWallet recordsDevice controlsYour access rights
rp555 rp555 Privacy Policy, Clearly Explained
HELP WITH PRIVACY

Get Policy Help From Your Account

A clear contact path matters when you want to ask about Privacy Policy handling. Start from the support link inside your account and include the phone number or email connected to the account, plus the date of the relevant event. We can then locate the right record without asking you to send a wallet password. Questions about a QRIS receipt, DANA status or device sign-in can be directed to the same route.

Team online

Account data questions

Use the account support path to ask what personal details are linked to your profile. Include your registered contact detail so we can distinguish your request from another account and reply with the correct Privacy Policy context.

Wallet record checks

If a DANA, OVO, GoPay or QRIS reference appears unclear, send the transaction date and reference shown in your account. We use those details to locate the payment record without requesting your wallet PIN or banking password.

Privacy change requests

For a correction, access request or question about stored data, contact us through account support and describe the requested action. We may ask for an account check before changing records so another person cannot act on your profile.

DATA HANDLING

How We Apply Privacy Policy Controls

Privacy Policy controls are tied to real account actions rather than broad statements. We separate identity details from payment references where practical, restrict account changes behind verification, and use device signals to…

Account records

We use the details entered during account creation to identify your profile, complete phone verification and respond to account requests. Keeping your contact detail current helps us send a privacy response to the person connected with the account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference data linked to your account. We use matching details to check receipt status and resolve cashier questions, not to collect wallet passwords.

Cookies and sessions

Cookies can keep your sign-in session and security settings consistent while you move between the lobby and account pages. Clearing them may sign you out or require another check, and browser controls can limit selected cookie functions.

Device security

We may record device type, browser signals and sign-in events to identify unusual access. The same approach applies when you use a phone for Live Roulette Diamond or a desktop browser for account settings.

Storage period

We retain account and payment records for as long as needed for the stated account, security, support and legal purposes. When a record is no longer needed, our handling follows the retention rules described in the current Privacy Policy.

Requests and corrections

You can ask how your data is used, request a copy where applicable, or seek correction through account support. We verify the request first, explain any legal reason for a limit, and record the response for audit purposes.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before account creation. They cover payment references, cookies, phone verification, device access, stored records and requests for changes. If your situation is not listed, use the support path inside your account and include enough detail for us to locate the relevant record.

It explains how we handle account details, phone verification data, device signals, cookies, support messages and payment references. The policy also describes why we use those records, how long they may remain stored, and how you can request access or correction.

No. Our Privacy Policy distinguishes payment references from wallet credentials. When you use DANA or OVO, we may receive a status or reference needed to match the account event, but you should never send us your wallet PIN or password.

Phone verification helps connect an account request to the person controlling the registered contact detail. Under the Privacy Policy, that check supports account access and security reviews. We may ask for another account check before handling a sensitive data request.

A QRIS payment can create a reference, amount and status connected with your account record. We use those details to check whether the receipt matches the cashier event. The Privacy Policy does not require your QRIS PIN or banking password.

Yes. Contact us through the account support path, identify the record you believe is wrong, and explain the correction needed. We verify ownership before changing information, then reply with the result or explain why a legal record must remain unchanged.

Cookies can keep a session active, remember security choices and help account pages function between visits. You can adjust browser settings or clear stored cookies, but this may sign you out or require phone verification again on your next access.

The policy is written for account and data handling in the Indonesian market, while availability and eligibility depend on local law. If you access from Denpasar or another location, local rules may affect whether an account path is available.