Rujukan Laman

Privacy Policy for Your Malaysia Account

Our Privacy Policy tells you exactly what happens to your account data when you open an account and reach Lucky Blackjack, Cleopatra or your wallet from Petaling Jaya.

Account dataCookie choicesPayment recordsPrivacy contact
pusay888 Privacy Policy for Your Malaysia Account
CONTACT PATHS

Privacy Contacts for Account Questions

Privacy requests should reach the team that can check identity, account history and data records without exposing your details in a public channel. We keep the contact flow inside account chat and email so you can ask for access, correction or deletion while we verify that the request comes from you. If your account is locked, we may ask for extra proof before sharing any personal data.

Team online

Account Chat

Use account chat when you can still log in and need help with cookie choices, profile edits or a privacy request tied to your wallet activity. We may ask you to confirm recent account actions before discussing data.

Email Request

Send privacy requests by email if you cannot reach chat or need a written record. Include your registered phone or email, the request type, and enough account detail for us to locate the correct record.

Security Check

For account takeover concerns, contact us before requesting data copies. We first secure access, then handle privacy actions, because sending records to the wrong person would put your account and payment history at risk.

CARE CONTROLS

Privacy Handling Around Lucky Blackjack

We write this policy from the same account flow you use: login, lobby entry, game session, wallet request and support contact.

Data We Collect

When you open an account, we collect registration details, login records, device signals and wallet references. Game sessions such as Lucky Blackjack or Dragon Fishing create activity records that help us check account access and resolve privacy queries.

Cookie Choices

Cookies help keep your session active, remember language and record consent choices. Some cookies are needed for login safety, while optional tracking can be adjusted through your browser or by asking support for help.

Payment Records

Touch 'n Go, GrabPay, Boost dan FPX records are used to match wallet requests, verify account ownership and investigate disputed activity. We keep payment references separate from chat content wherever the request can be handled that way.

Account Security

We use login checks, device matching and restricted staff access to reduce unauthorised viewing of your data. If a request looks unusual, we may pause privacy processing until your identity is confirmed.

Retention Periods

Some records are kept only for session use, while account, wallet and verification records may need longer retention for legal, dispute or security reasons. When retention no longer applies, we delete or anonymise records.

Change Requests

You can ask us to correct profile data, provide a copy of eligible records or delete data that no longer needs to be kept. We explain any refusal with the reason tied to law, safety or account records.

Privacy Policy Questions Before You Join

These answers explain how the Privacy Policy works before and after you open an account. They focus on the data you provide, the records created by account activity, and the ways you can contact us about access, correction, deletion or cookie choices. If a request involves legal duties or account safety, we will tell you why more checks are needed.

We collect the details needed to create and secure your account, such as contact data, login records, device signals and verification details where required. Wallet and game-session records are added when you use those account areas.

Payment records help match Touch 'n Go, GrabPay, Boost dan FPX activity to your wallet, confirm ownership and investigate disputes. We keep only what is needed for account records, legal duties and security checks.

Yes. You can ask us to correct data that is wrong or out of date. We may need to confirm your identity first, especially if the request affects login access, wallet records or verification details.

Cookies keep your session active, remember choices and help detect unusual access attempts. You can manage some cookies in your browser, and support can explain which cookies are needed for account access.

Only staff who need to handle the request can view the related records. We limit internal access by task, so a payment query, login issue or cookie request is routed to the relevant team.

Retention depends on the record type and the reason it was collected. Session cookies may expire quickly, while verification, wallet and dispute records may be kept longer for legal, security or account-history reasons.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy rights may also be handled according to applicable legal duties, account safety checks and required record keeping.