Rujukan Laman

Privacy Policy for your luck555 account

Our Privacy Policy sets out how account details, device signals, cookies and payment records are handled when you use the lobby with Touch 'n Go, GrabPay, Boost dan…

Account data useCookie controlsMalaysia payment recordsRequest paths
luck555 Privacy Policy for your luck555 account
CONTACT CHANNELS

Where to ask privacy questions

Privacy requests should reach the team that can check account records safely, not a public comment thread. Tell us the email or mobile number linked to your account, the data issue you want checked and any transaction reference if the request involves Touch 'n Go, GrabPay, Boost dan FPX. We may ask for extra proof before changing, sending or deleting account records.

Team online

Account privacy inbox

Use the privacy contact address shown inside your account area for access, correction or deletion requests. Include your account identifier and a clear reason so we can locate the right records without exposing data to the wrong person.

Live chat privacy route

Chat support can raise a privacy ticket after basic account checks. For your safety, agents will not ask for full wallet passwords, full banking credentials or one-time codes during a Privacy Policy request.

Payment data queries

If your privacy question concerns Touch 'n Go, GrabPay, Boost dan FPX, share the transaction time and reference shown by your provider. We use those details to match records while keeping wallet credentials separate.

DATA HANDLING

Six ways we handle your data

The policy is written around the records we actually use: account sign-in data, wallet references, game-session logs, cookies, security alerts and support tickets.

Account details

We use your name, contact details and login records to create and protect your account.

Cookie choices

Cookies help keep your session active, remember display settings and detect risky sign-in patterns.

Payment records

For Touch 'n Go, GrabPay, Boost dan FPX, we handle references such as amount, time, status and provider label.

Security checks

Device type, IP range, login time and unusual activity signals may be used to protect your account.

Retention periods

Different records are kept for different reasons, such as payment reconciliation, account safety, dispute handling or legal duties.

Change requests

You can ask us to correct inaccurate details, send a copy of certain records or delete data where the law…

Common privacy questions before joining

These answers explain the privacy points we are asked about most before an account is opened. They cover what we collect, why payment records matter, how cookies work and how you can reach us for changes. If your question involves access or eligibility, our answer also depends on local law and applies where local law permits.

We collect account details such as your contact data, login records, device signals and verification outcomes. The policy explains why each record is needed for account access, wallet matching, security checks and support follow-up.

No. We may store transaction references, status, time and provider labels for Touch 'n Go, GrabPay, Boost dan FPX. Wallet passwords, banking passwords and one-time codes should never be shared with our team.

Cookies help maintain your session, remember basic settings and detect sign-in activity that may need extra checks. You can change browser settings, but some account or wallet steps may not work as expected.

Yes. Send a request through the account privacy inbox or live chat route. We may ask you to verify identity before changing contact details, payment references or other records connected to your account.

Payment records are kept for the period needed to reconcile transactions, answer disputes, meet legal duties and protect account activity. When those reasons no longer apply, we delete or anonymise records where practical.

Only staff or service providers who need access to handle the request should see the relevant records. We use role-based access, ticket tracking and verification steps to reduce unnecessary exposure.

No. The Privacy Policy explains data handling; it does not expand eligibility. Access to the lobby, account services and related features depends on local law and is available where local law permits.