Rujukan Laman

Privacy Policy for Malaysia Account Data

Our Privacy Policy explains how megasloto collects account details, device signals, cookie data and payment records tied to Touch 'n Go, GrabPay, Boost dan FPX.

Account data explainedCookie choicesMalaysia privacy requestsTouch 'n Go context
megasloto Privacy Policy for Malaysia Account Data
HELP PATHS

Contact Us About Privacy Requests

You can ask about this Privacy Policy before or after you open an account. To protect your data, we may ask you to confirm account details before we discuss stored records or…

Privacy email Write to [email protected] with the email or phone number linked to your account. Do not send full card, bank, or identity images unless our team specifically asks through a protected channel.
Live chat request Use live chat when you need a quick route to the privacy queue. We will confirm basic account details first, then tell you which documents or reference numbers are needed for the request.
Account message If you can access your account, send a message from inside the account area. That route helps us match your request to the correct profile without asking for repeated personal details.
ACCOUNT CARE

Data Handling Around Cash or Bust

Our privacy work follows the account journey: sign-in, wallet checks, lobby sessions, game logs, support, and payout verification.

Data we collect

We collect account details, contact fields, age and identity checks, login records, device data, cookie choices, wallet references, game logs, and support messages. Each category connects to account operation, security, service support, or legal record duties.

Cookie controls

Cookies help keep you signed in, remember language choices, measure page errors, and detect risky access patterns. You can adjust browser settings, but some account, wallet, and security checks may not work without essential cookies.

Payment privacy

Touch 'n Go, GrabPay, Boost dan FPX records may include reference numbers, timestamps, transaction status, and the account name needed for checks. We use these records for reconciliation, disputes, chargeback handling, and payout verification.

Access security

We monitor sign-ins, password changes, withdrawal requests, and unusual device patterns. When risk signals appear, we may pause account changes until you confirm ownership through support or provide matching records.

Retention periods

Some data is removed when it is no longer needed, while payment, identity, dispute, and security records may stay longer. Retention depends on legal duties, fraud prevention, account disputes, and active privacy requests.

Change requests

You may ask us to correct contact details, update inaccurate account data, or explain why a record is being kept. If deletion is not possible, we will explain the reason in plain language.

Privacy Questions Before You Join

These answers explain how the Privacy Policy works in common account situations. They focus on data rights, payment records, cookies, security checks, support contact, and account closure. If your request involves legal status, identity checks, or access rules, availability depends on local law and where local law permits.

We collect details you provide, such as name, contact fields, account credentials, verification data, support messages, wallet references, device signals, IP address, cookie choices, and activity logs needed to manage your account.

We keep local payment references to match deposits, verify withdrawals, resolve disputes, track failed transfers, and meet record duties. These records normally include timestamps, transaction status, amount references, and account matching details.

Yes, you can ask for a copy of personal data linked to your account. We may verify your identity first, then provide the data we can share under applicable law and security rules.

You may ask us to correct inaccurate contact or profile details. Some fields, such as verified identity data or payment ownership records, may require proof before we can update them.

Cookies help with sign-in, security checks, language settings, error measurement, and account safety. You can manage many cookies through your browser, but essential cookies are needed for secure account and wallet access.

We share limited data with partners that support hosting, payment checks, analytics, security monitoring, and support tools. They receive only what they need for the task and must handle it under written controls.

After closure, we remove or reduce data where we can. Some identity, wallet, dispute, security, and legal records may stay for a required period before deletion or further restriction.