Rujukan Laman

kiss99 Privacy Policy For Malaysia Accounts

Your account can hold wallet records, device signals, cookie choices and privacy requests, so this Privacy Policy explains how we collect, use, share and protect that data at…

Account data useCookie choicesSecurity checksPrivacy requests
kiss99 kiss99 Privacy Policy For Malaysia Accounts
CONTACT PATHS

Reach Us About Privacy Requests

Privacy questions often need careful routing, especially when they involve wallet records, cookie settings or account access.

Live chat privacy help Open live chat and choose privacy help. We can confirm what we need, create a case ref and move sensitive requests to the privacy desk without asking for full payment credentials in chat.
Email privacy desk Send your request to [email protected] from the email linked to your account. Include your username, the request type and a safe contact route so we can reply with the next step.
Account request form Use the account form when you want access, correction or deletion. The form helps us match your request to the right login, wallet activity and consent choices before any change is made.
ACCOUNT SAFETY

Cookie Choices Around Playtech Roulette Sessions

Playtech Roulette, Football Studio and slot sessions can create logs such as device type, session time, language choice and security events.

Data minimisation

We ask for only the fields needed to create and maintain your account, support wallet checks and answer privacy requests. Extra data is requested only when a legal duty or security check requires it.

Cookie controls

Cookies can remember login status, language choice and safety signals. You can adjust browser settings, but some account and wallet checks may need required cookies to keep your session linked correctly.

Device checks

We record device and network signals to help detect account takeover attempts, repeated failed logins and unusual wallet activity. These checks are linked to security, not to public profiling.

Payment privacy

Touch 'n Go, GrabPay, Boost dan FPX may send payment refs, status codes and time stamps. We do not ask for your full banking password, and we keep payment records access-restricted.

Retention periods

Some records must be kept for legal, tax, dispute and security needs. When a record is no longer required, we remove it, anonymise it or separate it from active account access.

Change requests

You can ask us to correct outdated data, send a copy of account records or remove data where the law allows. We verify the account first so the request cannot be misused.

Privacy Questions Before You Join

Before you join, it is fair to ask what happens to your data and how to control it. These answers cover common privacy requests for Malaysia accounts, including cookies, payment records, access checks and deletion. If your case needs identity proof, we will ask for the minimum we need to match the account. You can still browse this page before opening an account.

We collect account details, login records, device signals, wallet refs and support messages needed to run your account and answer requests. We may also keep cookie choices and security events tied to your session.

Payment records help us match your wallet activity with provider status messages, resolve failed transfers and meet legal record duties. We keep refs and status data, not your full banking password or private wallet login.

Yes. Contact live chat, the account form or [email protected] and tell us you want account data access. We verify that the account is yours before sending any record through a safe channel.

Send the corrected detail through the account form or email [email protected] from your linked email. We may ask for proof when the change affects identity, wallet checks or account recovery.

Cookies mainly support login status, language choice, security checks and session continuity. Game session logs may record timing and technical events, but privacy requests can cover cookie records where the law allows.

You can ask us to delete data where local law allows. Some records may need to stay for legal, payment, tax, dispute or security reasons, and we will explain any record we must keep.

Only the teams needed to verify and answer your request can access it, such as privacy, account security or payment support. We restrict internal access and keep request handling tied to the correct account.