Reference

rajavigor Privacy Policy Explained

The rajavigor Privacy Policy explains what we collect when you open an account, verify your phone and move from login to the lobby.

Account dataDevice choicesWallet recordsPolicy requests
rajavigor rajavigor Privacy Policy Explained
REQUEST ROUTES

How To Reach Us About Privacy

A privacy question should not require a search through your account. We provide a clear support path for requests about stored details, wallet references, cookie choices or access records. Use the account help route when login stalls, then identify the request as a Privacy Policy matter so we can separate it from a DANA or QRIS status check. We may ask for account details to confirm that the request comes from you.

Team online

Account help path

Open account help from the login or cashier area and state that your request concerns the Privacy Policy. We use your account step and phone verification status to locate the correct record.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, include the payment reference and date shown in your account. We can check the recorded status without asking you to send a wallet password.

Privacy change request

Ask us to access, correct or clarify personal details through the same support path. We may verify your account before discussing records connected with Live Casino or other lobby activity.

DATA HANDLING

Six Practical Privacy Commitments

Privacy work is part of the account flow, not a separate promise placed away from the lobby.

Account details

We handle your phone number, verification result and account identifiers to create and protect access. These details help us distinguish your account from another session when you move from login to the lobby.

Cookie choices

Cookies can remember a session, language setting or security state on your mobile browser. If you clear them, you may need to complete phone verification again before account access continues.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt with your account. We use the reference and status, not a request for your wallet password.

Account security

We may check your phone verification status, device session and recent sign-in details when a request concerns private records. This reduces the chance of releasing account data to the wrong person.

Retention approach

We retain account, security and payment references only for operational, dispute and legal needs connected with the account. When a record is no longer needed, our handling follows the applicable retention requirement.

Correction requests

You can ask us to correct account details or explain how a record was used. Include the affected account step, such as phone verification or QRIS status, so our support team can respond precisely.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account questions you are most likely to have before opening access. We keep the wording practical, with references to phone verification, mobile browsing and Indonesian wallet records. If your question is not listed, use the account support path and identify it as a privacy request. Availability remains where local law permits.

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

Phone verification helps us create the correct account, protect login access and confirm a privacy request. It also helps support separate your record from another session using the mobile lobby.

Our policy covers payment references and recorded status, not a request for your DANA, OVO, GoPay or QRIS wallet password. Use the wallet provider directly for credentials or wallet security concerns.

We may receive browser, device, session and access details needed for security, troubleshooting and cookie operation. Clearing mobile browser cookies can require another login or phone verification step.

Use account help and identify your message as a Privacy Policy request. Name the detail to correct, such as your phone record or payment reference, and we may verify account ownership first.

We keep account, security and payment references for operational, dispute and legal needs. The applicable retention requirement determines when a record can be removed or no longer used.

Yes. Ask through the privacy support path and mention the account step involved. We can explain how records support login, phone verification, wallet status or access to titles such as Sweet Bonanza.