Rujukan Laman

How kiss4d handles your privacy

Our Privacy Policy explains how account records, wallet activity, device signals and contact details are collected, used and kept when you open an account with us.

Account data useCookie choicesMalaysia accessPrivacy requests
kiss4d How kiss4d handles your privacy
CONTACT ROUTES

Three ways to ask about privacy

If you want to ask how a record is used, corrected or kept, contact us through the channel that matches your request. We may ask for account checks before discussing private records, because privacy replies must go only to the account holder or an authorised contact.

Team online

Live chat privacy help

Use live chat from your signed-in account when your question is linked to wallet records, login alerts or recent contact history. We confirm account access first, then route the privacy request to the right internal team.

Email privacy request

Send your privacy request from the email address linked to your account and include your account name plus the record you want checked. Avoid sending card images or extra documents unless our team asks for them.

Wallet record query

For Touch 'n Go, GrabPay, Boost dan FPX privacy queries, share the transaction reference and date only. We use those details to locate the related wallet entry without asking for unrelated personal data.

DATA CONTROLS

Six privacy controls you can use

Privacy work is part of our account operations, not a side form. We use access controls, log checks and retention rules to keep account records limited to clear…

Account data collected

We collect details needed to create and manage your account, such as login name, contact channel, device checks and wallet…

Cookie and device signals

Cookies help us keep your session active, remember privacy choices and detect unusual access patterns.

Payment privacy checks

Touch 'n Go, GrabPay, Boost dan FPX references are used to match deposits or withdrawal checks to your wallet.

Access to records

You can ask us to confirm the personal data linked to your account.

Correction requests

If your contact details or account profile are wrong, tell us what needs to be changed and why.

Retention and deletion

Some records can be removed when they are no longer needed, while wallet, security and dispute records may need to…

Privacy Policy questions for your account

These answers explain the practical parts of our Privacy Policy in plain terms. They cover the data we collect, how payment records are used, when we keep records, and how you can contact us about access, correction or deletion requests.

It covers account details, login records, contact messages, device signals, cookie choices and wallet references linked to your account. We use this data to manage access, process requests, protect accounts and meet legal record duties.

We keep payment references so we can match deposits, check withdrawals, answer wallet questions and trace disputes. The record normally includes the method name, transaction reference, timing and account wallet link, not unrelated personal data.

Yes. Send a request through live chat or email from your registered contact channel. We verify your identity first, then explain what account data we can share and whether any record is restricted by legal duties.

Tell us which detail is wrong and provide the correct value through your signed-in account or registered email. We may ask for a check before changing contact, wallet or identity-related details to prevent unauthorised edits.

Cookies keep your session active, remember your privacy choices and help us detect unusual access. You can manage many cookies through your browser, though some account functions may need essential cookies to work correctly.

We keep data only for clear account, wallet, security, dispute or legal record purposes. Some records can be deleted sooner, while payment and access logs may need to remain for a defined period.

Contact live chat from your account or email us from your registered address with the privacy topic and relevant dates. Do not send extra documents unless requested, as we try to limit data shared in each request.