Rujukan Laman

How giga888 treats your data

Your account profile, wallet records, device signals and cookie choices are covered in this Privacy Policy before you open an account.

Malaysia data handlingCookie choicesWallet record careAccess requests
giga888 How giga888 treats your data
CONTACT ROUTES

Three privacy contact paths

Privacy requests need clear routing, so we separate routine support from account data changes.

Live chat privacy help Use chat when you need quick direction on cookies, account records or a pending…
Email data requests Send email for access, correction or deletion requests that need written detail.
Account correction path If your name, phone number or payment receipt reference is wrong, we may ask…
ACCOUNT CONTROLS

Six controls behind this policy

Our privacy work is tied to how your account actually runs. Login checks, wallet records, cookies, device markers and support transcripts are handled in separate systems with access given only to teams…

Account data

We use profile details to create your account, verify access, send service messages and match wallet activity to the right person. We do not sell your account profile to outside advertisers.

Cookie controls

Cookies help remember your session, language preference and security state. You can adjust browser cookie settings, but blocking required cookies may affect login, wallet display or saved privacy choices.

Wallet records

Touch 'n Go, GrabPay, Boost dan FPX activity creates receipt references, time stamps and status markers. We use these records to match payments, handle disputes and answer account data requests.

Device security

We may process device type, IP address, browser signals and login time to detect unusual access. These markers help protect your account without exposing your full device content to support staff.

Retention window

Some records must stay for payment checks, dispute handling, tax or legal requests. When a record is no longer needed, we remove it from active tools or strip personal markers where possible.

Change requests

You can ask us to correct, access or delete account data where the law allows. We may decline a request if another legal duty requires us to keep the record.

Privacy questions before you join

Before you open an account, it helps to know what data is involved and how privacy requests are handled. These answers explain the records we use for account access, payment matching, cookies, security checks and support contact. If your question involves a specific transaction or login, contact us with the date, channel and account name.

We collect details needed to create and protect your account, such as your name, contact details, login records, device signals and wallet references. We also keep support messages linked to privacy or account access requests.

Payment records help us match wallet activity to your account, trace failed transactions and answer disputes. The record normally includes a reference number, time stamp, amount status and channel response, not your banking password.

Yes. Contact us through chat or email and ask for account data access. We may verify your identity first, then provide available records unless a legal, security or payment duty restricts release.

Cookies support login sessions, language settings, security checks and account display. You can change browser settings, but some cookies are needed for access, so parts of the site may not work if they are blocked.

Send the correct details through our privacy contact path and include proof where needed. We check the request against account records before making changes, especially for names, phone numbers and payment references.

You can ask for deletion where local law allows. Some wallet, security or dispute records may need to stay for a required period, and we will explain if that affects your request.

Only team roles that need the case can access your request, such as support, payment checks or security staff. We limit access based on task type and keep a record of handling steps.