Rujukan Laman

Legal terms for Malaysia account access

Clear legal terms, Malaysian payment context, and direct support routes sit on this page so you can understand how your account, wallet records, and data requests are handled.

Malaysia legal accessTouch 'n Go contextGrabPay wallet checksBoost dan FPX records
max885 Legal terms for Malaysia account access
CONTACT ROUTES

Legal help through direct contact paths

Legal questions need a clear route, not a generic reply. Use the channel that matches your request so we can locate your account record, payment reference, cookie setting, or access concern with…

Account terms help Message support when you need account terms explained, including access status, login blocks, or rule updates. Include your account ID and the date of the issue so we can check the right record.
Payment record checks Send wallet queries with the payment name, reference number, and amount shown in your bank or e-wallet app. We use those details to match Touch 'n Go, GrabPay, Boost dan FPX records.
Data request channel Use the privacy contact path for data access, correction, or deletion requests. We may need identity confirmation before releasing or changing records, especially where wallet logs or account security checks are involved.
DATA CARE

How we handle legal and data duties

Our legal process is built around records we can verify: account details, login events, device signals, payment references, cookie choices, and support history.

Account data

We collect account details you provide, login timestamps, device signals, and contact history. These records help us confirm ownership, apply legal terms, answer account queries, and investigate suspicious access attempts.

Cookie use

Cookies help keep sessions active, remember basic preferences, and measure page function. You can adjust browser settings, but some account actions may require session cookies to keep access secure.

Wallet records

Touch 'n Go, GrabPay, Boost dan FPX transactions create references we use for reconciliation, refund checks, and dispute handling. We do not ask for your e-wallet password or banking login details.

Security checks

If an account shows unusual login behaviour, we may pause certain actions while ownership is confirmed. This can include checking identity details, device history, payment references, or support conversations.

Retention periods

Records are kept for the time needed to run the account, answer disputes, meet legal requests, and maintain payment history. When retention is no longer needed, we remove or anonymise data where practical.

Change requests

You can ask to update inaccurate account details or request a copy of personal data we hold. We verify the request first so records are not changed by someone else.

Questions about legal account handling

These answers explain how our legal terms apply to account access, data requests, cookies, payments, and support contact. They are written for Malaysia access and should be read with the condition that eligibility depends on local law. If your situation involves a live account record, contact us so we can check the exact details.

Access depends on local law and is available only where local law permits. We may also apply account checks before allowing wallet actions, support changes, or access to restricted account areas.

We keep account details you submit, login records, device signals, payment references, cookie preferences, and support conversations. These records help us manage access, answer disputes, and process data requests.

Contact the privacy route with your account ID and a clear request. We may ask you to confirm ownership before sharing records, correcting details, or taking action on deletion requests.

Wallet checks may happen when a Touch 'n Go, GrabPay, Boost dan FPX reference needs matching, a refund question is raised, or account activity requires extra verification under our legal terms.

Yes, you can request a correction through support or the privacy route. We verify ownership first, then update records where the request is valid and legal retention duties do not prevent the change.

Cookies support login sessions, basic preferences, and page function checks. You can manage them through your browser, but some secure account actions may not work correctly without required session cookies.

Use support for account-term questions and the privacy route for data requests. Include your account ID, payment reference if relevant, and a short description so we can find the correct record.