Reference

Privacy Policy for Your rupiah 126 Account

Your rupiah 126 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or use DANA and QRIS.

Account dataWallet recordsCookie choicesAccess requests
rupiah 126 Privacy Policy for Your rupiah 126 Account
SUPPORT PATH

Where Your Privacy Questions Go

A clear support route helps when your Privacy Policy question concerns a login event, wallet record or device cookie.

Data access request Ask us for the personal data connected to your account, including sign-in records and…
Correction request If your phone detail, contact record or verification status is wrong, describe the exact…
Wallet privacy help For DANA, OVO, GoPay, QRIS or bank transfer questions, include the transaction reference and…
SECURITY PRACTICE

Your Data Choices Inside rupiah 126

We treat the Privacy Policy as an operating process, not a label placed below the account form.

Data collection

We collect contact details, account activity, device signals and verification results when those records support sign-in, security or payment matching.

Cookie controls

Cookies help keep your session active and remember selected settings.

Account security

We use account contact checks, sign-in records and unusual-device signals to reduce unauthorised access.

Retention period

Payment references, account events and support messages remain while they serve account security, reconciliation or legal duties.

Your data rights

You can ask what personal data we hold, request a correction, object to a permitted use or ask for removal.

Policy contact

Use the support path inside your account for a Privacy Policy request.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the searches we receive before an account is opened. We explain the data connected to DANA, QRIS, sign-in devices and account verification in plain terms, while keeping the request path practical. If an answer does not settle your case, send the account contact detail and the specific record you want checked through support. Access and eligibility depend on local law, including whether a service or request is available in your region.

It covers personal data used for account creation, sign-in security, verification, payment matching, cookies and support requests. It also explains retention and your available data requests. The policy applies when you use a mobile browser or desktop session where local law permits.

No. We may store a payment reference, selected rail and status for DANA, OVO, GoPay, QRIS, bank transfer or virtual account reconciliation. We do not need your wallet password. Share a receipt reference only through the account support path.

Use the support path inside your account and ask for a data access request. Include the contact detail linked to your account and identify the record, such as a sign-in event or payment reference. We verify ownership before sending account-specific data.

Yes, you can request correction or removal of eligible personal data through support. Tell us which field or record is involved. Some payment, security or legal records may need to remain for the required period before removal or anonymisation.

Cookies can keep a browser session active and remember selected settings. Clearing cookies on your phone or desktop may sign you out and remove those settings from that browser. We may still retain the account records needed for security and payment matching.

We may use your contact detail, verification status, sign-in time, device signals and account events to identify unusual access. These checks help protect the account without requiring your DANA, OVO or GoPay wallet password.

Yes. Access to the lobby, account eligibility and some data requests depends on local law. We will explain if a legal, security or payment-retention duty limits your request, and we will use the support path to identify the applicable next step.