Reference

rp66k Privacy Policy for Your Account

Live Roulette Prestige, Aviator Mobile Play and Wallet Verification Steps sit behind an account flow that records only what we need to provide access, wallet checks and support.

Account dataWallet referencesDevice signalsCookie choices
Explore Our Lobby Read FAQ
rp66k rp66k Privacy Policy for Your Account
PRIVACY HELP ROUTE

Get Help With Privacy Requests

A privacy question should not require you to explain your whole account history. We use the support route connected with your account so we can match a request to the correct phone…

Account request Use the support path shown after account access to ask about personal data, correction or removal. Include the email or phone detail linked to your account so we can identify the correct record without requesting your password.
Wallet question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, share the rail and transaction date only. We can explain how the reference is stored and route a status question without exposing your full wallet credentials.
Access concern If a new phone or browser triggers an account check, contact support through the available account route and describe the device change. We use that context to discuss access records while keeping your verification details private.
HANDLING DETAILS

Inside rp66k Data Handling

Privacy work follows the same practical account steps you see when moving from login to the lobby.

Account creation

We use the details you submit to create and maintain your account, including the clear phone verification step before access. If a field is not needed for that purpose, it is not treated as a reason to request more personal detail.

Wallet references

A DANA, OVO, GoPay or QRIS reference helps us connect a payment status to the right account. Bank transfer and virtual account records can be checked in the same way, while full wallet credentials remain outside our requested support details.

Cookies and sessions

Cookies may remember a session or a setting between account pages. You can adjust cookie controls in your browser, although restricting them may require another login or affect how the account path keeps your session active.

Device protection

We may record practical device signals, such as browser or session context, to identify unusual account access. A change from mobile to another device can prompt a verification step rather than silently changing the account record.

Retention choices

We keep records for as long as they support account service, payment status checks, open requests or legal duties. When those purposes end, our process considers deletion, restriction or continued retention where a documented reason remains.

Your request path

You can ask what personal data is linked to your account, request a correction or ask about removal through support. We may need to verify that the request comes from you before discussing account or wallet records.

Privacy Policy Questions About rp66k

These Privacy Policy answers address the searches we hear most often from people checking account access in Indonesia. They cover the data collected during login, the way wallet references are handled, browser cookies, device changes and the steps for requesting access or correction. If your situation involves a specific DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, use the support route linked to your account and describe only the details needed to locate it.

The Privacy Policy covers account details, phone verification, wallet references, device signals, cookies, support requests and retention. It explains why we use each category, how we protect account access and how you can ask about, correct or restrict personal data connected with your account.

We may handle the details you submit for an account, the phone verification record used before access, session information and practical device signals. We also handle payment references needed to connect DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity to your account.

DANA and QRIS references are used to match a payment status with the correct account and support request. We do not need your password or full wallet credentials for a normal status question. Share the rail, date and relevant reference only through the account support route.

Yes. Send a correction request through the support path connected with your account and identify the field that needs changing. We may verify your phone or account details first, then explain whether the change affects access, wallet matching or an open payment record.

Retention depends on the purpose: account service, payment status checks, support handling or legal duties. When a purpose ends, we assess whether the record can be removed or restricted. An open request or unresolved payment matter may require the related details to remain available.

Cookies can help keep a mobile session active and remember selected settings between account pages. Your browser lets you adjust them, but restricting cookies may require another login or change how the account path works when you move between verification and the lobby.

A new phone or browser can create a different device signal and prompt verification. Use the account support route, explain that the device changed and avoid sending your password. We can discuss the access record after confirming that the request belongs to you.

Related Pages

rp66k Indonesia Football Parlay Guide Access guide FAQ About Us