Rujukan Laman

Open manu888de Legal Terms for Malaysia

We set out how account access, data use, and request handling work on manu888de, with clear limits for Malaysia and any other place where local law permits access.

MalaysiaLocal lawAccount termsData use

Browse The Lobby Read FAQ

Explore Jurisdiction Rules and Access

manu888de Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

We apply the local rule set first. If a requirement in Malaysia differs from a rule in another place, the stricter rule governs your access, record keeping, and request handling. When your account activity touches Touch 'n Go, GrabPay, Boost dan FPX, we keep the transaction

1
trail only as long as we need it for settlement checks, dispute handling, fraud checks, and the legal period that applies. Access stays available only where local law permits, and some functions may pause until identity or eligibility checks are complete. We do not use legal
2
requests for unrelated profiling, and we answer each question in plain English tied to the account record that raised it. If you ask for a correction, copy, or explanation, we verify the request against your registered details before we act, then confirm the result through the
3
same channel. Where a local rule conflicts with a general one, we follow the local rule for the matter at hand and keep the response path clear, dated, and attached to your record.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT ROUTES

Open a Legal Contact Path

When you need a legal clarification, we keep the contact path plain. Send the issue from your registered email, include the page, date, or account detail it touches, and we will route…

Registered email Send the question from the email attached to your account, then include the page, date, or action you want us to examine. That helps us tie the request to the right record without mixing it with another profile.

In-account message Use the message path inside your account when the matter touches access, data use, or a change to your details. It keeps the thread in one place and lets us match it to the same login history.

Escalation log If the matter needs a second look, we keep the reply chain and hand it to a senior agent who can confirm the rule that applies. You get a clear next step instead of a vague reply.

DATA COOKIES SECURITY

Browse Data Cookies and Security

We treat legal requests as account records, not loose messages. Cookies remember session state, language choice, and whether you have already seen a notice, while access logs and device signals help us…

Data handling

We only use account details, contact details, and device signals needed to run access, answer legal requests, manage disputes, and keep records in order. We do not turn those records into unrelated targeting or social sharing.

Cookies

Cookies remember session state, language choice, and whether you have already seen a notice so the legal pages load cleanly on return. You can clear them in your browser, although some settings may reset.

Account security

Before we release account changes or copy records, we may ask for a password check or a fresh code. That extra step stops another person from changing your legal details without consent.

Retention

Access logs, request history, and verification records stay only as long as we need them for local law, dispute handling, and system checks. After that, we remove or anonymise them under our retention schedule.

Request changes

If your name, contact details, or consent choices need updating, send the correction from your registered address and we will verify the match before making the edit or noting a refusal where the law requires it.

Contact trail

We keep the reply thread linked to your account so you can trace the result later. If a request needs more time, we say what is missing and which channel to use next.

Switch to Common Legal Questions

These questions cover the parts people ask about most: what data we keep, how long we keep it, how to ask for a correction, and how access works when local law changes. We keep the answers tied to account records, so you can see which request belongs to which profile. When a question affects identity or activity history, we may ask for a fresh verification step before we change anything.

You can ask us to correct contact details, update consent choices, or explain a record tied to your account. We verify identity first, then make the change or tell you why a local rule blocks it.

We use account details, contact details, device signals, and request history only to run access, answer legal requests, manage disputes, and keep records in order. We do not turn those records into unrelated targeting.

We keep records for the period needed by local law, dispute handling, and audit checks, so the file does not stay longer than needed. After that period ends, we remove or anonymise them under our retention schedule.

Yes. Send the request from your registered email and name the account details you want to see. After we confirm identity, we provide the record allowed by law or explain any limit.

If local law changes, we adjust access and related handling to match the new rule set. That may affect what we can show, store, or process for your account.

Use the registered email or the in-account message path, and include the legal topic in the subject line. That sends your request to the right queue and keeps the thread easy to trace.

Open manu888de Legal Terms for Malaysia

Open a Legal Contact Path

Browse Data Cookies and Security

Data handling

Cookies

Account security

Retention

Request changes

Contact trail

Switch to Common Legal Questions

01 What can I ask you to change?

02 How do you use my account data?

03 How long do you keep records?

04 Can I ask for a copy of my data?

05 What happens if local law changes?

06 How do I reach the right team?

Related Pages