Rujukan Laman

Privacy Policy for Malaysia account data

Our Privacy Policy shows what account, cookie, payment and support data we collect when you open an account, explore rooms such as French Roulette or Tower Quest, and…

Malaysia data rightsCookie choicesPayment privacySupport contact
autopay Privacy Policy for Malaysia account data
CONTACT ROUTES

Contact us about your privacy choices

Privacy requests work better when they reach the right queue, so we separate account, payment and security questions before we reply. Tell us whether your request is about access, correction, deletion, cookies, a support chat or a payment reference. We may ask you to confirm your account login, recent wallet method or device detail so we can avoid sending data to the wrong person.

Team online

Privacy inbox

Use the privacy inbox from the account help area to ask for access, correction, deletion or a copy of your data. We confirm the request through your account before sharing any record.

Live chat handoff

Start live chat when you need a quick privacy handoff, then ask the agent to mark the chat as a policy request. We keep the chat record tied to your account for follow-up.

Account ticket

Open an account ticket if your privacy question involves a payment reference, device login or withdrawal check. Add only the relevant date and method, not screenshots with unrelated personal data.

ACCOUNT SAFETY

French Roulette to FPX data handling

Data handling is part of how we keep the account area usable and traceable. We collect only what is needed for login, wallet reconciliation, game-session history, security checks, cookie settings and support…

Account data

We keep your name, contact details, login status and account settings so your account can be identified when you return, request help, change details or ask for privacy action.

Payment records

For Touch 'n Go, GrabPay, Boost dan FPX, we keep the transaction reference, amount, status and time received so wallet balances can be reconciled and checked during withdrawal verification.

Cookie choices

Cookies help remember your session, language preference and security state. You can manage browser settings, but some account pages may ask you to sign in again if cookies are blocked.

Security checks

Device, IP and sign-in records help us spot unusual access. When a login looks different, we may ask for extra confirmation before showing account or payment records.

Retention periods

Support chats, payment references and security logs are kept for different periods. We remove or anonymise data when it is no longer needed for the reason collected.

Change requests

You can ask us to correct inaccurate account data or delete eligible records. We may keep certain payment or security records if the law or dispute handling requires it.

Your Privacy Policy questions answered

These answers explain how the Privacy Policy applies when you open an account, use cookies, contact support, or pay through Malaysia methods. They are written for practical account situations, not legal theory. If your request is specific to your account, contact us from inside the account area so we can verify you before replying.

It covers account details, login records, device checks, cookie settings, game-session references, wallet activity and support messages. It also explains why we collect each data type and how you can contact us about it.

We use Touch 'n Go, GrabPay, Boost dan FPX records to confirm transaction status, reconcile your wallet and check withdrawal requests. We keep references and timestamps, not a public display of your payment activity.

Yes. Send a correction request through the privacy inbox or an account ticket. We may ask you to confirm your login or recent activity before changing data tied to your account.

Retention depends on the record type. Support chats may be kept for follow-up, payment references for reconciliation, and security logs for account protection. When a record is no longer needed, we remove or anonymise it.

Cookies help keep you signed in, remember basic preferences and support security checks. If you block them, some account pages may reload or ask for another sign-in before showing private records.

Only team roles that need the chat to answer your request, check account activity or handle a privacy action can see it. We do not treat chat records as public account content.

If account access, eligibility or a privacy request depends on your location, we apply the policy where local law permits. Some requests may need identity checks or may be limited by legal record duties.