Reference

Open the raja indo Privacy Policy

raja indo Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and cashier.

Account dataWallet recordsDevice accessCookie choices
raja indo Open the raja indo Privacy Policy
CONTACT ROUTES

Switch to clear Privacy Policy help

A clear contact path matters when you want to understand or change personal data held with your account.

Account help Use the account help path for a Privacy Policy question about your profile, phone verification or login record. We may ask for an account identifier and a confirmation step before discussing personal details, so your request is connected to the right account.
Wallet status For a data question tied to DANA, OVO, GoPay or QRIS, include the payment reference and approximate time. We can then check the stored status without requesting your wallet password, PIN or full authentication details through the contact route.
Correction request If your name, phone detail or account record needs correction, tell us which field is inaccurate and why. We may verify ownership before making a change, then use the account help path to confirm what action we completed.
DATA PRACTICE

Browse the controls behind your data

We keep our Privacy Policy practical: account data supports identity checks, payment records support wallet reconciliation, and device signals help us spot an unusual login.

Account security

Phone verification helps us match account access with the contact detail you supplied. If a login looks unusual, we may request another ownership step before discussing profile or wallet data. Never place a password or wallet PIN in a support message.

Payment records

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount and status record for reconciliation. We use that information to investigate a missing receipt or unclear cashier result, not to request your private wallet credentials.

Device details

Your browser and device may provide session, language and technical details when you move from account access to the lobby. These details help identify failed sessions and protect the account, while they are handled separately from wallet authentication secrets.

Cookie choices

Necessary cookies help maintain login and security functions. Where optional cookies are offered, you can manage them through your browser settings or the available cookie control. Removing some cookies may require you to repeat account steps on your next visit.

Retention checks

We retain records only for the account, payment reconciliation, security or legal purpose that calls for them. A deletion request does not always remove transaction or security records immediately when a valid retention need still applies.

Policy requests

To ask what personal data we hold, request a correction, or ask about deletion, contact us through account help with a clear description. We verify the request before releasing or changing data, which protects your account from an unauthorised change.

Get Privacy Policy answers before access

These Privacy Policy answers cover the questions we expect before an Indonesian account is opened or used. They explain the account step, wallet references, mobile cookies, access conditions and the contact route for data requests. If your situation is unusual, send the relevant details through account help rather than sharing private credentials.

The raja indo Privacy Policy covers account details, phone verification, login activity, device and cookie data, payment references, support messages and security records. It explains why we use each category, how retention is assessed, and how you can request access, correction or deletion where applicable.

DANA and QRIS can return a transaction reference, status and timing when you use them with your account. We use those details to reconcile a cashier record or investigate a receipt question. We do not need your wallet password or PIN for that check.

Yes. Send a data-access request through the account help path and describe the records you want, such as profile details, phone verification or payment references. We first confirm account ownership, then explain which records can be supplied and which may require continued retention.

Tell us which account field is wrong and provide the corrected value through account help. We may use a phone verification step before changing it. If the detail is tied to a DANA, OVO, GoPay or QRIS record, the original transaction reference may remain unchanged.

Yes. Our Privacy Policy covers cookies and similar browser storage used for login sessions, security and available preferences. You can manage optional cookie choices through your browser or the displayed control. Removing necessary session data may sign you out or repeat the account path.

Access and eligibility depends on local law. If local rules affect account opening, data handling or a request outcome, we apply the relevant restriction and explain it through account help. Where local law permits, we process eligible requests after confirming the account owner.

Use the account help route and label your message as a Privacy Policy request. Include your account identifier, the action you want and any relevant payment reference, but never include a password or wallet PIN. We use the ownership check before discussing personal data.