Rujukan Laman

Open your privacy terms clearly

Our Privacy Policy explains how we handle account details, device signals, cookies and payment references when you open an account or use the lobby from Malaysia, including George…

Account dataCookie choicesPayment referencesMalaysia support
918cuci Open your privacy terms clearly
CONTACT ROUTES

Check your privacy contact options

Privacy requests should reach the team that can identify your account without exposing extra data.

Live chat privacy request Use live chat when you need a quick check on account data, cookie settings…
Email record request Email is better for access, correction or deletion requests because it creates a clear…
Wallet data query If your question involves Touch 'n Go, GrabPay, Boost dan FPX references, tell us…
HANDLING RULES

Browse how we protect data

We keep privacy handling practical: collect what the account needs, restrict staff access, log sensitive changes and remove data when it is no longer required for legal, security or account purposes.

Account identity data

We collect details such as name, contact number, email, login records and verification status so your account can be opened, protected and supported. We avoid asking for extra documents unless checks require them.

Cookie and device data

Cookies help keep your session active, remember basic choices and detect unusual access attempts. Device data may include browser type, IP signal, time stamp and page actions linked to security checks.

Payment reference handling

Touch 'n Go, GrabPay, Boost dan FPX records are used to match wallet activity, confirm transaction status and answer payment-related privacy questions. We keep references separate from unnecessary personal banking details.

Access control

Staff access to personal data is limited by role and logged for review. Support agents see only the data needed to answer your request, verify identity or escalate a privacy case.

Retention periods

We keep account, support and wallet records only while they are needed for service, dispute handling, security checks or legal duties. When retention no longer applies, data is deleted or made anonymous.

Correction and removal

You can ask us to update inaccurate details or assess a removal request. Some records may need to remain where required for security, transaction evidence or duties under applicable local law.

Discover your data rights

These answers explain how we treat privacy requests on 918cuci, including account access, payment references, cookies and data changes. If your situation involves legal eligibility or location checks, our reply may depend on local law and where access is permitted.

We collect the details needed to create, protect and support your account, such as contact data, login records, verification status and account activity. We may also keep support messages linked to privacy or security requests.

We use payment references to match wallet activity, confirm transaction status and investigate account queries. We do not need your full banking login or wallet password, and you should never send those details to support.

Yes. Contact us from your registered email or verified chat session and explain the data you want to access. We may confirm identity first so your account details are not released to the wrong person.

Send us the outdated detail, the correct replacement and any proof needed for verification. We update records after checks are complete, especially where the change affects wallet matching, contact recovery or account security.

No. Cookies mainly support session control, basic preferences, fraud checks and page performance. Some cookies are needed for secure account access, while others help us understand errors without identifying more than necessary.

You may ask us to assess deletion when your account no longer needs certain data. Some records may be kept for transaction evidence, security logs, dispute handling or legal duties before removal can happen.

Use live chat for quick privacy questions or email for access, correction and deletion requests. Include your registered contact detail and a clear request, but do not send passwords or full bank statements.