Reference

Open armorbet78 with clearer privacy control

DANA, OVO, GoPay and QRIS wallet checks, device sign-ins, and lobby activity all create account data, so our Privacy Policy explains what we collect and why.

Indonesia account dataDANA and OVO recordsGoPay and QRIS checksDevice sign-in logs
armorbet78 Open armorbet78 with clearer privacy control
CONTACT ROUTES

Check privacy help before account changes

Privacy questions should reach the team that can see your account trail without asking you to repeat private details in public. Use the contact method linked to your login whenever possible, then include the account phone number, payment rail involved, and the date of the event you want us to check.

Team online

Live chat privacy desk

Message us from the logged-in chat between 09:00 and 23:00 WIB. We can confirm your account, check recent device access, and open a privacy case without asking for your wallet PIN or full card data.

Email data request

Send privacy requests from the email address on your account. Include your username, phone number, and whether the issue concerns DANA, OVO, GoPay, QRIS, cookies, device access, or a past support chat.

Account menu path

Use Account > Security > Privacy Request when you can still sign in. That path attaches your account ID, recent device label, and login time, which helps us handle corrections or access requests faster.

DATA HANDLING

Browse the privacy controls we use

We treat privacy as part of daily account operations, not as a separate page nobody reads.

Account details

We collect your name, phone number, email address, login ID, and password data needed to run your account. When you change these details, we may keep a timestamp so disputes can be traced correctly.

Payment records

DANA, OVO, GoPay and QRIS activity is stored as transaction references, wallet labels, amounts, status updates, and timing data. We use those records to match deposits, withdrawals, failed payments, refunds, and support questions.

Device and location checks

We record browser type, device label, IP address, and login time when you access the site. If a new device appears, we may ask for confirmation before allowing sensitive account changes.

Cookies and sessions

Cookies keep you signed in, remember language choices, and help us detect repeated failed logins. You can clear cookies in your browser, but doing so may require a new sign-in step.

Retention and deletion

We keep account and transaction records only as long as needed for service, security, dispute handling, and legal duties. When data is no longer needed, we delete it or detach it from direct account use.

Request handling

You can ask to access, correct, or delete eligible account data through live chat, email, or Account > Security > Privacy Request. We may confirm your identity before changing sensitive records.

Get answers on your privacy choices

These answers focus on the data we handle while you use your account, wallet, support channels, and lobby pages. If your case involves a specific payment or login event, send the date, device type, and payment method so we can trace the right record.

We collect the details needed to create and protect your account, such as your name, phone number, email address, username, password data, device record, IP address, and account activity timestamps.

We store payment references, status updates, wallet labels, timing data, and transaction amounts so deposits, withdrawals, failed transfers, refunds, and support cases can be matched to the correct account.

Yes. Send the request from your account email or use Account > Security > Privacy Request after signing in. We may verify your phone number or recent login before sharing account data.

Cookies help keep your session active, remember basic preferences, and detect unusual sign-in behaviour. You can clear them in your browser settings, but you may need to sign in again afterward.

Go to Account > Profile when you can sign in, or contact live chat from 09:00 to 23:00 WIB. We may ask you to confirm recent payment or device details before changing contact data.

We share only the data needed to process or verify a transaction, such as payment reference, amount, timing, and status. We do not ask you to send wallet PINs through chat or email.

We keep chat records, device logs, and security events for service, dispute handling, and account protection. When records are no longer needed, we delete them or separate them from direct account identity.