Reference

How area188 protects your privacy data

Live Roulette, Aviator, Football Betting and QRIS wallet activity all touch your account data, so our Privacy Policy shows what we collect when you open an account and…

Account dataDANA recordsCookie choicesDevice sessions
area188 How area188 protects your privacy data
CONTACT ROUTES

Three ways to reach privacy support

Privacy questions need a clear channel, not a maze. We keep live chat, email and account message routes open for data access, correction, cookie or wallet-record requests.

Live chat Use live chat from 09:00 to 23:00 WIB when you need a quick privacy check. We may ask you to confirm your registered email or phone before discussing wallet records.
Email privacy desk Send privacy requests by email when you need account data access, correction or deletion handling. Include your username, contact channel and a short description of the record you want us to check.
Account message Open Menu > Account > Support from your device to send a privacy message while logged in. This route links your request to the current session and reduces identity checks.
DATA CONTROLS

Six controls around your account data

We treat privacy as an operating process that touches login, wallet, cookies, session history and support.

Account verification

When you create an account, we use your phone or email confirmation to link privacy requests to the right profile. This helps us avoid sending account data to an unverified contact.

Wallet records

DANA, OVO, GoPay and QRIS activity creates transaction references, timestamps and status records. We use those records to match deposits or withdrawals to your wallet and answer payment privacy questions.

Cookie choices

Cookies help keep your session active, remember basic preferences and measure page errors. You can adjust browser cookie settings, but some account tools may ask you to log in again.

Device sessions

Go to Menu > Account > Security > Active Sessions to check recent device access. If you see a device you do not recognise, contact us so we can review the session record.

Retention handling

Some records are kept while your account is active, while payment and security records may be retained for dispute handling. Deletion requests are assessed against account safety and local requirements.

Correction requests

If your email, phone or profile detail is wrong, send a correction request through logged-in support. We confirm account ownership before changing data that could affect login or wallet access.

Privacy questions before you join

Before you open an account, you should know how your data moves through our registration, wallet and support flow. These answers focus on privacy choices, access requests and security checks you may search for before sharing contact details or using DANA, OVO, GoPay or QRIS.

We ask for the account details needed to create and protect your login, usually a username, password, contact channel and verification step. Extra checks may apply if a wallet or security issue needs account matching.

We keep payment references so deposits, withdrawals and wallet questions can be matched to your account. The record usually includes status, time and payment rail, not unrelated private spending outside our wallet.

Yes. Contact us through logged-in support or email with your username and registered contact channel. We verify the request before sharing account data, because privacy access should only go to the account owner.

Cookies keep your login session working and help us spot page errors on mobile browsers. You can change cookie settings in your browser, but disabling them may require repeated login checks.

Open Menu > Account > Support while logged in and ask for a correction. We may request confirmation from your current contact channel before updating details that can affect login recovery.

We share only the details needed to process or trace wallet activity through DANA, OVO, GoPay or QRIS. We do not send game choices such as Live Roulette or Bingo to payment partners for unrelated use.

We keep request records long enough to show what was asked, how we verified it and what action we took. Retention may differ when payment disputes, account safety or rules that depend on local law apply.