Reference

raja01 Privacy Policy For Your Account

The raja01 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet data contextCookie choicesContact route
raja01 raja01 Privacy Policy For Your Account
CONTACT THE DESK

Get Policy Help Through Your Account

A privacy question should have a clear route, so we connect requests to the account record rather than asking you to send sensitive details through an…

Account help route Open the account help path and select the privacy request subject.
Wallet record check For DANA, QRIS, OVO or GoPay questions, provide the payment reference and date, not…
Support desk hours Our support desk handles Privacy Policy requests from 09:00–23:00 WIB.
HANDLING YOUR DATA

See The Controls Behind This Policy

We apply the Privacy Policy through practical account controls rather than a separate process you must learn.

Account security

We record sign-in time, device type and security events to help identify unusual account access.

Device records

A mobile browser or desktop session can create technical records such as IP address, browser type and session timing.

Cookie controls

Cookies help keep a signed-in session working and remember selected settings.

Payment references

For BCA, BRI, Mandiri or BNI bank transfer records, we use the reference, amount status and timing needed to match…

Retention requests

You may ask why a record remains, request correction of an inaccurate detail or ask for deletion where local law…

Policy contact

Send a Privacy Policy request through the account help route with a clear subject and reachable contact.

Your Privacy Policy Questions Answered

These answers address the searches we receive most often about the raja01 Privacy Policy, from wallet records and cookies to access requests. If your situation is different, use the account help route and describe the exact record or action you want us to check.

It covers account details, phone verification, device and login records, cookies, payment references, support requests and retention. It explains why each category is used and how to ask about your records.

Yes. We may retain a DANA or QRIS reference, payment status and timing so we can match an account event. We do not require your wallet PIN or password for that check.

Phone verification helps confirm that the person opening or accessing an account controls the submitted contact. We may request it again before changing account details or discussing private records.

You can request access through the account help route during support hours. Include your account identifier and request subject; we verify identity before sending account-linked data or explaining its source.

Send a correction request through account help and identify the inaccurate field. We may confirm your phone number or another account detail before updating the record and will explain any limitation.

You may request deletion where local law permits. We first verify the request, then explain whether security, payment reconciliation, disputes or legal duties require a record to remain.

Required cookies help maintain your signed-in session and selected settings on mobile. Browser controls can remove or block them, but doing so may interrupt access or a privacy request.