Rujukan Laman

Privacy Policy for Your cuci2 Account

cuci2 connects your account, lobby activity and Malaysia wallet records under one Privacy Policy, so you can see how personal data is collected before you open an account.

Malaysia data useCookie choicesWallet reference handlingAccount access requests
cuci2 Privacy Policy for Your cuci2 Account
CONTACT PATHS

Three Ways to Reach Privacy Support

Privacy requests need the right route because we may have to confirm that the request comes from you. Use the channel that matches the issue: quick questions through chat, longer requests by email, and access recovery through support if you cannot log in. We keep the request trail so our team can see what was asked, what was checked and what action was taken.

Team online

Live Chat Privacy Help

Use chat when you want a quick privacy question answered while you are logged in. We may ask for your account ID, registered mobile number and a short reason before we discuss personal data.

Email Requests

Email works for longer privacy requests, including access copies, correction requests or deletion queries. Send the request from your registered address so we can match it to the account safely.

Account Recovery Checks

If you cannot enter your account, contact support and ask for a privacy identity check. We will verify control of your phone or email before changing any stored personal details.

ACCOUNT CARE

Six Privacy Controls We Use

Your privacy record is handled across account creation, login, wallet checks, cookies, support and retention. Each control below explains one part of that flow in plain terms.

Data Collected for Purpose

We ask for data that helps run your account, verify wallet activity and keep records required by our operating process. If a field is not needed for that purpose, we do not ask for it.

Cookie and Session Signals

Cookies help remember language, session state and device signals. You can clear them in your browser, though some account checks may repeat when the site no longer recognises your device.

Payment Reference Handling

Touch 'n Go, GrabPay, Boost dan FPX records are handled as payment references, not public profile content. We use them to confirm transaction status, resolve wallet issues and match withdrawals to the right account.

Account Access Security

Login alerts, password resets and session checks are used to protect your personal data. When activity looks unusual, we may request extra checks before showing sensitive account or wallet records.

Retention and Removal

We keep account and transaction data only for business, security, dispute and legal needs. When those needs end, records are removed, anonymised or kept in restricted archives with narrower access.

Policy Change Handling

When we change this policy, we update the page date and adjust the wording here. If a change affects how we use your personal data, we may also contact you through account channels.

Privacy Policy Questions Before You Join

These answers explain how the Privacy Policy works when you create an account, use the lobby, contact support or make wallet requests. They are written for Malaysia readers who want clear privacy steps before sharing personal data. If your situation needs a specific check, contact us through your account channel so we can look at the record.

This policy covers details you give us, data created by your account activity, device signals, cookie data and payment references. It also covers support messages when you ask us to check or change personal data.

Touch 'n Go, GrabPay, Boost dan FPX references are used to confirm transaction status, match wallet entries and resolve payment questions. We treat those references as account records and limit access to staff who need them.

Yes, you can ask us to correct personal data that is outdated or wrong. We may request account verification first, then update the record or explain why a change cannot be made.

Retention depends on the record type and the reason it is kept. Account, payment and support records may remain while needed for security, disputes, legal duties or internal checks, then they are removed or anonymised.

Cookies can store session, language and device details that help the site recognise your browser. You may clear cookies, but some login checks and account protections may need to run again afterward.

Access is limited to teams and service partners who need the data for account, payment, support, security or legal work. We do not open personal data to staff who have no role in the request.

Yes. Any access or eligibility mentioned in this policy depends on local law and is available where local law permits. If a legal requirement limits what we can provide, we will explain the next step.