Reference

Privacy Policy for rajapol Accounts

rajapol Privacy Policy explains what account details we collect, why we use them and how you can ask about your records before opening an account.

Account dataWallet detailsCookie choicesAccess requests
Explore Our Lobby Read FAQ
rajapol Privacy Policy for rajapol Accounts
CONTACT OUR TEAM

Three Ways To Ask About Privacy

A clear contact path helps when you want to understand a Privacy Policy decision or check an account record.

Account support Use our account support path for questions about phone verification, sign-in records or a device session. Tell us the account contact and approximate time, but do not send a wallet PIN, password or complete payment credential. We use those details to locate the Privacy Policy request.
Wallet status If a DANA, OVO, GoPay or QRIS status appears beside your account, ask us to check the related record through support. We can distinguish a payment reference from your private wallet credential and explain which details are retained for the transaction path.
Policy request For a copy, correction or removal question, identify the Privacy Policy request and the account email or phone used during access. We may ask for an account step to confirm ownership before discussing personal data, especially when the request comes from a new device.
DATA HANDLING

Six Details Behind Your Privacy Choices

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account creation

When you open a rajapol account, we use the contact details you submit to create access and send account-related responses. Phone verification confirms the access step before account use. We do not ask you to place a password or wallet PIN in a support message.

Device sessions

Your phone or desktop session may provide browser, device and sign-in signals that help us keep the account connected and identify an unusual access attempt. These signals support security checks around the lobby, including when you move from login toward Live Casino.

Cookies

Cookies can remember a session, language setting or page state so the Privacy Policy and account pages open in the expected place. You can manage cookie controls in your browser. Turning some cookies off may require another login or remove a remembered device setting.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account routes, we use payment references and status details to match an account action. We do not need your wallet password to check whether a reference reached the account record.

Security retention

We retain account, device and payment records only for the operational, security or legal purpose connected to them. A completed phone verification and a payment status may therefore follow different retention periods. Ask support which category applies to your specific Privacy Policy request.

Your requests

Where local law permits, you can ask for access, correction, deletion or an explanation of processing. We may verify ownership through the account contact before responding. If access depends on local law, we will explain the applicable path rather than promise a result that the law does not provide.

Privacy Policy Answers For Your Account

These Privacy Policy questions cover the account, device and wallet points you are most likely to check before opening access. Each answer describes our handling in plain terms and points you toward the account support path when a request needs verification. Access depends on local law, so your location and account status can affect the response.

The rajapol Privacy Policy covers account details, phone verification, device sessions, cookies, payment references and support requests connected with your access. It also explains how to ask about correction, deletion, retention or processing where local law permits.

We collect the contact details needed for account access and phone verification, together with device and session signals used for security. Payment routes such as DANA, OVO, GoPay and QRIS can create status or reference records, but you should never send a wallet PIN.

Cookies help keep a session active, remember a page state and apply a selected setting when you move between account pages and the lobby. You can control them through your browser. Some changes may require another login or remove a remembered device setting.

Contact our account support path and identify the account email or phone used during the relevant access step. Ask specifically for a Privacy Policy data request. We may verify ownership before replying, and the available response depends on local law.

Where local law permits, you can request a correction or deletion by contacting support with the account contact and the record you want changed. Some payment, security or legal records may need to remain for their stated purpose; we will explain that category.

We use DANA and QRIS references and status details to match an account payment step, investigate a receipt question and keep the account record accurate. We do not need your wallet password or PIN. Ask support if you need a specific reference checked.

Your access and any policy request depend on local law, including the rules that apply where you connect from Indonesia. A phone in Denpasar and a desktop elsewhere may show different session signals, but the same request path remains available.

Related Pages

rajapol Indonesia jeboltogell bolaxyz Access guide rajapol Casino