Reference

Privacy Policy for Your armada Account

Our armada Privacy Policy explains how we collect, use and protect the details connected to your account, including contact data, device signals and wallet records.

Clear data purposesWallet record contextPhone verificationPolicy contact path
Explore Our Lobby Read FAQ
armada Privacy Policy for Your armada Account
CONTACT ROUTES

Ask About Privacy Policy Changes

A direct contact route helps you act on this Privacy Policy without searching through unrelated account pages. We can receive questions about stored details, a wallet record, a phone verification step or the removal of a permitted data use. Include the account phone number and a clear description of your request, but do not send a password or full payment credentials. When a receipt from DANA, OVO or QRIS needs checking, keep the reference visible and share only the portion support requests.

Team online

Account contact

Use the support path connected to your armada account to ask which personal details we hold or why a phone verification record is needed. We may ask you to confirm account ownership before discussing data, so another person cannot request changes using only your phone number.

Wallet record check

For a DANA, OVO, GoPay or QRIS receipt, send the transaction reference through the account support route. We use the reference to match the payment status, avoid exposing unrelated wallet details and explain whether the record can be corrected under this Privacy Policy.

Policy request

Ask us to correct, access or restrict a permitted use of your personal details by naming the request plainly. We will check your identity, assess any local-law requirement and reply through the contact route linked to your account rather than disclosing details in an open channel.

DATA PRACTICES

How armada Handles Your Details

We separate routine account operation from requests that need a closer identity check.

Account details

We use your account details to create access, send account-related responses and connect your requests with the correct record.

Device signals

Browser type, device signals and login timing can be recorded to identify unusual access and protect your account.

Cookies

Cookies can keep a session working, remember selected settings and help us understand whether a page loads correctly.

Payment records

A DANA, QRIS, bank transfer or virtual account transaction can create a reference, amount and status record needed to reconcile…

Retention controls

We keep personal data for as long as it supports account operation, fraud checks, dispute handling or a legal obligation.

Request ownership

A request to access, correct or delete data must come from the account owner or an authorised person.

Privacy Policy Answers for armada

These Privacy Policy answers focus on the questions you may have before opening an armada account or asking us to change stored details. We explain what connects to account access, how payment records are handled and which path to use when you need help. If your request involves eligibility or access in Indonesia, the outcome depends on local law and the details of your account.

The armada Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use each category, how we protect it, when we retain it and how you can request access or correction where local law permits.

Yes. The Privacy Policy covers the reference, status and related account details created when you use DANA or QRIS. We use those records to reconcile a receipt or wallet status. Share only the requested reference through account support, never a password or full wallet credential.

We use phone verification to confirm account ownership before access or a sensitive data request. Verification details can support account security and payment checks, including a query about GoPay or OVO. We limit access to personnel and processes that need the record for that purpose.

You can send a correction request through the support path connected to your account. State which detail is wrong and provide the account phone number so we can locate the record. We may verify ownership first, then assess the request under this Privacy Policy and local law.

You may request deletion where local law permits by contacting us through your account support route. We first confirm ownership and check whether a record is still needed for account security, payment reconciliation, dispute handling or a legal obligation. If retention applies, we explain the reason.

Cookies can keep your session active, remember settings and help us identify loading problems on a mobile browser. They do not let us read unrelated device files. Your browser controls cookies, although disabling some may affect login, wallet status or the path to the lobby.

Use the support path linked to your armada account and describe the request as access, correction, deletion or a question about a payment record. Include only necessary account context. We may ask for phone verification, and eligibility for a particular request depends on local law.

Related Pages

armada Indonesia About Us Account information Access guide FAQ