Rujukan Laman

Your Privacy Policy For Malaysia

Our Privacy Policy explains what account, device, payment and support data we collect when you open an alibet88 account, why we use it, and how you can ask…

Malaysia data scopeCookie choicesPayment record usePrivacy request path
alibet88 Your Privacy Policy For Malaysia
CONTACT ROUTES

Privacy Help Through Local Channels

Privacy questions should reach the team that can act on account records, not a general inbox with no context.

Account centre Use the account centre to check the email, phone number and profile details linked to your account. If a field is wrong, send a correction request so we can assess the change against security records.
Live chat privacy check Live chat can help you confirm which records are needed before we process a privacy request. For account safety, the agent may ask for recent sign-in or wallet details before sharing any data summary.
Email privacy desk Email is suitable for access, correction, deletion or cookie questions that need a written trail. Include your account ID, contact email and the request type, but do not send card or bank passwords.
ACCOUNT SAFEGUARDS

How We Protect Account Data

We handle privacy as part of account operations, not as a separate afterthought. Each request is checked against the account record, wallet activity and support history before we answer.

Data minimisation

We ask for data that has a clear account purpose, such as identity checks, wallet matching, support replies and security screening. Extra documents are requested only when the existing record cannot verify the request safely.

Cookie controls

Cookies help keep your session active, remember device choices and detect unusual access patterns. You can change browser settings, but some account functions may need essential cookies to keep sign-in and wallet pages working.

Security checks

We monitor sign-in location, device signals and failed password attempts to reduce account misuse. If activity looks unusual, we may pause sensitive changes until you confirm ownership through a supported contact route.

Payment privacy

Touch 'n Go, GrabPay, Boost dan FPX references are stored as transaction records, not as full wallet passwords. We use them to match deposits, support withdrawal checks and resolve account disputes.

Retention rules

Some records are kept longer because finance, security or legal duties require an audit trail. When those duties end, we delete, anonymise or separate the data from active account use where possible.

Request handling

Your privacy request is logged with the date, channel and account ID so we can track the reply. We may decline a request if another law requires us to keep certain records.

Privacy Questions Before You Join

These answers explain how the Privacy Policy affects your account before and after you join. They cover data collection, payment records, cookies, access requests and correction paths in plain wording. If your situation involves a specific transaction or identity check, contact us through the account centre so we can look at the exact record tied to your profile.

We collect account details such as your name, contact data, sign-in records, device signals and wallet references. We also keep support messages and transaction logs needed to operate the account and answer privacy requests.

Payment records help us match Touch 'n Go, GrabPay, Boost dan FPX transactions to the correct wallet. They also support withdrawal checks, dispute handling and finance records required under applicable rules.

Yes. Send an access request through email or the account centre with your account ID and contact email. We will verify ownership first, then provide the data summary we can share under applicable law.

Use the account centre or contact support with the field that needs correction and proof that matches your account. We check the request against security records before changing phone, email or identity details.

Cookies support sign-in, language choices, security checks and session continuity. You can manage them in your browser, but blocking essential cookies may affect account pages, wallet access or privacy request forms.

You can ask for deletion of eligible records. Some data may need to stay for finance, legal, security or dispute reasons, and we will explain which records cannot be removed yet.

We may share limited fields with payment partners, security service providers, support tools or authorities when required. Each sharing step is tied to account operation, fraud checks, legal duties or your direct request.