Rujukan Laman

Your data choices at gdl888

gdl888 keeps this Privacy Policy close to your account flow: we explain what data we collect, why we collect it, and how your choices work before you open…

Malaysia account dataCookie choicesTouch 'n Go recordsSupport request handling
gdl888 Your data choices at gdl888
PRIVACY CONTACTS

Reach us about your privacy

Privacy requests should reach the team that can verify your account and act on the correct record. Use the contact route that matches your concern, then include your registered mobile number or email so we can locate the account without asking for extra data. We will not ask for your password in a privacy request, and we may need identity checks before changing or releasing account records.

Team online

Privacy email

Send privacy requests by email when you need a written record, such as access, correction, deletion, or cookie questions. Include your account email and the request type, but never include your password or full bank details.

In-account chat

Use chat after signing in when the request concerns the account you are using. The support team can confirm basic account markers, raise a privacy ticket, and tell you what proof is needed next.

Correction request

Ask for a correction when your name, mobile number, email, or payment reference needs updating. We may compare the request with verification records so account security is not weakened during the change.

DATA PRACTICES

How your account data is handled

We keep privacy work tied to practical account tasks, not vague promises. Data is collected when you create an account, set cookie preferences, contact support, make wallet transactions, or pass security checks.

Account data

We collect account identifiers such as name, email, mobile number, login history, and verification markers. These fields help us manage account access, confirm requests, prevent unauthorised changes, and connect support cases to the correct profile.

Cookie choices

Cookies help keep you signed in, remember language choices, measure page performance, and detect unusual access attempts. You can adjust browser settings, although some account and security functions may not work correctly without essential cookies.

Payment records

Touch 'n Go, GrabPay, Boost dan FPX records are used to match deposits, verify withdrawals, resolve wallet disputes, and meet transaction record duties. We store references, timing, status, and limited account markers rather than full card data.

Security checks

Login attempts, device signals, IP patterns, and failed verification events help us spot account takeover attempts. When risk is detected, we may ask for extra proof before making changes or releasing private account records.

Retention windows

Some records must be kept after account closure because payment disputes, fraud checks, tax duties, or legal requests can arise later. When a retention reason ends, we delete, anonymise, or archive the record securely.

Data requests

You can ask to access, correct, restrict, or delete eligible personal data. We check identity first, then respond based on the data type, local law, security needs, and records we must still keep.

Clear answers on your privacy rights

These answers explain how the Privacy Policy works when you manage your account, use local payment options, set cookies, or contact support. They are written for common Malaysia privacy questions and focus on the data we collect through the gdl888 account flow. If your request involves legal rights, we will handle it according to local law and the records connected to your account.

It covers personal data linked to your account, wallet activity, identity checks, support chats, cookie choices, login records, and security events. It also explains when service providers handle data for payment, hosting, verification, or support purposes.

We ask for account details to create and maintain your profile, verify account ownership, process wallet activity, respond to support requests, and protect the account from unauthorised access. We avoid asking for data that is not needed.

Payment records help us match deposits, confirm withdrawal ownership, handle disputes, trace failed transactions, and meet record duties. We keep transaction references and status data, not unnecessary payment details beyond what the process requires.

Yes, you can ask for access to eligible account data through email or in-account chat. We will verify your identity first, then provide the data we can release under local law and security rules.

You can request correction of profile details such as email, mobile number, or name spelling. We may ask for proof before making changes, especially if the update affects login access or payment verification.

Retention depends on the record type and why it is needed. Wallet records may be kept for disputes, fraud checks, and legal duties, while support records are kept long enough to resolve cases and protect account history.

Only service providers that help us operate the account flow may receive relevant data, such as hosting, payment processing, verification, security monitoring, or support tools. They must handle the data for our stated purpose.