Rujukan Laman

Privacy Policy for wabo22 accounts

Account data, wallet checks, cookie choices and support records sit behind every wabo22 account, so this Privacy Policy explains what we collect, why we use it and how…

Malaysia data handlingCookie choice detailsTouch 'n Go contextAccount request routes
wabo22 Privacy Policy for wabo22 accounts
CONTACT ROUTES

3 privacy contact paths

Before you share documents or ask for a data change, choose the route that matches your request.

Live chat privacy handoff Start with live chat when you need quick routing for a privacy question. We will not ask you to post full wallet credentials there; the team will move sensitive requests to a safer channel.
Email request trail Use email for correction, deletion, access or cookie questions that need a written record. Include your account ID, registered contact and a clear request so we can trace the right records.
Account security check If you think your login or personal data was exposed, contact us before making further wallet activity. We can check recent sessions, freeze risky changes and explain the next privacy steps.
DATA PRACTICES

6 controls behind your account data

Our privacy work sits inside daily account operations, not in a separate promise page. Each control below explains a practical step we use when account data, payment references, cookies or support records…

Data minimisation

We ask for account, contact and verification details that support access, wallet checks and service safety. Extra documents are requested only when a specific check requires them, not for casual browsing.

Cookie controls

Cookies help keep sessions active, remember language choices and detect suspicious account access. You can adjust browser settings, but some account functions may need session cookies to work correctly.

Access controls

Internal access is limited by work role, request type and security need. Support staff see only what they need for your case, while sensitive records require additional checks.

Retention checks

We keep account and wallet records for operational, legal, tax, dispute and security periods. When those needs end, we remove, mask or aggregate records so they are no longer tied to you.

Correction requests

If your name, contact detail or account record is wrong, send us a correction request with matching proof. We check the record, update it where appropriate and confirm the outcome.

Processor care

Payment and technical vendors may process limited data for Touch 'n Go, GrabPay, Boost dan FPX references, hosting or security. We require them to handle the data only for the agreed service purpose.

7 answers on your privacy rights

These questions focus on the practical parts of this Privacy Policy: what we collect, how long we keep it, when we share it and how you can reach us. If your concern is tied to a specific wallet transaction, support chat or login event, include the date and account contact so we can find the right record faster.

We collect details such as your name, contact number, email, login records, device signals, wallet references and support messages. Verification documents may be requested when account safety, withdrawal checks or legal duties require stronger confirmation.

Payment references help us match a wallet action to your account, confirm status, investigate disputes and keep transaction records. We do not need your full banking password or private app login to complete those checks.

Yes. Send a request through email or the privacy handoff in chat, then complete the identity check. We will provide the account data we can share, subject to security, legal and fraud-prevention limits.

Tell us which detail is wrong and provide matching proof, such as the registered contact and any document needed for the change. We will check the record, update it where appropriate and confirm the result.

We share limited data with payment processors, hosting providers, security tools and support systems when they need it to perform a service. We may also share records when law, dispute handling or account protection requires it.

Retention depends on the record type. Account, wallet, verification and support records may be kept for operational, legal, tax, dispute or security needs, then removed, masked or aggregated when those reasons no longer apply.

Eligibility and access depend on local law and are available where local law permits. Privacy requests are still handled through the stated contact paths, but some account actions may be limited by applicable rules.