Reference

rajapools Privacy Policy

rajapools Privacy Policy explains how we collect, use and retain details connected with your account, device and wallet activity.

Account dataWallet recordsCookie choices
rajapools rajapools Privacy Policy
CONTACT PATHS

Get Privacy Policy Help From Your Account

A privacy question should not get lost beside a payment issue, so we keep the contact route close to your signed-in account.

Account privacy request Use the signed-in support path to ask what account details we hold, why they are used, or how to request a correction. Include your registered phone number so we can match the request.
Wallet record check For DANA, OVO, GoPay or QRIS questions, attach the payment reference rather than your wallet password. We can connect a receipt status to the relevant account record and explain the next step.
Device access concern If your Android Chrome or iPhone browser shows an unfamiliar login, contact us through the account support route and mention the device path. We can direct you through phone verification before access.
HANDLING YOUR DATA

Privacy Controls Inside rajapools

We handle this policy area through ordinary account operations you can recognise: a phone check before account access, a wallet reference for payment matching and browser controls for cookies.

Account details

We may use your phone number and account credentials to identify your account, complete the clear phone verification step before access, and protect account actions from an unfamiliar device.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt to your account. We do not need your wallet password to investigate a status.

Cookie controls

Cookies can remember session details and help us understand which account page was opened. You can manage browser cookie settings on Android Chrome or iPhone before returning to the site.

Security checks

We may use device, login and account activity signals to identify unusual access. If a check interrupts entry to Gates of Olympus or Fishing God, support can explain the account step.

Retention approach

We retain records for the operational, safety and legal purposes connected with your account, payment matching and support history. You can ask support which category applies to a specific record.

Change requests

Ask through signed-in support to correct a phone detail, clarify a data use, or request available removal steps. We may need account verification before changing or disclosing personal data.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account, device and payment questions you are most likely to ask before opening rajapools. Each route starts with the signed-in account support path, and access remains where local law permits.

It covers account details, phone verification, device signals, cookies, payment references and support records connected with rajapools. It also explains why we use, retain and protect those records.

Yes. The Privacy Policy covers DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account records used to match a receipt with your account.

We use your phone number to identify the account, complete phone verification before account access and help support locate the correct record when you ask about privacy or payment status.

Open the support route inside your signed-in account and ask for the data category you want to access. Include your registered phone number; we may verify ownership before responding.

You can request a correction through account support. State which detail is incorrect and provide the updated value. We may ask for phone verification before changing the account record.

Cookies can maintain a session and connect browser activity with the page you opened. On Android Chrome or iPhone, you can adjust cookie settings before using the mobile browser path.

Yes. Account and data handling are subject to the rules that apply to your location, so access depends on local law. Contact support if you need a location-specific policy explanation.