Reference

raja111 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open a raja111 account, how we use account and wallet details, and how you can request help with your…

Clear data purposesWallet record contextAccount access choicesCookie controls
raja111 raja111 Privacy Policy For Your Account
PRIVATE HELP PATHS

Three Ways To Ask About Privacy

Privacy questions are easier to resolve when you include the account step or wallet status that prompted them.

Account access If you cannot enter your account after phone verification, use the account help path…
Wallet records For a DANA, OVO, GoPay or QRIS privacy question, share the transaction reference only…
Data requests Ask us to explain, correct or review a personal record by naming the account…
SIX DATA CONTROLS

Six Practical Safeguards We Apply

We handle privacy as an operating process rather than a banner on the page. Account creation, phone verification, mobile access and wallet reconciliation each create different records, so…

Purpose first

We use account details for clear operational reasons: creating access, completing phone verification, matching wallet status and responding to privacy…

Cookie choices

Cookies and similar browser records can help retain a session or remember a device path.

Login security

We treat login events, device type and phone verification as account-security signals.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account can be linked to the relevant account…

Retention logic

We keep records for as long as needed for the purpose that created them, including account security, payment reconciliation and…

Change requests

You can ask about access, correction or deletion of personal data through the account help path.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account questions you are most likely to have before opening access or checking a wallet record. We keep the wording practical: what is collected, how a request starts, why verification matters and what local access wording means. The same account help path can be used whether you are on a phone, desktop browser or a page showing Dragon Tiger, bongkarjp or luxbola.

The raja111 Privacy Policy covers account details, phone verification, login and device records, cookies, wallet references, payment status and privacy requests. It explains why we use each category and how you can ask about access, correction or deletion through the account help path.

We may collect the details needed to create and secure your account, including contact data, verification status, login events and device information. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, related references and status records may also be stored.

Device and browser details help us identify unusual login behaviour and protect the account connected to your phone verification. They can also explain why a session ended or why another login is needed. We use this context for security, not to describe your private activity publicly.

Start through the account help path and state that your request concerns personal data. Tell us whether you want access, correction or deletion, and identify the relevant account step. We may verify account ownership before sharing private records or processing a change.

Yes. The Privacy Policy covers references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use them to match payment activity to the correct account and resolve a related privacy question.

Retention depends on why a record exists, whether the account relationship remains active and what local law requires. Security events, payment reconciliation details and an open privacy request may need different periods. Ask through account help and we can explain the relevant record category.

Access depends on local law, and our services are available where local law permits. The Privacy Policy does not change that condition. If you have an eligibility or account-access question, use the account help path without sending unnecessary personal or wallet details.