Reference

raja1606 Privacy Policy for Your Account

Our Privacy Policy explains how raja1606 uses account, device and payment details when you access Sic Bo, Plinko or Aviator.

Account dataDevice detailsWallet choicesYour privacy requests
Explore Our Lobby Read FAQ
raja1606 raja1606 Privacy Policy for Your Account
HELP WITH YOUR DATA

Get Policy Help Near Wallet Status

A clear contact path helps when you want to ask about your Privacy Policy rights or an account record linked to a wallet action. Use the account help route while signed in, and include the phone number on your profile plus the relevant payment reference. We use those details to locate the correct record without asking for a wallet password or full payment secret.

Team online

Account help route

Send a Privacy Policy question from your signed-in account help area. Adding your profile phone number helps us match the request to the correct raja1606 record.

Payment record query

For DANA, OVO, GoPay or QRIS data questions, include the transaction reference and date. We can check the account-side status without requesting your wallet PIN.

Access request

Ask us to find, correct or remove eligible account data through the same support path. We may verify your phone before discussing private account details.

HOW WE HANDLE RECORDS

How We Protect Account Details

Privacy is handled through practical account controls rather than broad promises. We separate login details from wallet credentials, review unusual device activity and use phone verification before account access.

Data handling

We use profile, verification, device and payment-reference data to provide account access, match wallet activity and investigate unusual sign-ins. We do not ask for your DANA, OVO or GoPay password.

Cookie controls

Cookies can keep your session and selected settings available between pages. You can clear or restrict them in your browser, although sign-in preferences may need to be set again.

Account security

Phone verification is part of the access path, and device signals help us identify activity that does not match your usual sign-in pattern. Keep your phone and login details private.

Record retention

We keep account, support and payment-reference records for as long as needed for security checks, account assistance, disputes or legal duties, then remove or separate them when appropriate.

Correction requests

If your phone number, account name or another eligible detail is wrong, contact us through account help. We may ask for verification before changing a private profile record.

Who to contact

Our account support route handles questions about this Privacy Policy, stored device details, cookies, payment references and data access. Include a specific request so we can follow the right record.

Privacy Policy Questions Before Opening

These Privacy Policy answers focus on the account decisions you make before opening access, from phone verification to local wallet use. We keep each answer tied to the records we handle on raja1606, so you know what to provide and where to ask for help.

It covers account details, phone verification, device activity, cookies, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use your phone number to create and verify the account, support sign-in checks and match a privacy request to the correct record before discussing private details.

No. We may receive a payment status or reference from DANA, OVO, GoPay or QRIS, but you should never provide a wallet PIN, password or full secret.

Use the signed-in account help route and ask for a copy of eligible records. Include your profile phone number and request details; we may verify ownership first.

Yes, you can request a correction to an eligible account detail through support. Tell us which field is wrong, and complete the phone check if we request it.

We retain records for account support, security checks, disputes or legal duties for the period needed for that purpose. Afterward, we remove or separate them when appropriate.

It applies to your use where local law permits, while access and eligibility depends on local law. Contact account support if you need clarification about a local requirement.

Related Pages

raja1606 Indonesia Sic Bo Plinko MotoGP Betting Account information