Reference

armada88 Privacy Policy For Your Account

The armada88 Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and contact our support route.

Clear data purposesWallet details explainedAccount access choices

Browse Our Lobby Read FAQ

Open The Privacy Policy Before Access

armada88 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies to the account path from phone verification through lobby access and wallet activity. We collect details needed to create and protect your account, confirm payment status, respond to requests, and identify unusual access. A DANA, OVO, GoPay or QRIS transaction may create

1
payment references, while bank transfer and virtual account records help us match a deposit or withdrawal request. We do not describe access as universal: where local law permits, you can use the account and request the rights set out here. If a section is unclear, use
2
the support route shown in your account and include the email or phone number linked to your profile. We may update this policy when our data practices change, with the current version kept on this page.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST SUPPORT

Check armada88 Help For Privacy Requests

Privacy questions should reach us through the account support route rather than a public message. This keeps your request connected to the correct profile and limits exposure of sensitive details. You can ask about a data copy, a correction, a deletion request, or a wallet record, while access remains subject to local law and account checks.

Team online

Account route

Open the support area after login and select a privacy request. Include your registered phone number only inside the secure account path, not in an open comment or public post.

Wallet query

For DANA, OVO, GoPay or QRIS records, mention the transaction date and payment reference. We use those details to locate the correct account event without asking you to share a wallet password.

Access issue

If phone verification or a device check blocks your request, explain the step shown on screen. Our support route can connect the access problem with the relevant Privacy Policy question.

DATA CONTROLS

Switch Devices With Policy Control

We keep the Privacy Policy practical by linking each data purpose to an account action you can recognise.

Account details

When you open an account, we may collect your phone number and basic profile details so we can complete verification, connect support replies to you, and maintain the correct account record.

Payment references

A DANA, OVO, GoPay or QRIS payment can leave a reference, amount and status in our records. Bank transfer and virtual account entries are handled for matching and reconciliation.

Cookies

Cookies can remember sign-in preferences, language choices and page settings. You can manage cookie behaviour through your browser, although some account steps may not work without required cookies.

Device security

A change from mobile to desktop may trigger an additional account check. We use device and sign-in signals to help detect unusual access, not to replace your phone verification step.

Retention period

We retain account, payment and support records for the periods needed to operate the service, resolve disputes and meet applicable legal duties. The current Privacy Policy describes the relevant purpose.

Change request

To correct a detail, ask for a copy, or request removal where available, contact us through the secure account support route. We may verify ownership before making any change.

Browse Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we most often expect before account access. They cover account data, cookies, payment references, device checks and requests for changes. If your situation involves a specific DANA, QRIS, OVO, GoPay, bank transfer or virtual account record, include its reference through the secure support route.

It covers data collected during account opening, phone verification, sign-in, payment activity, cookie use, support requests and device checks. It also explains retention, security measures and the requests available to you.

Phone verification helps connect the account to the correct contact detail and protects access when you sign in from a new device. It also helps us confirm ownership before handling a privacy request.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS activity may create payment references and status records. Bank transfer and virtual account details may be used for matching.

Use the secure support route after login and ask for an account data copy. State the phone number linked to your profile, then complete any ownership check required before we respond.

Yes, you can request a correction through account support. Tell us which detail is wrong and what it should say. We may request verification before changing profile, contact or payment records.

Cookies can remember selected settings and support parts of the sign-in path. Browser controls let you manage them, but disabling required cookies may interrupt phone verification or account access.

Yes. Available access, correction, deletion and related requests depend on local law. Where local law permits, contact us through the account support route so we can assess your request.

armada88 Privacy Policy For Your Account

Check armada88 Help For Privacy Requests

Account route

Wallet query

Access issue

Switch Devices With Policy Control

Account details

Payment references

Cookies

Device security

Retention period

Change request

Browse Privacy Policy Answers For Your Account

01 What does the armada88 Privacy Policy cover?

02 Why does armada88 ask for phone verification?

03 Does the Privacy Policy mention DANA and QRIS data?

04 How can I request a copy of my account data?

05 Can I ask armada88 to correct my details?

06 How do cookies affect my armada88 account?

07 Does access to my data depend on local law?

Related Pages