Rujukan Laman

Privacy Policy for Malaysia Accounts

Before you open your account, our Privacy Policy explains how klu008 collects, uses, stores and protects the data linked to your profile, device, wallet checks and support chats.

Malaysia data careCookie choicesWallet privacy checksLocal law applies
klu008 Privacy Policy for Malaysia Accounts
CONTACT CARE

Privacy Help for Malaysia Wallets

If a privacy question comes up while you open your account, change profile details or ask about wallet records, contact us through the channel that matches your request. We may ask for account proof before changing or releasing personal data, because privacy requests must be tied to the correct account holder.

Team online

Live chat privacy desk

Use live chat when you need help finding cookie choices, correcting profile details or asking why a privacy check appears during wallet activity. We confirm your account first, then route the case to the right team.

Email request channel

Email us for access, correction or deletion requests that need written handling. Include your account name, contact email and the privacy action you want, but do not send passwords or full bank details.

Wallet record checks

For Touch 'n Go, GrabPay, Boost dan FPX privacy questions, share the transaction time and account reference. We use that to trace the record without asking for extra payment data we do not need.

DATA HANDLING

How klu008 Handles Your Privacy

Our privacy work sits behind every account step, from sign-in checks to wallet matching and support follow-up.

Account data collection

We collect profile details, contact data, login records and device signals needed to create and protect your account. The policy explains the purpose for each category so you know why a field is requested.

Cookie choices

Cookies help remember your session, language choice and security status. You can adjust browser settings, though some account checks may need session cookies so the wallet and support pages recognise you correctly.

Wallet verification

When you use Touch 'n Go, GrabPay, Boost dan FPX, we keep transaction references, timing and account links for matching and dispute handling. We avoid storing full payment credentials that are not needed for privacy records.

Security checks

Login alerts, device patterns and failed access attempts may be recorded to protect your account from misuse. These records are handled under access controls and are used only for account safety and investigation needs.

Retention periods

Some records are kept while your account remains active, while payment and security logs may stay longer where legal or dispute duties require it. When retention ends, we delete or anonymise records where practical.

Request changes

You can ask us to correct outdated profile details, access personal data linked to your account or remove data that is no longer needed. We may verify identity before acting on any privacy request.

Malaysia Privacy Questions Before You Join

These privacy questions explain what happens to your data before and after you open an account. We keep the answers practical: what we collect, why wallet checks appear, how cookies work, who may handle records and how you can ask us to change them.

We collect details needed to create and protect your account, such as profile fields, contact data, login records, device signals, wallet references and support messages. Each category is tied to account access, payment matching or customer care.

Those names may appear because we need to match wallet activity with your account. We keep transaction references, timing and status for support and dispute handling, while avoiding extra payment credentials that are not required.

Cookies keep your session active, remember language choices and support account security checks. Some cookies are needed for sign-in and wallet pages, while browser settings can help you manage other cookies on your device.

Yes. Contact us with the field that needs correction and proof that the account belongs to you. We check the request, update eligible records and tell you if any legal duty prevents a change.

Account records are kept while needed for account operation, support, dispute handling or legal duties. When a record is no longer required, we delete, anonymise or restrict it depending on the type of data involved.

Access is limited by role. Support teams may see account contact details, wallet teams may see transaction references, and security teams may see login records. Staff access is logged and tied to work needs.

Access and eligibility depend on local law and are available where local law permits. If a legal rule affects your account, we may need to limit access, keep certain records or ask for extra verification.