Rujukan Laman

Malaysia Legal Terms at metta888

metta888 keeps your legal terms in one place, so you can check how account records, access, and request handling work for Malaysia before you join.

Local law firstWritten recordsAccount checksCookie control
metta888 Malaysia Legal Terms at metta888
REQUEST CHANNELS

Where to Send Legal Requests

When you need a legal reply, use the channel that matches the request so we can verify it faster.

Email request Send the email linked to your account, the change you want, and the date you noticed the issue. We use those details to verify the request and answer in writing.
Live chat Use chat when you want a quick point on access, retention, or cookies. We can confirm the right path, then move the case to writing if the matter needs a record.
Web form The form is useful when you need to attach proof, ask for a copy of records, or submit a correction. It creates a dated trail and helps us track the next step.
DATA CARE

How We Handle Records and Cookies

We keep legal handling narrow. Only the details needed to open, verify, and service your account are stored, and we separate those records from casual site browsing where possible.

Data handling

We collect only the details needed to open, verify, and service your account, then restrict access to staff who need them for a legal task. That keeps the record set smaller and easier to audit.

Cookies

Cookies help us remember your session, device state, and language choice so the legal pages and account screens keep their place. You can clear them in your browser, but some session steps may ask you to sign in again.

Account security

When you change password, device, or contact details, we may ask for a second check before the edit lands. That extra step protects your account from unauthorised changes and gives you a clear record of the request.

Record retention

We keep request logs, transaction traces, and support replies only as long as needed for law, audit, and dispute handling. After that window, the records are removed or anonymised according to the record type.

Change requests

If you want a correction or deletion request, write from the email on file, say what must change, and attach proof when asked. We confirm the request in writing before any record is updated.

Contact trail

Every legal request gets a case trail so you can follow what we received, what we checked, and what happens next. That trail helps us keep replies consistent across email, chat, and the web form.

Questions About Your Legal Rights

If you need to check a rule, change account details, or ask how we store your records, start with the contact channel that matches the issue. We answer in writing, keep the case trail, and apply the local rule that governs your account when access is available under local law. That keeps the process clear when your request touches data, cookies, or access in Malaysia.

Access depends on local law and is available where local law permits. If your location is covered, you can open the account and use the legal pages; if not, the access limit stays in place.

We keep the details needed to verify you, process changes, and answer later queries, plus a log of key account actions. Less-needed records are removed or anonymised once the retention period ends.

Send the request from the email on file, say which detail is wrong, and attach proof if we ask for it. We confirm the change in writing before updating the record.

Yes. You can ask which cookies help the site remember session state, language choice, and security checks. You may clear them in your browser, but some account steps may ask you to sign in again.

Include your registered email, the account detail involved, and the date or screen where you noticed the issue. That lets us check the right record set without asking you to repeat the whole case.

Use email for written records, live chat for quick direction, or the web form when you need a dated submission with files attached. We route the message to the team that handles that request.

Extra checks help us confirm account ownership before a sensitive change lands, especially when a device, contact detail, or payment record is involved. That reduces mistakes and keeps the request history clear.