Rujukan Laman

Open your privacy choices with king4d

Perfect Blackjack, Dragon Dance and Football Studio sit behind one account record, and this Privacy Policy explains how we collect, use, protect and keep the data linked to…

Account data useCookie choicesMalaysia privacy requestPayment data context

Explore the lobby Read FAQ

Explore how this policy protects your data

king4d Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

This Privacy Policy covers the personal data we handle when you create an account, enter the lobby, verify a payment, ask for support or request a privacy change. We collect only what we need for account access, wallet records, security checks, fraud screening, service messages and

1
legal duties that may apply in Malaysia. If you open from Melaka, the same account checks apply as any other supported Malaysia location. Payment references from Touch 'n Go, GrabPay, Boost dan FPX are used to match your wallet activity, confirm your request and keep audit
2
records. We do not sell your personal data. We may share limited data with payment processors, security vendors and service partners when they need it to complete a task for your account. Access and eligibility depend on local law and are available where local law permits.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

REQUEST PATHS

Check your privacy contact paths

Privacy requests should reach the team that can verify your account safely before any change is made.

Live chat privacy help Use live chat when you need a quick explanation about the data shown in your account, cookie controls or payment references. We may move sensitive requests to email if identity checks are needed.

Email data requests Send privacy correction, access or deletion requests by email with your account name and contact detail. We will check identity, confirm what can be changed and explain any record we must keep.

Account security checks If you think your account data has been viewed without permission, contact us at once. We can review login records, wallet activity and recent device signals before advising the next steps.

SECURITY PRACTICE

Browse our data handling controls

Our Privacy Policy is written around the data actions we perform every day: account creation, login checks, wallet matching, cookie use, support replies and retention.

Account profile data

We use your registration details to create and maintain your account, match support requests and keep access records accurate. If a profile field is wrong, ask us to correct it after identity checks.

Cookie and device signals

Cookies help keep your session active, remember basic preferences and flag unusual login behaviour. You can adjust browser settings, but some security and account functions may not work as intended.

Payment reference handling

Touch 'n Go, GrabPay, Boost dan FPX references are used to match wallet activity with your account. We store transaction identifiers, timing and status, not full banking credentials from your provider.

Withdrawal verification data

When you request a withdrawal, we check account ownership, wallet history and payment match records. These checks help prevent account misuse and may require us to keep audit data for a set period.

Retention and deletion

We keep personal data only while needed for account service, security checks, dispute handling and legal record duties. If deletion is available, we remove or anonymise data that no longer needs retention.

Sharing with service partners

Some data is shared with payment processors, hosting services, fraud screening tools and support systems. Each partner receives only the data needed for its task and must protect it under agreed controls.

Discover answers about your privacy rights

These answers explain how to act on the rights described in this Privacy Policy. They focus on account data, payment references, cookies, support records and security checks. If your request depends on local law, we will tell you what can be done for your account and what records must remain.

We collect registration details, contact data, login records, device signals, wallet activity and support messages. We use these records to run your account, protect access, process requests and meet duties that may apply.

We use payment references to match your wallet activity, confirm timing, handle support questions and check withdrawal requests. We do not receive full banking credentials from those payment providers through normal account use.

Yes, you can ask us to share the account data we hold or correct details that are wrong. We will verify your identity first, then explain what can be changed or released.

You may request deletion when the data is no longer needed for account service. Some records may remain for security checks, dispute handling, payment audits or legal duties before they are removed or anonymised.

Cookies keep your session active, remember basic settings and help us detect unusual access attempts. You can manage cookies in your browser, but some account and security features may be affected.

Only team members and service partners who need to handle the request may access related data. We limit access by role and keep request records so privacy actions can be traced.

We update this page when our privacy handling changes in a meaningful way. If a change affects your account use or data rights, we may also send a service message through available contact paths.

Open your privacy choices with king4d

Check your privacy contact paths

Browse our data handling controls

Account profile data

Cookie and device signals

Payment reference handling

Withdrawal verification data

Retention and deletion

Sharing with service partners

Discover answers about your privacy rights

01 What personal data do we collect when you open an account?

02 How do we use Touch 'n Go, GrabPay, Boost dan FPX data?

03 Can you ask to see or correct your account data?

04 When can account data be deleted?

05 Why do we use cookies on the site?

06 Who can access your privacy request?

07 How will we tell you about policy changes?

Related Pages