Rujukan Laman

Privacy Policy for Malaysia Accounts

Privacy choices, account records, cookie settings and payment references are handled in one clear Privacy Policy for isenang88.

Account data useCookie choicesPayment reference careRequest channels
isenang88 Privacy Policy for Malaysia Accounts
CONTACT PATHS

Contact Us About Your Privacy

Privacy questions should reach the right team without exposing more data than needed. Tell us your account ID, the email or phone linked to the account, and the request type.

Privacy email Use the privacy email shown in your account area for access, correction or deletion requests. We may ask for a short identity check before changing records, so another person cannot alter your data.
Live chat handoff Start with live chat when the question is urgent, then ask the agent to send the case to the privacy queue. Keep the chat focused on the account record or transaction reference involved.
Account message You can send a message from inside your account when you are signed in. That route helps us match your request to the right profile without asking for extra identity documents.
ACCOUNT CARE

How We Protect Account Data

Our privacy work covers the full account journey, from first registration to wallet checks and later support requests.

Collection limits

We ask for data that supports account creation, verification, payments, security checks and support replies. If a field is not needed for those purposes, we aim not to collect it.

Cookie handling

Cookies help keep you signed in, remember basic settings and detect unusual access patterns. You can adjust browser cookie controls, but some account and wallet checks may not work without required cookies.

Payment references

For Touch 'n Go, GrabPay, Boost dan FPX, we keep transaction IDs, timestamps and status records needed to match payments to your wallet. We do not ask for your banking password.

Account security

Login attempts, device signals and session records help us spot account misuse. If we detect unusual access, we may pause sensitive account actions until identity checks are completed.

Retention periods

We keep personal data only while needed for account service, dispute handling, financial records, security checks or legal duties. After that, data is deleted, anonymised or separated from active account tools.

Correction requests

If your phone number, email or profile details are wrong, contact us through the privacy email or signed-in message route. We may need proof before changing sensitive account records.

Privacy Questions Before You Join

These answers explain the privacy choices and account data practices you may want to understand before opening an account. They cover what we collect, why we use it, how payment records are handled, and how you can ask us to access, correct or delete personal data.

We collect details you provide during account creation, such as contact data and verification details, plus login records, device signals, wallet activity, transaction references, cookie identifiers and support messages connected to your account.

Payment records help us match deposits and withdrawals to the correct wallet, trace failed transfers and answer transaction questions. For Touch 'n Go, GrabPay, Boost dan FPX, we keep references rather than banking passwords.

Yes. Send a request through the privacy email or signed-in account message. We will confirm your identity first, then provide the relevant account data in a practical format where local law permits.

Contact us with the field that needs correction, such as phone number, email or profile detail. We may ask for proof before changing sensitive data, especially where the change affects access or wallet security.

Retention depends on the record type. Account, payment and security data may be kept while needed for service delivery, dispute handling, financial record duties or legal requirements, then deleted or anonymised when no longer needed.

Cookies are used for sign-in, security, settings and basic measurement. Where advertising or analytics partners are used, we limit the data shared and avoid providing full account details unless required for the stated task.

Our support team receives the request, then routes privacy matters to staff who handle account data cases. Use the privacy email or signed-in message route so we can match the request safely.