Reference

rajapola Privacy Policy for Your Account

Our Privacy Policy explains what rajapola collects when you open an account, sign in from your phone, browse Live Casino or use DANA and QRIS.

Account dataWallet checksCookie choicesPolicy requests
Explore Our Lobby Read FAQ
rajapola rajapola Privacy Policy for Your Account
CONTACT YOUR WAY

Privacy Help Beside Account Support

A clear support route matters when a Privacy Policy question appears beside a login or wallet status issue. Start from the account help path and include the email or phone detail attached to your account, plus a receipt reference if your question concerns DANA, OVO or QRIS. We use those details to locate the correct record without asking you to send a full wallet password.

Team online

Policy request

Use the account help path to ask which account details we hold, why a field is used, or how to request a correction. Keep your request tied to one account.

Wallet privacy

For DANA, OVO, GoPay or QRIS questions, include the transaction reference and date rather than secret wallet credentials. We can check the payment record while limiting unnecessary exposure.

Access concern

If a sign-in or device change looks unfamiliar, report it through account support and pause further account activity. We may ask account-step details to confirm that the request is yours.

DATA HANDLING

What We Do With Account Details

We keep the Privacy Policy practical: each data use connects to an account step, a payment check, a cookie setting or a support request.

Account records

We use your submitted account details to create access, verify the phone step before entry and connect support messages with the correct account. We do not need wallet passwords for this process.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a cashier event. We retain the relevant record for checking status, reconciliation and account protection.

Device signals

When you sign in on a phone, we may record technical signals such as browser type, session time and device context. These signals help us investigate unusual access without reading unrelated phone content.

Cookie controls

Cookies can keep a session working and remember selected settings. You can adjust cookie controls in your browser, although disabling some cookies may interrupt sign-in or policy request forms.

Retention questions

We keep records only while needed for the purpose described in this policy, account protection, payment reconciliation or a legal requirement. Ask through account support if you need the retention reason for a record.

Changes and access

You may ask to see, correct or delete eligible account details. We first confirm the request against your account step, then explain any data that must remain for payment or legal records.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the searches we hear before an Indonesian account is opened or a wallet is connected. If your situation involves a specific payment reference, device change or account request, use the support path so we can check the relevant record.

It covers account details, sign-in and device records, cookies, payment references and support conversations connected with rajapola. It also explains your access, correction and deletion request options.

It covers the payment references we receive when you use DANA or QRIS, including status and receipt matching. DANA and QRIS handle their own account data under their separate policies.

We use the phone verification step and limited device signals to create account access, recognise an unusual session and investigate login concerns. We do not use this process to read unrelated phone content.

Send a request through the account help path using the email or phone attached to your account. We may confirm an account step before providing eligible records or explaining any restriction.

Yes. Use account support and identify the field that needs correction, such as a phone detail or contact record. We confirm ownership first, then update eligible data or explain the reason.

We retain payment references only as long as needed for status checks, reconciliation, account protection or a legal requirement. Ask support about a particular DANA, OVO, GoPay or QRIS record.

Use the account help path and describe the policy issue without sending a password or full wallet credentials. Include a transaction reference only when your question concerns payment data or receipt status.

Related Pages

rajapola Indonesia Account information FAQ Access guide About Us