Rujukan Laman

Privacy Policy For Your Malaysia Account

Playtech Roulette, Mega Jade, Football Studio and Cash or Crash sit beside Touch 'n Go, GrabPay, Boost dan FPX in your account flow; this Privacy Policy explains the…

Account data explainedCookie choicesWallet record useMalaysia law context
smcrown Privacy Policy For Your Malaysia Account
CONTACT PATHS

Privacy Help Through Malaysia Channels

Questions about this Privacy Policy should come through the same channels you use for account help, but mark them clearly as privacy matters.

Live chat privacy queue Open chat from your account and ask for privacy help.
Email request record Send privacy requests from the email linked to your account.
Account centre changes Use the account centre for simple profile updates first.
ACCOUNT CARE

Data Care Across Wallet And Lobby

We handle privacy work through account, wallet, security and support checks that match how the lobby runs day to day.

Account profile data

We collect details you provide when opening and maintaining your account, such as name, contact details and login identifiers.

Cookie handling

Cookies keep you signed in, remember basic preferences and help us see when a page fails to load.

Wallet activity records

For Touch 'n Go, GrabPay, Boost dan FPX, we keep transaction references, timing, status and related account identifiers.

Lobby preference data

When you open Playtech Roulette, Mega Jade, Bombing Fishing or Cat in Vegas, we may record session data, device type…

Retention controls

We keep data for as long as needed for account service, security checks, disputes and legal duties.

Correction requests

If account data looks wrong, tell us what should be changed and provide proof where needed.

Privacy Questions Before You Open Account

This FAQ focuses only on how this Privacy Policy works for your data. Use it before you open an account, or return to it when you want to ask for a copy, correction, deletion where allowed, or more detail about wallet and cookie records. For personal requests, contact support from your linked account.

We collect the details needed to create and protect your account, such as contact data, login identifiers and verification records. We also keep security logs and support messages connected with account access.

Those wallet methods can create privacy records when you make account transactions. We may receive references, status messages, timing and account identifiers, while full banking credentials stay with the payment provider.

Cookies and similar tools can remember session status, language choices, device type and error signals. They help account pages function and help us understand technical faults, not to collect full payment credentials.

Yes. Contact us from your linked account and state what needs correction. We may request proof before changing verified details, and we will explain if a legal duty requires a record to stay unchanged.

Retention depends on the record type and the reason it was collected. Account, wallet and support records are kept for service, dispute, security and legal needs, then deleted or anonymised when allowed.

Only teams that need the record for account help, privacy requests, security checks or legal duties should access it. Partners may receive limited data when needed to resolve a wallet or service issue.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy requests are handled with that context, plus any legal or payment-partner duties that apply.