Rujukan Laman

Open gbslot888 Privacy Policy

gbslot888 keeps your account sign-in, wallet checks and lobby activity under a clear Privacy Policy, with local payment context for Touch 'n Go, GrabPay, Boost dan FPX.

Account data useWallet privacy checksCookie choicesCorrection requests
gbslot888 Open gbslot888 Privacy Policy
CONTACT PATHS

Check privacy contact paths

Privacy questions should reach a team that can match your request to the right account record.

Privacy email Send a request to [email protected] if you want access to your stored account data, a correction, or removal where local law allows. Include your registered phone or email so we can match the request.
Live chat ticket Open live chat and ask for a privacy ticket when your concern relates to cookies, device sessions or wallet records. The team will record the request and route it for a privacy check.
Account inbox Use the account inbox after sign-in when you need a reply tied to your profile. It keeps privacy messages inside your account area and helps us avoid sending sensitive data to the wrong address.
PRIVACY HANDLING

Browse how we handle privacy

Our Privacy Policy is written around the account flow you use: sign-in, identity checks, wallet records, game session logs and contact with our team.

Data collection

We collect account details, sign-in records, device data and service messages when they are needed for access, wallet matching or privacy support. We avoid asking for extra documents unless a check requires them.

Payment records

Touch 'n Go, GrabPay, Boost dan FPX records are used to connect your wallet action with your account balance. We keep transaction references, timing and status, not your full payment app credentials.

Cookie use

Cookies help keep your session active, remember language settings and detect repeated failed sign-ins. You can adjust browser cookie settings, but some account features may need session cookies to work correctly.

Access security

Privacy access is limited to team roles that need the data for account support, payment matching or security checks. Staff access is logged so sensitive account records are not handled without a business reason.

Retention periods

We keep account and wallet records only for as long as needed for service, dispute handling, legal duties and fraud checks. When retention no longer applies, we remove or anonymise eligible records.

Correction requests

If your profile data is wrong, ask us to correct it through email, live chat or account inbox. We may verify your identity first so a third party cannot change your account details.

See your privacy questions answered

These answers explain how the Privacy Policy works when you create an account, use local payment methods, manage cookies or ask us to change stored data. They are written for Malaysia account flows and should be read with the full policy above. If your case involves legal rights, our reply will follow local law where it applies.

It covers account details, sign-in records, device data, wallet references, service messages and privacy requests. It also covers data created when you use Touch 'n Go, GrabPay, Boost dan FPX with your account.

Yes. Send a request through privacy email, live chat or your account inbox. We will verify that the request is yours before sharing account data that local law allows us to provide.

Payment data is used to match your wallet action to your account, confirm status and handle payment disputes. We use transaction references from Touch 'n Go, GrabPay, Boost dan FPX, not full app credentials.

Cookies support login sessions, language settings and security checks. You can change browser settings, but blocking session cookies may affect account access, wallet pages or privacy request forms.

We keep data for as long as needed for account service, payment checks, dispute handling, legal duties and security controls. When those reasons no longer apply, eligible records are removed or anonymised.

Yes. Contact us with the corrected detail and proof that the account is yours. We will update eligible fields or explain why a record must stay unchanged for legal or security reasons.

Only assigned team roles can access personal data for account support, wallet matching, security checks or privacy handling. Access is limited by task, and sensitive actions are logged for internal control.