Rujukan Laman

Privacy Policy for Your kk88 Account

This Privacy Policy explains how kk88 collects, uses, stores, and shares account details when you open an account, verify identity, use the wallet, or ask support for help.

DATA USECOOKIE CONTROLACCOUNT ACCESSLOCAL LAW

explore lobby Read FAQ

How kk88 Handles Your Records

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

We keep privacy handling tied to the account, not treated as a separate side note. The record we hold may include your name, contact details, login history, device markers, cookie signals, and transaction references when you use Touch 'n Go, GrabPay, Boost, or FPX. We use

1
that record to run the account, match deposits and withdrawals, answer support requests, stop duplicate submissions, and keep dispute handling consistent. Where local law asks for extra checks, we may ask for more documents before we change account details or release a copy of the record.
2
If a local rule conflicts with this page, the local rule applies first, and access stays available only where local law permits. You can ask us to correct, update, or close parts of your record through the contact paths on this page.

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

CONTACT CHANNELS

Ways to Reach Our Privacy Team

If you want to ask about access, correction, deletion, or a copy of your record, use the channels below and send the email or phone tied to the account.

Live chat Open a chat from your account page and send the question you want us to trace. We use it for access, correction, or deletion requests, then link the thread to your login details so the right record is handled.

Email Write to [email protected] with the email tied to your account, the change you want, and any document that helps us verify you. We use the message trail to confirm identity and respond in the same thread.

Account form Use the form in your profile when you want to update contact details, consent choices, or stored device notes. If we need more proof, we will ask through the same form before any change is applied.

RECORDS AND CONTROLS

What We Keep and Why

Our privacy handling follows four checks: what we need, why we need it, who can see it, and when it should be removed.

Data scope

We collect only the details needed to run your account, confirm identity, and answer support cases. That can include contact details, login events, device markers, and transaction references, but not more than we need for the purpose shown to you.

Cookies

Cookies keep your session active, remember language and device choices, and help us spot repeated login failures. If you clear them, some saved settings disappear and you may need to verify your device again.

Account security

We use password checks, device recognition, and verification steps before changing sensitive settings or releasing record copies. If you log in from a shared device, we suggest signing out once you finish so your session does not remain open.

Retention

We keep records only as long as they are needed for account support, dispute handling, fraud checks, or any legal duty that applies. After that period, we delete, mask, or archive the record so it is no longer used for active handling.

Access and correction

You can ask to see the record we hold, correct missing details, or request removal where local law allows. We may ask for identity proof first, because the request must be matched to the right account before we act.

Changes contact

Send privacy changes through chat, email, or the profile form, and include the account email plus the change you want. If a regional rule affects the request, we will explain what can be done and what must stay on file.

Common Privacy Policy Questions

These answers cover what we collect, how we use it, how long it stays on file, and how you can ask for a change. If your question is about a specific account action, send the email tied to that account so we can match the record first. Some requests depend on local law, and where the law allows, we will handle them through the channels on this page.

We usually collect the details needed to run your account, such as your name, contact details, login history, device markers, and transaction references. If a case needs more proof, we may ask for extra records before changing anything.

Cookies help us keep you signed in, remember language choices, and understand when a login or page step fails. They also help us spot unusual access, so we can protect the account and keep support records clear.

Yes. Use the contact paths on this page and send the account email so we can match the request. We may verify your identity first, then provide the record or explain any legal limit on what can be shared.

When a deposit or withdrawal is made through Touch 'n Go, GrabPay, Boost, or FPX, we keep the reference needed to match the transaction and handle disputes. We do not keep more than the account needs for that purpose.

We keep records only for as long as they are needed for account support, dispute handling, fraud checks, or any law that applies to your region. After that, we delete, mask, or archive them.

Send the change through chat, email, or the profile form and include the detail you want corrected. We may ask for identity proof before we update the record, because the request has to match the right account.

Privacy Policy for Your kk88 Account

Ways to Reach Our Privacy Team

What We Keep and Why

Data scope

Cookies

Account security

Retention

Access and correction

Changes contact

Common Privacy Policy Questions

01 What personal details do you collect?

02 Why do you use cookies on my account?

03 Can I ask for a copy of my record?

04 How do payment references affect privacy?

05 How long do you keep my records?

06 How do I ask for corrections?

Related Pages