Rujukan Laman

Open your gtr88 privacy choices

Your account connects Lightning Blackjack, Egypt Treasure, Football Studio and Malaysia wallet checks, and this Privacy Policy explains how the related data is collected, used and kept.

Account data scopeCookie choicesTouch 'n Go contextData request routes
gtr88 Open your gtr88 privacy choices
CONTACT PATHS

Check your privacy contact routes

Privacy requests need a clear route, not a vague inbox. Use the contact option that matches your concern, and include your account name, registered phone number and the data point you want…

Account data request Send us the account field you want checked, such as name spelling, phone number or email. We verify the request against account access logs before we change or confirm any stored data.
Wallet data question For Touch 'n Go, GrabPay, Boost dan FPX records, share the date, amount and reference shown in your wallet. We use that detail to trace the record without asking for your full bank login.
Cookie and device query If your question is about cookies, browser storage or device records, tell us the device type and browser used. We can explain which records help sessions stay linked to your account.
ACCOUNT CARE

Browse our data handling controls

Every privacy control has a practical job. Some records prove that your wallet transfer matched the right account, while others keep your session from being taken over.

Collection scope

We collect account opening details, login records, device signals and wallet references tied to your activity. The purpose is to confirm access, match transfers and answer privacy requests without collecting data that has no use.

Cookie control

Cookies help keep your session active, remember language settings and detect unusual login patterns. You can clear cookies in your browser, but some account checks may ask you to sign in again.

Wallet records

Touch 'n Go, GrabPay, Boost dan FPX records are stored as transaction references, timestamps and account matching details. We use them to reconcile balances and handle disputes, not to access your wallet password.

Security checks

Login attempts, password resets and device changes create security records. These records help us detect account misuse, confirm that a request came from you and protect your stored account data.

Retention schedule

We keep records only for account service, dispute handling, security checks and legal duties. When a record is no longer needed, we remove it or separate it from details that identify you.

Change requests

You may ask us to check, correct or remove personal data where Malaysian law allows. We will confirm your identity first, then tell you what can be changed and what must be retained.

Discover answers about your privacy

These answers explain the parts of the Privacy Policy you are most likely to use after opening an account. They cover what we collect, why wallet references matter, how cookies work, how long records stay with us and how you can ask for changes.

It covers account opening details, login records, device signals, wallet references, cookie settings and support messages. It also explains why each data type is collected and how you can ask us to check it.

Wallet records help us match Touch 'n Go, GrabPay, Boost dan FPX transfers to the correct account. We store references, time stamps and matching data, not your wallet password or full banking login.

Cookies keep your session connected, remember basic settings and help detect unusual access. You can clear them in your browser, but you may need to sign in again after doing so.

Yes. Send the field you want corrected and proof that links the request to your account. We will check the record, apply changes where allowed and explain any data we must retain.

Retention depends on the record type. Security logs, wallet references and support messages may be kept for dispute checks, account service or legal duties, then removed or separated from identifying details.

Access is limited to staff and service partners who need the data for account service, payment matching, security checks or lawful requests. We do not give every team the same level of access.

Yes. When access or eligibility is discussed, it depends on local law and is available where local law permits. This Privacy Policy explains how data is handled where access is allowed.