Reference

indoraja Privacy Policy for Your Account

indoraja Privacy Policy explains how we handle your account details, wallet records and device activity when you use our service.

Account detailsWallet recordsCookie choicesContact steps
indoraja indoraja Privacy Policy for Your Account
HELP WITH PRIVACY

Where To Ask About Your Data

A clear contact path matters when a privacy question affects your account or wallet status. Start from the account support route and state whether you need a copy, correction, deletion request or explanation of a cookie. Include the phone number linked to your account, but never send a password or wallet PIN. We use the account details already on file to confirm identity before discussing records. If a DANA, OVO, GoPay or QRIS reference appears incorrect, mention the date and transaction reference so we can trace the relevant entry.

Team online

Account privacy request

Use the support route connected to your account when you want to ask what personal details we hold. We may ask you to complete phone verification before sharing records, which helps prevent another person from receiving your account data.

Wallet record question

For a payment reference linked to DANA, OVO, GoPay or QRIS, send the transaction date and visible reference only. We can investigate the record without asking for your wallet PIN, password or full bank credentials.

Correction or removal

Tell us which detail needs changing or removal and why it is no longer accurate. We check the request against your account, explain any retention reason, and apply the change where local law permits.

DATA HANDLING

What Our Privacy Work Covers

Privacy controls work alongside the account steps you already know, rather than sitting apart from them.

Account details

We may hold your name, phone number and sign-in details because they help create and protect your account. Phone verification is required before account access, and we use those details to match a privacy request with the correct account.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry can identify a payment event without giving us your wallet PIN. We use the reference to reconcile status, investigate errors and answer a related data request.

Cookies and devices

Cookies can keep your sign-in session and selected settings working across a mobile browser. Device and browser signals may also help us spot unusual access. You can manage browser cookies, though switching them off may affect account continuity.

Account protection

We limit sensitive account discussions until identity checks are complete. Never share a password, verification code or wallet PIN in a support message. If a sign-in looks unfamiliar, use the account support route and describe the device event.

Retention choices

We keep records for account operation, payment reconciliation, dispute handling, security checks or a legal obligation. When a record is no longer needed for those purposes, we aim to remove it or separate it from direct account identifiers.

Requesting changes

You can ask for access, correction or removal through the account support route. Tell us the request type and the account phone number, then complete any identity check. We explain the result and any limit that depends on local law.

Privacy Policy Questions About indoraja

These Privacy Policy answers address the account and wallet questions you may have before opening an account. We keep each answer tied to an actual step, from phone verification to a DANA reference or a cookie setting, so you know what to expect when requesting help. If your question is not covered, use the account support route and avoid sending secret credentials.

The indoraja Privacy Policy covers account details, phone verification, payment references, cookies, device signals, support requests and retention. It explains why we use each category and how you can ask for access, correction or removal where local law permits.

We use phone verification before account access to confirm that the person asking about the account is connected to it. The check also helps protect privacy requests from being sent to the wrong person. Never provide your password or wallet PIN.

Yes. Our Privacy Policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use details such as a date or reference to trace status, while we do not need your wallet PIN.

We may record browser, device and sign-in signals connected with account use. These details help keep a mobile session working and identify unusual access. They are handled as part of the Privacy Policy and are not a request for your private device files.

Use the account support route and ask for a copy of the personal data connected with your account. Include the linked phone number and complete identity checks if requested. We then explain what can be provided under local law.

You can request a correction or removal through the account support route. Describe the specific detail and the reason for your request. We assess retention needs such as payment reconciliation or legal duties before confirming what action is possible.

Cookies can keep your session and preferences available when you move through the account area on mobile or desktop. You can manage them in your browser. If you disable required cookies, sign-in continuity or selected account functions may not work as expected.