Rujukan Laman

Privacy Policy for Malaysia accounts

Our Privacy Policy sets out what data we collect when you open an account, enter the lobby, use Touch 'n Go, GrabPay, Boost dan FPX, or ask support…

Malaysia data wordingCookie choicesAccount request channelPayment record context
chealse888 Privacy Policy for Malaysia accounts
PRIVACY CONTACTS

Three privacy contact paths

Privacy questions should reach the team that can check your account record without asking you to repeat sensitive details.

Live chat privacy help Use live chat when you need a quick explanation of cookies, recent login data…
Email data requests Send an email when you want access to your account data, a correction, or…
Wallet privacy checks Contact wallet support when a Touch 'n Go, GrabPay, Boost dan FPX reference appears…
DATA HANDLING CHECKS

Six data practices behind the policy

Our Privacy Policy is written around the account actions you actually take: opening an account, logging in, moving through the lobby, using local payments, and asking support for help.

Account data collection

We collect the details needed to create and maintain your account, such as contact data, login credentials, device signals, and verification records. The policy explains why each category is used and who handles it internally.

Cookie control

Cookies help remember session status, language choice, and account safety prompts. Where a cookie supports analytics or preference storage, the Privacy Policy explains its purpose so you can understand what is being recorded.

Session and game records

When you open Free Bet Blackjack, Dragon Hatch, Football Studio, or European Roulette, we keep session records that link actions to your account. These records help resolve disputes and check unusual account activity.

Payment data limits

For Touch 'n Go, GrabPay, Boost dan FPX, we store transaction references, status checks, and verification outcomes. We do not need your full banking credentials, and the policy states how payment data is used.

Retention windows

Some records must be kept for account, fraud prevention, payment, or legal reasons. When a record is no longer needed for those purposes, our process is to delete it or make it no longer identifiable.

Change requests

You can ask us to correct account data, provide a copy, or erase details where retention duties do not apply. We verify ownership first, then respond through the contact path used for the request.

Privacy Policy questions before you join

These privacy questions explain how we handle account data before, during, and after you use the lobby. They focus on your rights, payment records, cookies, device checks, and contact routes. If anything is unclear after you read this page, ask support before you open an account or before you send extra documents.

We collect account details, contact data, login credentials, device signals, and verification records needed to create and protect your account. The Privacy Policy explains each category and the purpose linked to that category.

We keep transaction references, payment status, timestamps, and checks needed to match deposits or withdrawals to your account. We do not ask for full banking credentials through the Privacy Policy process.

Cookies support login sessions, language settings, account safety prompts, and service measurement. The Privacy Policy describes why cookies are used and how they relate to your device and account activity.

Yes, you can ask for a copy through support. We verify account ownership before sharing data, then provide the categories we can release without exposing another person, system security detail, or restricted record.

You can ask us to correct inaccurate account details, contact data, or payment references tied to your profile. We may request proof if the change affects identity checks, withdrawals, or account access.

Retention depends on the record type and the reason it was collected. Payment, security, and legal records may be kept longer, while data with no active purpose is deleted or made non-identifiable.

Yes. Any access or eligibility discussed in this Privacy Policy depends on local law and is available only where local law permits. Privacy requests remain available through support for account data we hold.