Rujukan Laman

Privacy Policy for Your mbet88 Account

mbet88 keeps your account data, cookie choices, payment records and support messages under one clear Privacy Policy, so you know what we collect before you open the lobby…

Malaysia data handlingCookie choicesPayment privacyAccount request route
mbet88 Privacy Policy for Your mbet88 Account
CONTACT ROUTES

Three Privacy Contact Paths

Privacy requests should reach the team that can check your account record, confirm your identity and answer without exposing data to the wrong person.

Live chat privacy handoff Start with live chat when you need a privacy request logged quickly. Our agent will confirm your account handle, open the privacy ticket, and tell you which proof is needed before data is shared or changed.
Email request trail Use email for access, correction, deletion or cookie questions that need a written trail. We match the sender against your account contact, then reply with the next step and expected handling time.
Account message reply When we contact you about a material privacy change, you can reply through the account message thread. This keeps the request tied to your profile and reduces the chance of mistaken disclosure.
DATA CONTROLS

Six Controls Behind This Policy

A privacy page only matters if the daily account process follows it. We apply access checks, logging, storage rules and staff permissions around the data that enters the wallet, lobby, chat and…

Account data collection

We collect the data needed to create and run your account, such as contact details, login records, device signals and transaction references. We avoid asking for extra data when the same check can be completed another way.

Cookie and device signals

Cookies help keep your session active, remember basic choices and spot unusual account access. You can change browser cookie settings, but some account checks may need cookies to keep the login flow working.

Payment record handling

Touch 'n Go, GrabPay, Boost dan FPX references are used to match deposits, check withdrawals and resolve wallet queries. We store transaction records with account logs so support can trace a payment without exposing full banking data.

Staff access control

Only assigned teams can view personal data, and access depends on their role. Support can see what is needed for your ticket, while deeper wallet or identity checks require tighter permission and internal logging.

Retention and deletion

We keep account records for the time needed to run your account, handle disputes, prevent misuse and meet legal duties. When data is no longer needed, we delete it or separate it from direct account identity.

Change request handling

If your name, phone, email or payment reference is wrong, contact us from the account channel already on file. We may request proof before making changes so another person cannot alter your record.

Privacy Questions Before You Join

These answers cover the privacy points we are asked about most before an account is opened: what we collect, why payment records matter, how cookies behave, who can see account data and how you can ask for a copy or correction.

We collect data needed to create and run your account, including contact details, login records, device signals, wallet references and support messages. We use it for account access, payment matching, safety checks and request handling.

Payment records help us match deposits and withdrawals through Touch 'n Go, GrabPay, Boost dan FPX. They also let support trace a missing wallet entry without asking you to repeat the same transaction proof.

Yes. Contact us through live chat or email using the contact method linked to your account. We will verify your identity, gather the account data we can share, and explain any legal reason for holding back a record.

Cookies keep your session active, remember basic site choices and help detect unusual login behaviour. You can manage cookies through your browser, but blocking some cookies may affect account access or wallet checks.

We keep records while your account is active and for the period needed to resolve disputes, meet legal duties and prevent misuse. When those reasons end, we delete data or separate it from direct identity.

Access is limited by role. Support sees the data needed to answer your ticket, wallet teams see payment references, and technical teams review logs only when needed for account access or service checks.

Send a correction request from your account contact channel and state which record is wrong. We may ask for proof before editing or deleting data, especially when the change affects wallet access or identity checks.