Reference

armada88 Privacy Policy For Your Account

Your account details, wallet records and device choices are explained clearly in the armada88 Privacy Policy.

ACCOUNT DATAWALLET RECORDSCOOKIE CHOICESCONTACT PATH
armada88 armada88 Privacy Policy For Your Account
CONTACT YOUR DATA TEAM

Get Help With A Privacy Request

A clear contact route helps when you want to ask about a record, correct an account detail or question a cookie choice.

Account access Use the account support path when your phone verification, login record or saved contact detail needs checking. We will ask for enough account evidence to confirm that the request comes from you.
Wallet records For DANA, OVO, GoPay or QRIS references, share the cashier date and payment reference rather than a wallet password. This lets us locate the correct record without requesting unnecessary credentials.
Privacy changes Ask us to correct, access or clarify personal data through the support contact shown in your account. Include the requested change and your registered contact so we can route it accurately.
ACCOUNT DATA PRACTICE

Account Security Beside QRIS Records

We handle Privacy Policy requests through the same account checks used before access to your lobby and wallet records.

What we collect

We may collect your registration contact, phone verification result, login events, device details and support messages. Payment records can include a method label and reference for DANA, QRIS or bank transfer matching.

Cookie choices

Cookies can keep an account session active and remember device preferences. If you want a cookie category explained or changed, contact us with the browser and account detail connected to your request.

Account protection

Phone verification helps us distinguish an account holder from an unknown login attempt. Never send a wallet password or one-time code in a support message; we do not need either to discuss policy.

Retention period

We keep account, payment and support records while they serve account operation, dispute handling or legal needs. When a record no longer serves those purposes, it is removed or anonymised.

Correction requests

You can ask us to correct a wrong email, phone detail or other account entry. We compare the request with your verified account path before making a change to the stored record.

Who receives requests

Privacy questions go to the support contact linked from your account, where our team can see the relevant policy route. Payment concerns remain tied to the cashier reference you provide.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we expect before you open an account: what is collected, how wallet records are matched, how device access works, and how to request a correction. Read the relevant answer first, then use the account support path if your situation needs a private check.

It covers registration details, phone verification, login and device events, cookies, support messages, payment references and retention. It also explains how to ask for access, correction or clarification about your stored data.

No. We use payment method labels and cashier references to match a request with your account. Do not send a DANA, OVO, GoPay or QRIS password to support.

Device and browser signals help us recognise unusual login activity, maintain a phone session and investigate access trouble. We may compare these signals with your verified account details during a support request.

Use the support contact shown inside your account and state that you want a copy or explanation of your stored data. Include your registered contact, then complete the account check we request.

Yes, you can ask us to correct a phone number, email or other registration entry. We verify the request against your account before changing the record, so the update stays connected to you.

We retain payment references while they support cashier matching, account support, disputes or legal needs. After that need ends, the record is removed or anonymised through our retention process.

Open the support path linked to your account and mention cookies, login history or phone verification. We will direct the request to the relevant Privacy Policy contact and ask for account evidence when needed.