Reference

rr303 Privacy Policy for Your Account

Live Roulette Salon, AduQ Live Arena and QRIS account records are covered by our Privacy Policy, so you can see what we collect before opening an account.

Account clarityWallet record careCookie choicesPhone verification
rr303 rr303 Privacy Policy for Your Account
CONTACT PATH

Privacy Questions Beside Your Account

A clear contact path matters when a privacy request and a wallet receipt meet in the same account. We ask you to use the support route shown in your account area and include the phone number linked to your profile, the request type and any relevant transaction reference. That lets us separate a data question from a DANA, OVO, GoPay or QRIS status issue without asking you to repeat the whole account story.

Team online

Access requests

Ask which account details we hold through the signed-in support route. We may check your phone verification status before releasing personal records, so the request reaches the correct account owner.

Correction requests

If your phone number or contact detail is wrong, tell us the field that needs changing and why. We compare the request with your account record before applying an update.

Wallet questions

For a payment record that looks unfamiliar, include the rail used, such as QRIS or bank transfer, plus its reference. We use those details to trace the privacy and receipt trail together.

HANDLING DETAILS

Cookies, Devices and Account Safety

We keep this policy practical by linking each privacy topic to an account action you can recognise.

Account records

We handle your phone number, contact details and verification state to create and maintain your account. Those fields also help us respond to a request about access, correction or account ownership.

Payment references

A DANA, OVO, GoPay or QRIS reference can show that an account action reached the payment stage. We use the reference for matching and support checks rather than treating it as public profile content.

Mobile cookies

Cookies can keep your signed-in path and selected lobby state available while you move from a mobile browser to account pages. You can manage browser cookies, although some account steps may then need repeating.

Device signals

We may record browser type, device signals and login timing to spot unusual access. These details help us protect your account without changing the privacy request route shown after you sign in.

Retention period

We keep personal and payment-related records for the period needed for account operation, dispute handling, security checks or legal duties. When a record is no longer needed, we remove or limit it.

Policy changes

If this Privacy Policy changes in a way that affects your account data, we place the updated wording on this page. You can ask our support route what changed and request help with your records.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the account and payment questions we expect you to ask before opening access. They cover data collection, wallet references, cookies, corrections and contact steps for rr303, with eligibility handled where local law permits.

The rr303 Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references and support requests. It explains why we use each category, how retention works and how you can ask to access or correct your records.

Yes. The Privacy Policy explains that DANA and QRIS references may be used to match an account action with a payment status or receipt query. We also cover OVO, GoPay, bank transfer and virtual account references in the same way.

When you open an account, we may collect your phone number, contact details and verification state, along with device and browser signals linked to access. The Privacy Policy explains how these records support account ownership checks and security.

You can ask for a copy of personal records through the support route shown in your account area. Include your linked phone number and request type. We may confirm phone verification first, and any response depends on local law.

Use the signed-in support route and identify the detail that needs correction, such as a phone number or contact field. We compare the request with your account record before changing it, so the update reaches the right profile.

Cookies can preserve a mobile browser session, account path and selected lobby state while you move between pages. You can manage them in your browser settings, but turning them off may require you to repeat certain account steps.

Send a deletion or retention question through the support route in your account area and include the relevant account detail. We assess what can be removed or limited against operational, security and legal needs, where local law permits.