Sending Data to US AI Tools: PDPA Cross-Border Rules Explained
Section 129 of the amended PDPA decides when personal data may go to AI tools hosted in the US or elsewhere: conditions, 2025 guidelines and a practical checklist.
Malaysian companies may send personal data to AI tools abroad if they meet a condition in section 129 of the amended PDPA, such as a substantially similar law at the destination, explicit consent, contract necessity, or reasonable precautions and due diligence. The Commissioner's guidelines of 29 April 2025 describe a Transfer Impact Assessment, contract clauses and binding corporate rules.
Part of the guide: PDPA and AI in Malaysia: What Companies Must Know (2026 Guide)

On this page
Most big AI services run on servers outside Malaysia. This is how the PDPA treats that.
Part of the guide: PDPA and AI in Malaysia. Checked against the amendment Act A1727 and the Commissioner's cross-border transfer guideline.
What changed on 1 April 2025?
Before, a transfer abroad was allowed to places on a list approved by the Minister, or if other conditions were met. The amended section 129 removed the list and the ministerial public-interest ground and replaced them with prescribed conditions. The Commissioner then issued the Guidelines on Cross Border Personal Data Transfer on 29 April 2025.

What are the conditions?
A controller needs at least one of these, as set out in the Commissioner's guideline:
| Condition | Meaning for an AI tool |
|---|---|
| Substantially similar law or adequate protection (s.129(2)) | You assess whether the destination's law is close to the PDPA. Done through a Transfer Impact Assessment. |
| Explicit consent (s.129(3)(a)) | Customers are told in writing which class of third party receives data and why, and agree. |
| Contract necessity (s.129(3)(b) and (c)) | The transfer is necessary to perform a contract with the person. |
| Avoiding adverse action (s.129(3)(e)) | Consent cannot be given, the transfer avoids harm, and you tried to get consent. |
| Vital interests (s.129(3)(g)) | Emergencies. |
| Legal purposes | Legal proceedings or advice. A mere possibility of future proceedings is not enough. |
| Reasonable precautions and due diligence (s.129(3)(f)) | You make sure the data will not be processed abroad in a way that would breach the PDPA if done in Malaysia. |
For ordinary business use of an AI tool, the realistic routes are the assessment of the destination's law, consent, or due diligence backed by contract.
What is a Transfer Impact Assessment?
A written assessment of whether the destination gives protection similar to the PDPA. The guidelines list factors: data subject rights, data protection principles, DPO and breach notification requirements, processor obligations, and the regulator's existence and powers. The result can be relied on for up to three years, with a review after significant changes.

What contract clauses help?
The guidelines name the ASEAN Model Contractual Clauses and the EU Standard Contractual Clauses as examples. In practice you want: purpose limits, security measures, sub-processor approval, breach notice, deletion and return, audit cooperation, and a promise to apply PDPA-equivalent protection. If EU data is involved too, the transfer rules run the other way as well; see GDPR vs PDPA Malaysia.
What is a practical checklist?
- List which AI tools send personal data abroad and to which countries (ask for the vendor's data location page).
- Record the route you rely on for each tool.
- Run a short Transfer Impact Assessment for each destination, reuse it across tools.
- Check the vendor contract for the clauses above.
- Update your privacy notice to mention overseas service providers.
- Re-check in three years or when the law changes.
Are there options that avoid the problem?
Yes: tools with a Malaysian or regional data location, private deployments, or removing personal data before sending. Check what is stored "at rest" versus where processing happens. Ask each vendor for its current data-location page and plan; we have not verified any vendor's regional options here. See Data residency and the Malaysian sovereign cloud and LLM data boundaries.
Choosing tools with cross-border rules in mind is part of the governance session in AI Strategy for Leaders.
What next?
Pick your three most-used AI tools and fill the checklist for them this week. If you want help, an AI opportunity audit maps the flows. Book a call.
Sources
(checked November 2026)
- Personal Data Protection Department Malaysia, Guidelines on Cross Border Personal Data Transfer (29 April 2025)
- Personal Data Protection (Amendment) Act 2024, Act A1727, section 12 (amending section 129)
- Personal Data Protection Department Malaysia, Act 709
General information, not legal advice. Have counsel confirm your transfer basis.
Frequently asked questions
Is the US a whitelisted country under the PDPA?
There is no whitelist any more. The Minister's list of places was removed on 1 April 2025. Each transfer is tested against the conditions in section 129.
Do I need consent to use a US-hosted AI service?
Not always. Consent is one of several routes. If you rely on another route, such as reasonable precautions and due diligence backed by a contract, consent may not be needed, but your privacy notice should still mention the disclosure.
How long is a Transfer Impact Assessment valid?
The [Commissioner's guideline](https://www.pdp.gov.my/wp-content/uploads/2025/08/GP_CBPDT_EN-1.pdf) says findings can be relied on for up to three years, with a review earlier if the destination's law or protection changes significantly.
Does hosting in Malaysia remove the issue?
If data stays in Malaysia, including vendor sub-processors and support access, the cross-border rules are not triggered. Check support staff access and backups, which can move data abroad.