Rujukan Laman

Legal Terms Before You Join

ar88 puts your account terms, privacy rules, cookie choices and Malaysia payment clauses in one place so you can read the legal position before you open your account.

Account termsPrivacy rightsCookie choicesMalaysia law
ar88 Legal Terms Before You Join
CONTACT PATHS

Three Legal Contact Paths

Legal questions need the right route, so we separate account access, privacy requests and payment-record checks before support replies. This helps us confirm who is asking, what policy area applies and which record should be examined. We will not ask for your password, full card details or private wallet PIN when handling a legal request. Use the matching contact path below so your message reaches the team that can act on it.

Team online

Account terms desk

Use this path when you need help reading account clauses, access rules or closure wording. Include your registered mobile number and the exact term you want us to explain.

Privacy request desk

Send privacy requests here when you want to view, correct or question personal data linked to your profile. We may ask for identity proof before changing account records.

Payment record desk

Choose this route for legal questions about Touch 'n Go, GrabPay, Boost dan FPX records. Share the transaction time, amount and wallet reference so we can trace it.

DATA PRACTICE

Six Ways We Handle Your Data

Our legal handling is built around clear records rather than vague promises. We keep account, wallet, device and contact details only for defined purposes such as access checks, payment matching, dispute handling…

Data we collect

We collect profile details, login activity, device signals and wallet references when needed for account operation, fraud checks, payment matching or legal response. We avoid asking for data that has no clear purpose.

Cookie handling

Cookies help keep sessions active, remember language choice and measure whether legal banners are seen. Marketing cookies, if used, are separated from required session cookies so consent choices stay clear.

Account security

When access looks unusual, we may hold account actions while we check login pattern, device match and payment history. This protects your records and helps prevent changes by the wrong person.

Retention periods

We keep records for as long as they are needed for account service, payment disputes, legal duties or security checks. When a record is no longer required, we remove or anonymise it.

Change requests

You may ask us to correct profile data, update contact details or explain why a record is retained. We verify your identity before making changes to legally relevant account records.

Payment verification

Touch 'n Go, GrabPay, Boost dan FPX activity may be checked against wallet ownership, bank routing and account name. These checks support withdrawal handling and help resolve payment disputes.

Legal Questions Before You Open Account

Read these answers before you open your account so you know how legal terms, privacy requests, cookie settings and payment records are handled. If your question is about access or eligibility, the answer depends on local law and availability where local law permits. For anything linked to your own records, contact support from the registered email or mobile number so we can verify you first.

The account terms cover eligibility, login use, wallet activity, withdrawal checks, dispute handling and closure rules. By opening an account, you agree to those terms where local law permits access.

Yes. Send a privacy request from your registered contact details and state what account data you want to see. We verify identity before sharing records to protect your account.

Contact the privacy request desk with the old detail, the corrected detail and supporting proof where needed. We may keep an audit record showing when the change was requested and completed.

Payment records help us match Touch 'n Go, GrabPay, Boost dan FPX activity, check withdrawal routing and answer disputes. Retention also supports legal duties tied to account and wallet activity.

Yes. Access may be restricted if local law does not permit use, identity checks fail, payment ownership is unclear or account activity raises security concerns. We explain the relevant route when possible.

Required cookies support login sessions, language settings and legal banner status. Optional cookies, where used, are handled separately so your consent choice can be recorded and changed later.

Use the legal contact path that matches the issue: account terms, privacy data or payment records. Include dates, references and screenshots where relevant, but never send passwords or wallet PINs.