Rujukan Laman

Privacy Policy for your Malaysia account

Our Privacy Policy explains what data we collect when you open an account, enter the lobby, use Touch 'n Go, GrabPay, Boost dan FPX, or contact support.

Account data scopeCookie choicesPayment record carePrivacy request path
berjaya918 Privacy Policy for your Malaysia account
CONTACT PATHS

Three ways to ask about privacy

Privacy requests should reach the right team quickly, so we keep the contact route simple. Tell us what you want checked, changed or removed, and include the account details needed to match your request. We may ask for extra proof before we alter sensitive records, because privacy protection also means keeping your account from being changed by the wrong person.

Team online

Live chat privacy desk

Ask our chat team to route your privacy request, account-data query or cookie question. We log the request, confirm the account link and tell you what proof is needed before any record is changed.

Email record request

Send a clear request through our email channel when you need a written trail. State whether you want access, correction or deletion, and we will reply with the next verification step.

Wallet data query

For Touch 'n Go, GrabPay, Boost dan FPX privacy questions, share the transaction reference only through our support path. We use it to locate records without asking for full wallet credentials.

DATA CARE

Six privacy controls we keep active

A privacy policy works only when it matches real account handling. We separate payment references from login credentials, restrict internal access to staff who need it, and keep support records tied to…

Account creation data

When you open an account, we collect the details needed to set up access and keep records matched to you. We do not ask for payment passwords or full wallet login credentials.

Cookie and device signals

Cookies help keep sessions active, remember basic choices and flag unusual sign-ins. Device signals such as browser type or IP range help us protect access without reading private files on your phone.

Payment reference records

Touch 'n Go, GrabPay, Boost dan FPX entries may create transaction references in our wallet system. We use those references to match account activity, answer disputes and meet record duties.

Access checks

If a login looks unusual, we may ask for extra confirmation before showing account records. This protects privacy by reducing the chance that another person can view your wallet or support history.

Retention periods

We keep records only for purposes described in this policy, including account service, dispute handling, security checks and legal duties. When records are no longer needed, we delete or anonymise them.

Correction requests

If your account data is wrong, contact us with the detail that needs correction. We check ownership first, then update the record or explain why a record must remain unchanged.

Privacy questions before you join

Use these answers to understand how your privacy is handled before you open your account or send any document to support. They cover access requests, payment data, cookies, record changes and deletion. If your question is not listed, contact us and ask for the privacy route so your case reaches the right team.

We collect the details needed to create and manage your account, such as registration data, login records, device signals, wallet references and support messages. We collect only what is needed for the purposes in this policy.

Payment records help us match Touch 'n Go, GrabPay, Boost dan FPX activity to your account. We use transaction references for wallet checks, dispute handling, accounting records and security monitoring, not for full wallet access.

Yes. Contact support and ask for access to your account data. We will verify that the account belongs to you, then explain what records can be shared and the format we can provide.

Send the corrected detail through our support path and include enough proof to confirm account ownership. We update records after verification, unless a legal, security or accounting reason requires the original record to remain.

Cookies keep sessions running, remember basic account choices and help detect risky sign-ins. You can adjust browser cookie settings, but some privacy and security features may not work properly if key cookies are blocked.

We delete or anonymise records when they are no longer needed for account service, legal duties, fraud checks, accounting or dispute handling. Some records may be kept longer where law or security needs require it.

Start with live chat or email and ask for the privacy request route. Share your account identifier, the concern and any relevant transaction reference, but never send wallet passwords or unnecessary private documents.