Rujukan Laman

Privacy Policy Before You Join ar88

ar88 explains how your account, wallet, device and support data is handled before you open your account.

Malaysia data handlingAccount privacy choicesWallet record claritySupport contact paths
ar88 Privacy Policy Before You Join ar88
ACCOUNT HELP

Three Privacy Contact Paths

Privacy questions should reach the team that can read your account record and answer without exposing extra data. We may ask you to confirm account details before we discuss wallet records, login history, or identity checks. This keeps your request tied to the right account and helps us avoid sending private details to the wrong person.

Team online

Live chat privacy request

Use live chat when you need a quick privacy check on account data, login alerts, or wallet record wording. We verify your account first, then route the request to the team that can handle private data.

Email record request

Email support suits access, correction, or deletion requests that need written handling. Include your account name, registered contact detail, and the privacy topic, but do not send card images or unrelated files.

Wallet query channel

For Touch 'n Go, GrabPay, Boost dan FPX record questions, use the wallet query path. We compare transaction references with account logs and share only the details needed to answer your privacy concern.

DATA CARE

Six Ways We Handle Privacy

Privacy work is part of account operations, not a separate promise hidden away from the lobby.

Account data collection

We collect account details you provide, login data from your device, wallet references, and support messages. This helps us open your account, protect access, match payments, and respond to privacy requests.

Cookie controls

Cookies help remember sessions, language choices, security status, and basic site performance. You can adjust browser settings, but blocking required cookies may affect login, wallet access, or support forms.

Wallet record handling

Deposits and withdrawals through Touch 'n Go, GrabPay, Boost dan FPX create transaction records in your account. We use those records for reconciliation, fraud checks, support replies, and legal retention duties.

Security access limits

Only authorised staff may view private account records, and access is tied to work needs such as account checks, wallet queries, or support follow-up. Internal access logs help us review unusual activity.

Retention approach

We keep records only as long as needed for account service, dispute handling, security checks, and legal duties. When records are no longer required, we delete or anonymise them where our systems allow.

Correction requests

If your account details are outdated or inaccurate, contact support with the change you need. We may ask for verification before editing records so another person cannot alter your private account data.

Privacy Policy Questions For Your Account

These answers explain the privacy points we are asked about most often: what we collect, why we keep it, how wallet records work, and how you can request access or changes. If your concern involves account safety, we may verify you first before sharing any private details.

We collect the details needed to create and protect your account, including registration data, login records, device signals, wallet references, and support messages. We use this data for account access, security, payments, and service replies.

Wallet records may show Touch 'n Go, GrabPay, Boost dan FPX because those names help match deposits, withdrawals, and support queries. We use the records to confirm transactions and resolve privacy-related account questions.

Yes. Contact support with your account name and the data request you want us to check. We may verify your identity first, then share the account data we can provide under applicable law.

Send the corrected detail through the support path connected to your account. We may request verification before making changes, especially for contact details, wallet-related records, or data used for security checks.

We keep account, wallet, login, and support records for as long as needed to run the service, answer disputes, meet legal duties, and protect accounts. When no longer needed, records are removed or anonymised where possible.

Cookies help keep your session active, remember site settings, and support account security. You can adjust browser controls, but some required cookies are needed for login, wallet access, and privacy request forms.

Start with live chat for quick routing or email support for written requests. If your concern involves wallet records, mention the payment method and transaction reference so we can locate the correct account record.