Reference

RAJAX Privacy Policy for Indonesia

Your account records, wallet references and device details have a clear place in our Privacy Policy.

Account dataWallet referencesDevice choicesPolicy requests

What DANA And QRIS Data Means

RAJAX Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details needed to create and protect your account, including your contact details, phone verification status, sign-in records, device or browser signals, and messages sent through account help. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we

1
may retain payment references and status records so we can match an account action without storing wallet credentials that we do not need. Game and lobby activity, such as access to Rocket Crash or Super Bingo, may appear in operational records. Cookies can remember selected settings
2
and help us detect unusual sign-ins. We use these records for access, support, account safety and policy administration. Where local law permits, you may request access, correction or deletion, subject to records we must retain. Eligibility and access depends on local law.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Get Privacy Help Near Cashier

A clear contact route helps when a privacy request overlaps with login or wallet status.

Account access If you cannot reach your account, include the phone verification detail and device path you used. We can separate a login question from a Privacy Policy request before checking the record.

Wallet status For DANA, OVO, GoPay or QRIS concerns, share the payment reference and date shown in your account. We use that narrow detail to check status without requesting wallet credentials.

Data changes To request correction or removal, identify the account detail involved and the reason for your request. We may confirm account ownership before changing records connected with access or payment history.

DATA PRACTICE

How We Protect Account Records

We keep privacy work close to the account steps where records are created. Phone verification helps us distinguish your account before we respond, while sign-in checks help us spot an unfamiliar device.

Collected details

We handle contact details, verification status, sign-in events, device signals, payment references and support messages when those records are needed for account access or a requested service.

Cookie choices

Cookies can retain settings and support sign-in checks on your mobile browser. You can review browser controls and ask us how a cookie relates to your account session.

Account protection

Phone verification and account checks help protect records from an unfamiliar device. Never send a wallet password in a support request; payment references are enough for a status check.

Retention reasons

We retain selected account, payment and support records for access control, dispute checks and policy administration. The applicable retention period can depend on the record and local law.

Request owner

Our support route receives requests about access, correction, deletion and cookie questions. Include the account phone detail and the specific record so we can direct the request correctly.

Policy changes

If this Privacy Policy changes, we will present the updated wording through the policy area. Check the page before changing account details or linking a local wallet.

Privacy Policy Questions About RAJAX

These Privacy Policy answers focus on the account actions you are most likely to check before opening access in Indonesia. We cover phone verification, mobile browsing, wallet references, cookies, retention and requests, with eligibility handled where local law permits.

The RAJAX Privacy Policy covers contact details, phone verification, sign-in events, device signals, wallet references, selected lobby activity and support messages connected with your account.

Our Privacy Policy does not require your DANA or QRIS password for a status check. We use payment references and transaction status details to match an account action.

Phone verification helps us confirm account ownership before access or a data request is handled. It also helps separate your account from an unfamiliar mobile device or sign-in attempt.

Yes. Contact us through the account help route and identify the records you want to access. We may confirm ownership before preparing a response, and timing depends on the request and local law.

Send a correction request through account help with the exact detail that needs changing, such as a phone entry or contact field. We may ask for verification before making the update.

Cookies can remember settings and support sign-in checks in your mobile browser. Your browser controls can limit them, although changing cookie settings may affect parts of the account access path.

Retention depends on the record, its account or dispute purpose and local law. The Privacy Policy explains why selected DANA, OVO, GoPay, QRIS or bank references may remain available.

RAJAX Privacy Policy for Indonesia

Get Privacy Help Near Cashier

How We Protect Account Records

Collected details

Cookie choices

Account protection

Retention reasons

Request owner

Policy changes

Privacy Policy Questions About RAJAX

01 What does the RAJAX Privacy Policy collect?

02 Does the Privacy Policy store my DANA or QRIS password?

03 Why does RAJAX need phone verification?

04 Can I request a copy of my account data?

05 How can I correct data in the Privacy Policy records?

06 How do cookies affect my mobile account session?

07 How long does RAJAX keep payment references?

Related Pages