Reference

Privacy Policy for rajapool Accounts

rajapool Privacy Policy explains how we handle your account details, wallet records and device access before you open the lobby.

Account clarityWallet recordsDevice accessPolicy requests
Explore Our Lobby Read FAQ
rajapool Privacy Policy for rajapool Accounts
CONTACT YOUR WAY

Privacy Help Beside Account Support

A clear contact path helps you ask what data we hold, why a record appears or how to request a correction.

Account help Use the account help path when you want to ask about profile details, phone verification or login records. We may ask you to confirm account ownership before discussing private data, and we use that step to avoid sending account details to the wrong person.
Wallet status For a privacy question involving DANA, OVO, GoPay, QRIS or a bank transfer, include the payment reference and approximate date rather than a wallet password. This gives us a focused way to trace the record while keeping unnecessary financial details out of the request.
Data request Ask through the same account support route if you want a copy, correction or explanation of personal data connected with your account. We review the request against account ownership details and reply through the contact path already associated with your profile.
DATA CONTROL POINTS

What Your Privacy Policy Covers

Privacy depends on practical controls, not only on a page of legal wording. We separate account records from lobby activity, apply checks before changing phone details and use device signals to help…

Account details

We use the details needed to create and maintain your account, including contact information and phone verification status. This supports account access and helps us distinguish your request from another person asking about the same profile.

Payment references

A payment record can include a method name, reference, status and reconciliation details. DANA, OVO, GoPay, QRIS, virtual account and bank transfer references help us resolve a status question without asking you to share a wallet PIN or password.

Cookies

Cookies may keep a session active, remember a device choice or support basic security checks. They can affect how login and the lobby load on mobile, but they are not a reason for us to request your private wallet credentials.

Account security

Phone verification and sign-in checks help protect changes to your account. When a device or access pattern looks unusual, we may ask for an account step before discussing private records or changing contact details.

Retention

We retain records for the period needed to operate the account, reconcile payments, address disputes and meet applicable legal duties. When a record is no longer needed for those purposes, our handling follows the retention controls attached to that record type.

Your requests

You can ask about access, correction or deletion of personal data through account support. Some requests may need ownership checks or may be limited where keeping a payment or security record is required by local law.

Privacy Policy Questions From Indonesia

The answers below focus on the questions you may have before opening or using a rajapool account. Each response stays within the Privacy Policy scope, from payment references and cookies to account access, corrections and contact steps. If your situation is unusual, send a focused request through account support and avoid sharing wallet passwords or verification codes.

It covers account details, phone verification, login activity, device signals, cookies and payment references connected with your account. It also explains how we use, protect, retain and respond to requests about those records when access is available where local law permits.

DANA and QRIS records can show a payment reference, status and reconciliation result. We use those details to match your account activity and resolve a cashier question. We do not need your wallet PIN or password to investigate a payment status.

Yes. Send a data request through the account help path and identify the account without including unnecessary private credentials. We may confirm phone verification or another ownership detail before discussing the records linked to your profile.

Cookies can support session continuity, device choices and basic sign-in security when you move from login to the lobby on a mobile browser. They may also help us detect unusual access, but they do not replace your account security steps.

Contact account support with the field that appears incorrect and the correction you are requesting. We check ownership before changing phone or profile details, then assess whether the requested change affects payment reconciliation or a security record.

We keep each record while it is needed for account operation, payment matching, dispute handling, security or applicable legal duties. Retention can differ between login events, wallet references and account details, and we remove or restrict records when those purposes end.

Yes. Account access and some privacy requests depend on local law. Where local law permits, we handle access, correction or deletion requests through account support, while retaining records that must remain available for security, payment or legal reasons.

Related Pages

rajapool Indonesia rajapool Casino Account information Access guide FAQ