Rujukan Laman

Privacy Policy for Malaysia accounts

Your account, wallet and lobby activity sit behind one Privacy Policy, including data linked to Lucky Blackjack, Safari Wilds, Football Studio, Crash X and American Roulette.

Account data clarityCookie use explainedMalaysia payment recordsPrivacy contact paths
kclub99 Privacy Policy for Malaysia accounts
DATA CONTACTS

Contact us about privacy data

Privacy requests should reach the team through a channel where we can confirm account ownership without exposing more data than needed. Tell us the account name, the contact detail you want us to use and the exact privacy request. Do not send card images, full identity files or payment screenshots unless our team asks for a specific item.

Team online

Live chat privacy queue

Use live chat when you need a fast privacy check on account access, cookie settings or wallet record status. We may ask for partial account details before discussing personal data.

Email request path

Email works well for correction, export or removal requests because it leaves a dated trail. Include your account name, registered contact detail and the data area you want us to check.

Wallet data query

For Touch 'n Go, GrabPay, Boost dan FPX privacy questions, share the transaction time and reference code only. Our team checks the record without asking for full wallet login details.

ACCOUNT SAFEGUARDS

How we handle your account data

We treat privacy as part of daily account operations, not a separate form hidden away from the lobby.

Account details

We collect details you provide when opening or managing your account, such as contact data, login records and verification status. These fields help us keep access tied to the correct person.

Cookies and device data

Cookies help keep your session active, remember language choices and detect unusual login patterns. You can adjust browser settings, but some account and wallet functions may need essential cookies.

Payment references

Touch 'n Go, GrabPay, Boost dan FPX records are used to match wallet activity with your account. We keep transaction codes, times and status data, not your full wallet password.

Access checks

When a login looks unusual, we may ask for confirmation before account data is shown. This can include device checks, one-time codes or support verification through the contact detail on file.

Retention decisions

Some records must stay while your account is active or while a legal, payment or security matter remains open. After that, we delete, anonymise or separate data where practical.

Change requests

You can ask us to correct outdated details, send a copy of account data or remove eligible records. We check identity first, then respond through the contact path linked to your account.

Malaysia privacy questions for your account

These answers focus on how the Privacy Policy works when you use your account, wallet and support channels. If your question involves a specific transaction, login attempt or data correction, contact us with the smallest set of details needed. That keeps the request clear and reduces extra data sharing.

We collect account details you give us, login records, device signals and verification status. We use this data to create access, protect your wallet, respond to requests and keep records required for service or law.

Payment records help us match wallet activity to your account, check transaction status and resolve disputes. For Touch 'n Go, GrabPay, Boost dan FPX, we keep references and status data, not your wallet password.

Cookies help the site remember session status, language choices and security signals. Some cookies are needed for account areas to work, while browser settings may let you block or clear others.

Yes. Send the account name, registered contact detail and the field that needs correction. We check identity before making changes so another person cannot alter your account data without permission.

Retention depends on the type of record, account status, payment activity and legal duties. When data is no longer needed, we delete it, anonymise it or keep it separate with reduced access.

Only staff who need the data for account, wallet, security or support tasks may access it. We limit access by role and keep internal checks around sensitive records and payment references.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy requests may also be handled according to laws that apply to your location and account activity.