Reference

Privacy Policy for Your indoraja Account

Your indoraja Privacy Policy explains how we handle the details connected with your account, wallet status and device access.

Account dataWallet recordsDevice accessCookie choices
indoraja Privacy Policy for Your indoraja Account
CONTACT PATHS

Ask About Your Privacy Policy Rights

A clear contact path helps when you want to understand a data record rather than guess what happened.

Account privacy request Send a request through the account support path when you want a copy of personal details connected with your indoraja account. We may ask you to complete a phone verification step before discussing the record.
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, include its date and visible transaction reference. We use those details to check the account record without asking you to share your wallet password or full security code.
Correction or deletion Tell us which detail needs changing or which eligible record you want removed. We first confirm account ownership, then explain any retention reason that prevents immediate deletion, including an open payment or security check.
DATA PRACTICE

How We Handle Wallet And Device Data

We keep the Privacy Policy practical by linking each data type to a clear account task. Phone verification helps us confirm account access, wallet references help us trace a payment request, and…

Account creation

When you open an account, we handle the phone number and verification result needed to establish access. We do not ask for your password through a support message, and you should keep sign-in codes private.

Wallet references

A payment record may contain a method label such as DANA or QRIS, a reference, amount and status. We use those fields to match the request to your account and investigate a pending or reversed entry.

Browser cookies

Cookies can remember session state and selected preferences so the privacy page and account area load consistently. You can manage browser cookie settings, though changing them may interrupt sign-in or remove saved choices.

Device signals

We may read limited browser, operating system and connection signals to protect an account from unusual access. These signals are reviewed for security patterns, not used as a substitute for your phone verification.

Retention periods

We keep personal details only while they support account operation, payment tracing, security checks or a legal requirement. When a period ends, we remove, anonymise or restrict the record where the applicable process allows.

Policy changes

If our handling changes, we place the revised Privacy Policy on this page and update its wording before the change applies. Checking this page after a material update helps you see what changed and which choices remain available.

Privacy Policy Questions About indoraja

These Privacy Policy answers address the practical questions that come up before account access: what we collect, how wallet records are used, what a phone check means and how to contact us. They also explain the limits that can apply when a record must remain available for payment tracing or security. If your situation is different, send the account support request described above.

The indoraja Privacy Policy covers account details, phone verification, wallet references, browser cookies, device signals and contact requests. It explains why we use each category, how retention works and how you can ask for access, correction or eligible deletion.

Phone verification helps us connect an account request to the person controlling the sign-in route. It can also protect a Privacy Policy request from being disclosed to someone else. We will not ask you to reveal a password or private wallet code.

Yes. The Privacy Policy covers payment references linked to DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use method, reference and status details to match an account request and check a payment issue.

You can contact our account support path and request the personal details connected with your account. We may confirm ownership through the phone verification step, then explain what can be supplied and whether any security or payment record must remain restricted.

State which detail is inaccurate and provide the account reference that helps us locate it. After confirming ownership, we assess the correction under the Privacy Policy and update the eligible record. A payment reference may require a separate status check before editing.

Retention depends on why the record exists. Account and device details support access and security, while wallet references may be needed to trace a payment. We remove, anonymise or restrict records when the operational, security or legal period ends.

Access or eligibility depends on local law. The Privacy Policy does not change that condition. If you are unsure whether account access is available in your location, check the applicable local requirements before sending personal details or opening an account.