Rujukan Laman

Open your gdwon privacy choices

Our Privacy Policy explains what data we collect when you open an account, verify access, use the wallet, contact support or move around the lobby.

Malaysia data useTouch 'n Go recordsGrabPay privacyBoost dan FPX context
gdwon Open your gdwon privacy choices
CONTACT ROUTES

Check privacy contact paths

Privacy questions need a clear route, not a long hunt through menus. Use the account help area for logged-in requests, or contact support if you cannot access your account.

Account help area When you can log in, send privacy requests from the help area so we can match your message to your account securely. This is the right route for data copies, corrections and wallet record questions.
Support email route If you cannot enter your account, email support with your registered contact detail and a short privacy request summary. We may ask for extra checks before changing or sharing account data.
Live chat handoff Live chat can receive basic privacy questions and pass complex requests to the right team. For your safety, chat will not disclose full account data until identity checks are completed.
HANDLING PRACTICE

Browse our data handling steps

We handle privacy work through defined checks rather than ad hoc replies. Payment records, account access logs, cookie choices and support messages sit in separate systems with access limited by role.

Data we collect

We collect details you give us, account activity, device signals, login times, wallet references and support messages. Each category is tied to account operation, security, payment checks, service records or legal obligations.

Cookie use

Cookies help keep sessions active, remember basic choices, measure page performance and detect unusual access. You can adjust browser settings, although some account features may not work correctly without essential cookies.

Account security

We use login checks, device signals and verification steps to reduce unauthorised access. If activity looks unusual, we may pause certain account actions until we confirm the request came from you.

Payment privacy

Touch 'n Go, GrabPay, Boost dan FPX records are used to match deposits, withdrawals and wallet checks to your account. We keep only the references needed for processing, reconciliation and dispute handling.

Retention approach

We keep data only for account operation, legal record needs, dispute handling, security checks and audit reasons. When a record is no longer needed, we delete it or separate it from personal identifiers.

Change requests

You can ask us to correct, access or delete eligible data. We verify your identity first, then explain what can be changed, what must be retained and the reason for any limit.

Discover your Privacy Policy answers

These answers focus on practical privacy matters you may raise before or after opening an account. They explain the types of data we handle, why certain records remain after a request, how cookies fit into account access and how you can contact us about your rights under applicable local law.

We collect account details you provide, contact data, login records, device signals, payment references, wallet activity, verification files and support messages. We use them for account operation, security, payment checks and legal record needs.

Payment references help us match Touch 'n Go, GrabPay, Boost dan FPX transactions to your wallet, trace failed payments and handle disputes. We use the minimum practical record for matching, reconciliation and support checks.

Yes. Send the request through the account help area when possible, or contact support if you cannot log in. We will verify your identity before preparing eligible account data for release.

You can request deletion of eligible data. Some records may need to remain for legal, payment, dispute, fraud-prevention or security reasons, and we will explain any retention limit that applies to your request.

Cookies support login sessions, page performance, basic preferences and unusual access detection. You can manage cookies through your browser, but essential account functions may fail if required session cookies are blocked.

Access is limited to staff and service providers who need the data for account operation, payment processing, verification, support, hosting, analytics or legal duties. We apply role-based access and keep request records.

Yes. Account access, eligibility and certain privacy rights depend on local law and are available where local law permits. If a legal rule affects your request, we will explain the relevant limit clearly.