Reference

RAJADANA Privacy Policy Explained

Our Privacy Policy explains how we handle the account, device and wallet data used when you access RAJADANA, including DANA, OVO, GoPay and QRIS selections.

Account dataWallet choicesCookie controlsAccess requests
RAJADANA RAJADANA Privacy Policy Explained
CONTACT ROUTES

Get Privacy Help From Your Account

A clear contact path matters when you need a copy, correction or deletion request. Start inside your account support area and include the email or phone detail attached to your profile, plus…

Account support path Open the support area after login and identify the account email or phone number connected to your request. We can then locate the relevant profile data without asking you to send wallet passwords.
Payment data query For a DANA, OVO, GoPay or QRIS question, include the payment rail and receipt status shown in your account. We use those details to separate a cashier record from unrelated account activity.
Access correction request Tell us which field needs review, such as a phone number or device entry, and explain the requested change. We may ask for account confirmation before updating or releasing personal data.
HOW DATA WORKS

Account Security And Cookie Choices

We keep this policy practical by linking each data use to an account action: login, phone verification, wallet selection, receipt matching or support contact.

Account details

We use your submitted account details, such as contact data and phone verification status, to create the correct profile and respond to account requests. We do not need your DANA or bank password.

Payment references

When you choose QRIS, DANA, OVO, GoPay, bank transfer or a virtual account, we retain payment references and status details needed to reconcile the request with your account.

Device signals

Browser type, device identifiers and login timing can be recorded to keep sessions working and flag unusual access. These signals are not a substitute for your phone verification step.

Cookie settings

Cookies may remember a session or preserve a selected page setting. You can adjust cookie controls in your browser, although blocking them may require another login or affect account access.

Retention periods

We keep account, payment and support records only for the period needed for the stated account purpose, dispute handling or a local legal requirement. You can ask why a record remains stored.

Your data request

Use the account support path to request access, correction or deletion where local law permits. Include the relevant account step, and we may confirm ownership before acting on the request.

Privacy Policy Questions For RAJADANA

These answers focus on the data choices you are most likely to consider before opening an account or selecting a local wallet. If your question is not covered, use the account support path and point to the relevant Privacy Policy topic.

It covers account details, phone verification, device signals, cookies, payment references and support records created when you use RAJADANA. It also explains retention, requests and local-law limits.

Yes. The Privacy Policy explains how we use the payment reference and status linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. Wallet passwords stay with your wallet provider.

We may record browser, device and login signals to maintain a session and identify unusual account access. These signals help protect the account but do not replace phone verification.

After login, open the account support path and ask for access to your stored data. Include the account email or phone detail, then complete any ownership check we request.

Yes, where local law permits. Name the field that is wrong, such as your phone detail or device entry, and send the request through account support so we can verify and update it.

We retain payment references and related support records for the period needed for reconciliation, disputes or a local legal requirement. You can ask support why a specific record is still retained.

The policy is available for account questions, but access and eligibility depend on local law. If a local rule affects your request or account, we will address that through the available support path.