Rujukan Laman

club888 Privacy Policy for Malaysia

This page explains how club888 handles the details attached to your account, device, and payment activity.

Data useCookiesSecurity checksRequest changes
club888 club888 Privacy Policy for Malaysia
CONTACT ROUTES

Where to Reach Us

If you need a copy, correction, or a question answered about how a record was handled, use the contact path that fits the request.

Privacy email Send a written request when you want a copy, a correction, or an account…
Live chat Use chat for faster help with cookies, device access, or a question about how…
Postal route Post a formal request if you need a paper trail for a privacy change.
DATA HANDLING

How We Handle Your Data

Our privacy handling is built around three habits: collect only what the account needs, keep it only as long as the purpose lasts, and let you ask for changes through a clear…

Data only for purpose

We collect account, device, and transaction details only for the task in front of us: access, verification, support, and record keeping. Extra fields are avoided unless a rule or dispute makes them necessary.

Cookie control

Cookies keep your session live, remember language choice, and reduce repeated checks on each page load. You can change browser settings at any time, though some screens may ask again or load with fewer saved preferences.

Security checks

Passwords, session flags, and device signals help us spot unusual access. If a login looks wrong, we may pause it and ask for confirmation before the account opens again.

Transaction records

Touch 'n Go, GrabPay, Boost dan FPX records are tied to your account history so we can reconcile amounts, trace failed payments, and answer disputes with a clear audit trail.

Retention window

We keep records only while they serve the purpose collected, then delete, anonymise, or archive them under access control. Some records stay longer when a complaint, audit, or legal duty requires it.

Your request path

You may ask for a copy, correction, or deletion of eligible data by reaching the contact paths below. We verify identity before acting so changes land on the right account.

Privacy Questions You May Ask

These answers focus on the parts that matter most: what we store, why we keep it, how you can ask for a change, and when a request may need a local law check. If your account record needs a correction, we use the contact path that matches the request and verify the details before we act.

We keep the details you enter on your account, the device and browser data needed for access, and transaction references tied to deposits or withdrawals. We avoid collecting extra fields that do not help with those tasks.

Cookies remember session state, language choice, and whether you have already seen a notice. If you turn them off, some pages may ask again or lose a few saved settings, but the core account can still load.

We keep personal data only for the purpose that created it, then remove, mask, or archive it. Some records stay longer when a dispute, audit, or legal duty needs a longer trail.

Yes. Send the request through the contact path below, and we will verify the account before making any change. We can correct details or share a copy where local law allows.

Only staff who need the record for access, support, payment reconciliation, security, or legal duty can reach it. We limit access by role so the data stays in the smallest useful circle.

The policy still applies, but any access or eligibility question depends on local law and is available where local law permits. We keep the same data-handling rules for the account you use.

Use email for written requests, chat for account checks, or post for formal notices. Add your account email and the change you want so we can route it without delay.