Rujukan Laman

Legal Terms Before You Join sar288

Clear account terms, Malaysia-aware access wording, and a direct data request path sit on this page so you know how our legal rules apply before you open an…

Malaysia law awareAccount termsData request pathTouch 'n Go context
sar288 Legal Terms Before You Join sar288
CONTACT ROUTES

Three Contact Paths For Legal Matters

Legal questions should reach the right desk, not a general chat thread that loses context.

Live chat legal queue Use live chat when you need to ask which legal route fits your issue.
Email for written records Send written legal requests by email when you need a dated trail.
Account verification desk Use the verification desk when a legal request involves account ownership, wallet records, or…
DATA HANDLING

Six Ways We Handle Legal Requests

Legal handling is tied to evidence, timing, and account ownership. We check the account record before making changes, limit the data we ask for, and keep request trails so your case can…

Data fields

We ask for account details that help confirm who is making the request, such as registered mobile number, account ID, email, and relevant dates. Extra documents are requested only when the case needs stronger matching.

Cookie choices

Cookies support login sessions, fraud checks, and page settings. If you restrict them in your browser, some account actions may need another verification step before we can process legal or data requests.

Account security

Password resets, device changes, and access disputes are checked against account records before changes are made. This protects your wallet trail and reduces the risk of another person controlling your legal request.

Retention rules

We keep different records for different periods depending on account activity, transaction checks, dispute handling, and legal duties. When a record is no longer needed, we remove it or reduce it where suitable.

Correction requests

You can ask us to correct contact details or account data that is inaccurate. We may need proof that the account belongs to you before changing fields tied to payments or identity checks.

Escalation path

If your legal matter needs more checking, support can escalate it to the account and compliance team. We keep the request history so you do not have to repeat every detail again.

Legal Questions Before Account Opening

This section answers common legal questions in plain language before you open your account. It covers access, data requests, wallet records, cookies, and how to contact us when something needs correction. The answers are written for Malaysia readers, but eligibility and access still depend on local law and are available where local law permits. For account-specific matters, contact support with enough detail to identify your record.

Your account is governed by the terms shown on our site, any privacy and cookie wording linked to it, and rules displayed during account use. Access depends on local law and is available where local law permits.

Yes, you can ask what account data we hold and how it is used. We first verify that the request comes from the account holder, then respond through a suitable contact route.

Those payment names help us match transaction trails with your account. We may check receipt references, wallet timing, account ownership, and support messages when handling access disputes, correction requests, or payment record questions.

Contact support and explain which detail needs correction. We may ask for account matching data before changing mobile numbers, email addresses, or wallet-linked fields, especially when the change could affect account access.

Cookies help keep sessions consistent, remember settings, and detect unusual access. If you block them, some legal or account actions may require added checks before we can confirm the request.

You can contact us about account closure or record removal. Some records may need to be kept for legal, security, transaction, or dispute reasons before they can be deleted or reduced.

Start with support and ask for the legal request route. Provide your account ID, registered contact, the issue date, and a short summary so we can direct it to the correct team.