Malaysia AI Compliance Guide
Plain-English walkthrough of how to deploy AI lawfully when end-users are in this country.
How AI law works in Malaysia
Malaysia has not enacted an AI statute, and that is a measurement over the whole register rather than a summary: the Attorney General’s Chambers publishes the complete Laws of Malaysia series as its own PDF export, and the words “artificial intelligence”, “kecerdasan buatan” and “algoritma” appear nowhere across roughly 700 principal Acts — nor anywhere in the separate Amendment Acts series. Malaysia established a National AI Office in December 2024 and MOSTI published National Guidelines on AI Governance & Ethics in 2024, both of which are policy and neither of which creates an obligation. What binds a business deploying AI in Malaysia is the digital stack that does exist: the Personal Data Protection Act 2010 (Act 709), whose seven Personal Data Protection Principles — General, Notice and Choice, Disclosure, Security, Retention, Data Integrity and Access — govern any personal data used to train or run a system, and which was significantly amended in 2024; the Cyber Security Act 2024 (Act 854), which imposes duties on entities running National Critical Information Infrastructure; the Online Safety Act 2025 (Act 866), which regulates harmful online content and applies to platform providers; the Communications and Multimedia Act 1998 (Act 588), under which the MCMC licenses and regulates network and content services; and the Computer Crimes Act 1997 (Act 563).
Applicable laws
- 📜 Act 709 — Personal Data Protection Act 2010 (amended by Act A1727, the Personal Data Protection (Amendment) Act 2024)
- 📜 Act 866 — Online Safety Act 2025
- 📜 Act 854 — Cyber Security Act 2024
- 📜 Act 588 — Communications and Multimedia Act 1998
- 📜 National Guidelines on AI Governance & Ethics (MOSTI, 2024 — voluntary)
A sequential implementation roadmap for EU AI Act compliance in Malaysia begins immediately and runs through August 2, 2026. Month 1 (now): Conduct a complete inventory of all AI systems. Document what each system does, what data it uses, whether you built it or procured it, and where it is deployed. Classify each system by risk level (prohibited, high-risk, limited-risk, minimal-risk). Identify any prohibited systems and plan immediate remediation. Identify all high-risk systems and flag them for urgent assessment. Month 2-3: Engage technical and legal experts to conduct conformity assessments for all high-risk systems. Execute bias and fairness testing, focusing on protected characteristics (race, color, religion, national origin, sex, gender identity, sexual orientation, disability, age). Document assessment results and identify any disparate impact requiring mitigation.
Months 4-6: Implement transparency mechanisms and human-review processes. Add clear, accessible disclosures to high-risk systems notifying affected individuals that they are subject to AI decisions, explaining how the system works, and providing contact information for questions or appeals. Establish a documented human-review process with trained personnel authorized to override AI decisions. Begin audit logging for all high-risk decisions. Test the transparency and human-review workflows to ensure they work as designed. Month 6-8: Complete remediation of any deficiencies identified in conformity assessment and bias testing. Retrain models if bias was detected, adjust decision thresholds, or restrict system scope if necessary. Finalize documentation of all compliance activities. Conduct an internal audit against the EU AI Act's requirements to verify readiness.
Months 8-12: Establish permanent compliance governance. Designate a compliance owner responsible for maintaining the AI inventory, tracking regulatory updates, coordinating vendor management, and responding to individual rights requests. Establish a schedule for annual re-assessment and bias re-testing of high-risk systems. Implement staff training on EU AI Act obligations, transparency procedures, and escalation pathways. Create a compliance manual documenting your AI systems, assessment processes, risk mitigation, and governance. June-August 2026: Conduct a final readiness review. Verify that all high-risk systems have passed conformity assessment and bias testing, that all transparency and human-review processes are operational, that audit logs are functional, and that staff are trained. Prepare documentation for potential regulatory inspection.
High-priority actions for businesses with high-risk hiring, benefits, or law-enforcement systems: These systems face the highest penalty exposure and scrutiny. Conduct immediate and thorough bias testing, focusing on gender, race, age, and disability disparities. If bias is detected, consider whether the system should be removed from production immediately or remediated in-place. Either path requires documented justification and urgency. For high-risk benefits systems (loan decisions, insurance eligibility, social services), ensure that individuals can request human re-evaluation and have a genuine appeal process. For any system already deployed and now identified as high-risk, document the date you discovered the non-compliance and the steps you took to remediate — this documentation can reduce penalties by demonstrating good faith.
Emergency remediation for systems discovered to be non-compliant close to August 2, 2026: If you discover a high-risk system lacks conformity assessment or you cannot complete bias testing in time, document what you have completed, what remains outstanding, and your timeline for completion. Remove or suspend the system if remediation cannot be completed before August 2. If you keep the system in operation pending completion of assessment, document the risk and your remediation plan — this can provide a defense against maximum penalties by demonstrating that you were actively working toward compliance at enforcement. Do not attempt to hide or conceal non-compliant systems — transparency with regulators and documented good-faith effort to remediate are your best defenses against severe penalties.
The Malaysia AI compliance walkthrough
Map every AI system that touches Malaysia users
3-5 daysIncluding embedded AI inside SaaS tools (assistants, recommendation engines, autocomplete). Note vendor, training-data provenance, and where the output is acted on.
Classify each system against EU AI Act risk tiers
2-3 daysProhibited / high-risk / limited-risk / minimal. The classification decides whether you need a conformity assessment, technical file, registration, transparency labels — or just minimal-risk best practice.
Run a DPIA + bias assessment for every high-impact system
1-2 weeks per systemUse a written template covering: purpose, training data, validation, fairness across protected classes, security, human override, contestation. The artifact is what regulators and plaintiffs ask for.
Update Malaysia disclosures and consent flows
1 weekPlain-language notice, before the AI decision is final, in the user's language. Article 50 transparency where AI-generated content is involved. Cross-link your privacy policy to your AI policy.
Wire technical + contractual controls
2-4 weeksAudit logs, prompt/response retention, vendor DPAs + AI Act addendums, content provenance (C2PA), opt-out mechanism, EU representative designation if established outside the EU.
Train, monitor, re-assess
OngoingTrain every staff member touching the system; designate a complaint owner; review logs monthly; quarterly governance review; re-assess annually + after every material model update; report serious incidents to the supervisory authority.
More Malaysia resources
Other countries
Anchored to the primary government source (statute, bill text, or agency rule) and verified directly against it · Last verified Aug 31, 2026. See our methodology.
- ↗lom.agc.gov.myhttps://lom.agc.gov.my/principal.php?type=updated
- ↗lom.agc.gov.myhttps://lom.agc.gov.my/principal.php?type=amendment
- ↗pdp.gov.myhttps://www.pdp.gov.my/ppdpv1/akta/akta-pdp-2010-my/