Reference

armada888 Privacy Policy Explained

armada888 keeps its Privacy Policy practical: we explain what account details, device signals and wallet records we use, why we need them, and how you can ask about…

Account dataWallet recordsDevice choicesPolicy requests
armada888 armada888 Privacy Policy Explained
CONTACT OPTIONS

Reach Our Privacy Support Path

A clear contact route helps when you want to ask about Privacy Policy handling rather than solve a lobby question.

Account request Use our account support channel to ask which personal details are linked to your profile, including phone verification status and sign-in records.
Wallet query For DANA, OVO, GoPay or QRIS questions, include the receipt or status reference so we can separate your payment record from another account.
Correction path Tell us which detail needs changing and why. We may request an account check before updating contact, verification or wallet-related records.
DATA HANDLING

Explore How We Handle Your Records

Privacy Policy decisions are tied to real account events, not broad guesses about you. We separate sign-in activity from payment references, limit internal access to work needs, and use account checks before…

Collected details

We may receive your name or contact detail, phone verification result, account activity, device information and payment references created during DANA, OVO, GoPay or QRIS actions.

Use of records

We use these details to open and protect your account, match a cashier event, respond to Privacy Policy questions and identify activity that needs an account check.

Cookies and storage

Cookies or similar browser storage may remember sign-in choices, language settings or session needs. You can review browser controls, though changing them may affect account access.

Account security

Phone verification, sign-in events and device signals help us assess whether an access request matches your account. Never share your password or verification code with another person.

Retention approach

We retain records only while needed for the stated account, security, support or payment purpose, unless a longer period depends on local law or a valid dispute.

Change requests

You can ask us to access, correct or remove eligible personal details through support. We confirm the account first and explain any record that cannot be removed.

Browse Privacy Policy Answers

These Privacy Policy answers focus on the account steps Indonesian customers ask about most. If your situation involves a particular device, phone verification event or wallet receipt, mention that detail when you contact us so our reply can address the correct record.

The armada888 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer.

We use phone verification to connect an access request with the correct account and reduce mistaken account discussions. It can also help us investigate unusual sign-in activity or a wallet status question.

Yes. The Privacy Policy includes payment references and status details created when you use DANA or QRIS. Similar records may apply to OVO, GoPay, bank transfer and virtual account steps.

Contact our support channel with the phone or account detail connected to your profile and ask for a data access request. We confirm ownership before discussing records linked to that account.

Yes, you can request a correction through support and identify the detail that is wrong. We may ask for an account check, then explain whether the record can be changed.

Retention varies by record type and purpose. Account, security, support and payment references may be kept while needed, or longer where local law permits or a valid dispute requires.

Yes. Some access, correction or deletion requests depend on local law. Where local law permits, we explain the available option, the identity check and any reason a record must remain.