Data Protection Monitor
Global Privacy & Data Protection Intelligence

Malaysia Data Protection & Privacy Regulation

MY schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 125 claims · 53 sources in the cumulative register

Malaysia's data protection regime underwent its most significant structural tightening since the Personal Data Protection Act 2010's original enactment, with all three phases of the Personal Data Protection (Amendment) Act 2024 now in force.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Sectoral Watch, Algorithmic, Biometric & Surveillance Governance (3 open gaps).

Framework & posture10 of 10 modules active
10 active · 14 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix125 claims · 39 sources · machine-compiled
65 Probable58 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

Jurisdiction brief

Latest update · 4 November 2026

Lead Signal

Malaysia's data protection regime is in the midst of a phased tightening that this cycle shows advancing on several fronts at once. The Personal Data Protection (Amendment) Act 2024 (Act A1727), whose core changes are being phased in across 2025, has raised the maximum fine for breach of the data protection principles from RM300,000 to RM1,000,000, introduced a mandatory breach-notification duty under a new section 12B, and created a mandatory duty to appoint a data protection officer for organisations processing personal data at scale or handling sensitive categories. Alongside these statutory changes, the Department of Personal Data Protection issued final guidelines on data protection impact assessments, data protection by design, and automated decision-making and profiling on 8 May 2026, concluding a 2025 consultation process, and most recently opened a public consultation, closed 23 October 2026, on a draft ten-part, forty-three-section AI and Personal Data Protection Framework.

Key regulatory facts for Malaysia
Key regulatory facts for Malaysia
Regulatory DimensionMalaysia Standing Position
JurisdictionMalaysia (MY)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 125 sourced findings)
Regulator & FrameworkComprehensive statute in force with a fully commenced modernising amendment; core institutional architecture (Commissioner + PDP) is stable and actively issuing implementing guidance.
Lawful Processing & Special DataCore consent/sensitive-data architecture is well evidenced and in force, but consent-threshold specifics (freely-given/withdrawal standard) and pseudonymisation/anonymisation treatment were not confirmed via primary-source retrieval in this run.
Data Subject RightsAccess, correction and (newly) portability rights are well evidenced and in force; restriction/objection rights and precise response deadlines remain unconfirmed gaps.
Controller/Processor DutiesDPO, breach-notification, security and retention duties are strongly evidenced and in force; DPIA/ROPA/joint-controller equivalents remain unconfirmed gaps versus the GDPR baseline.
Primary Instruments CitedDataGuidance (hosted copy of official Act text), DataGuidance, Malaysia Official Instrument (onekeybiz.com malaysia-pdpa-amendment-2024-dat), Malaysia Official Instrument (recordinglaw.com malaysia-data-privacy-laws), negaraku.md
Last Confirmed / Updated (53 sources in cumulative register)

#

Comprehensive statute in force with a fully commenced modernising amendment; core institutional architecture (Commissioner + PDP) is stable and actively issuing implementing guidance.

Primary frameworkPersonal Data Protection Act 2010 (Act 709), as amended by the Personal Data Protection (Amendment) Act 2024
Traffic-light rationale — GreenComprehensive statute in force with a fully commenced modernising amendment; core institutional architecture (Commissioner + PDP) is stable and actively issuing implementing guidance.

Sub-modules (5)

Regulator and authorityGreen

The Commissioner, assisted by PDP, administers and enforces the PDPA.

Claims (5):

  • The PDPA confers powers to the Personal Data Protection Commissioner, who is assisted by the Department of Personal Data Protection (PDP) to administer and enforce the provisions of the PDPA.
  • Department of Personal Data Protection (JPDP) — Malaysia's primary data-protection regulator, distinct from the Securities Commission's crypto/DAX role
  • JPDP was established on 16 May 2011 and operates under the Digital Ministry, assisting the Personal Data Protection Commissioner in enforcing the PDPA.
  • Department of Personal Data Protection (JPDP) — JPDP, under the Ministry of Digital, administers and enforces the PDPA, assisting the Personal Data Protection Commissioner.
  • Jabatan Perlindungan Data Peribadi (JPDP) — Securities Commission Malaysia, which holds a separate regulatory role over crypto-assets and DAX under its own statutory mandate; the two regimes run in parallel

Act and instrumentsGreen

PDPA 2010 in force since 15 November 2013; Amendment Act 2024 gazetted 17 October 2024 with staged commencement through 1 June 2025.

Claims (8):

  • The Personal Data Protection (Amendment) Act 2024 was published in the Gazette on 17 October 2024 after receiving Royal Assent on 9 October 2024, following passage by the Senate (31 July 2024) and House of Representatives (16 July 2024).
  • The Amendment Act's provisions were implemented in stages, with sections coming into effect on 1 January, 1 April, and 1 June 2025, covering biometric data, controller/processor terminology, cross-border transfer rules, DPO appointment, breach notification and portability respectively.
  • Personal Data Protection (Amendment) Act 2024 (Act A1727) — Amended Act 709, with headline obligations (breach notification, DPO) phased into force through 2025, replacing 'data user' with 'data controller' throughout.
  • Personal Data Protection (Amendment) Act 2024 — Received Royal Assent on 9 October 2024 and was gazetted 17 October 2024, phasing in mandatory DPO appointment and breach notification from 1 June 2025
  • The Personal Data Protection (Amendment) Act 2024 (Act A1727) made several core changes to the PDPA, phased in across 2025.
  • JPDP Public Consultation Paper No. 1/2026 — JPDP published Public Consultation Paper No. 1/2026 on 5 October 2026, a draft AI and Personal Data Protection Framework (10 parts, 43 sections) with seven consultation questions, comment period closing 23 October 2026.
  • Personal Data Protection (Amendment) Act 2024 (Act A1727) — Royal Assent 9 October 2024; published in Federal Gazette 17 October 2024
  • Personal Data Protection (Amendment) Act 2024 (Act A1727) — Renamed 'data user' to 'data controller' throughout the PDPA and introduced mandatory breach notification (s.12B), a mandatory DPO duty (s.12A), biometric data as sensitive personal data, and a data portability right, phased in 1 January, 1 April and 1 June 2025.

Material scopeGreen

PDPA covers processing of personal data in commercial transactions by an establishment in Malaysia or using equipment in Malaysia.

Claims (2):

  • The PDPA regulates the processing of personal data in commercial transactions either by an establishment in Malaysia or with equipment in Malaysia, unless the personal data only transits through Malaysia.
  • Personal Data Protection Act 2010 (Act 709) — The PDPA does not apply to the Federal Government, a scope exclusion unchanged by the 2024 Amendment.

Territorial scopeAmber

Extraterritorial reach is anchored to use of equipment in Malaysia rather than a pure establishment test; transit-only data is excluded.

Claims (1):

  • Extraterritorial application of the PDPA turns on use of equipment located in Malaysia (an equipment-based test), rather than a GDPR-style establishment/targeting test; data merely transiting Malaysia is expressly excluded.

Regulator registration and filingGreen

PDP mandates registration of 13 designated classes of data controllers/users, and separately requires DPO-appointment notification within 21 days via a dedicated registration manual.

Claims (4):

  • PDP mandates registration for 13 designated classes/groups of data controllers under the PDPA, with penalties for non-compliance with the registration requirement.
  • Controllers and processors must notify the Commissioner of DPO appointments; PDP's DPO registration manual requires such notification within 21 days of appointment.
  • PDPA registration regime — The 2024 Amendment did not alter pre-existing data-controller registration requirements
  • Personal Data Protection Act 2010 (Act 709), s.15 — The 2024 Amendment Act did not alter the s.15 registrable-class registration duty or the registrable classes (13/14 classes)
Category narrative 94 words

Malaysia's data-protection regime is anchored in the Personal Data Protection Act 2010 (Act 709, 'PDPA'), administered by the Personal Data Protection Commissioner supported by the Department of Personal Data Protection (Jabatan Perlindungan Data Peribadi, 'PDP'). The regime was materially modernised by the Personal Data Protection (Amendment) Act 2024, gazetted 17 October 2024 following Royal Assent, and commenced in three stages across 1 January, 1 April and 1 June 2025, bringing DPO appointment, mandatory breach notification, portability, processor accountability and revised cross-border rules into force. As of this run all staged provisions are in force.

Periodic update · new data 2026-11-08

The Department of Personal Data Protection, operating under the Ministry of Digital, administers and enforces the Personal Data Protection Act, assisting the Personal Data Protection Commissioner in that function. This regulatory structure remains the settled institutional anchor for data protection oversight in Malaysia.

The department published Public Consultation Paper No. 1/2026 on 5 October 2026, setting out a draft Artificial Intelligence and Personal Data Protection Framework comprising ten parts and forty-three sections, accompanied by seven consultation questions. The comment period closed on 23 October 2026. No outcome document or finalised framework has been located following the close of that consultation window, so the framework's eventual form and binding status remain to be determined. The consultation paper itself is understood to represent an early-stage instrument; it has not been enacted and carries no binding effect at this stage.

Outlook

The principal matter to watch is whether the Department of Personal Data Protection issues a response paper or finalised framework following the close of the AI and Personal Data Protection Framework consultation on 23 October 2026. Given the scale of the draft instrument, ten parts and forty-three sections, any finalised version would represent a significant addition to the regulator's framework for governing AI systems that process personal data, and its eventual stage, whether guidance, binding rule, or further consultation, is not yet known.

3 earlier distinct updates
Periodic update · new data 2026-10-25

The Personal Data Protection (Amendment) Act 2024, cited as Act A1727, amended the Personal Data Protection Act 2010, cited as Act 709, and is understood to have replaced the term data user with data controller throughout the principal legislation. The amendment's headline obligations are being phased into force through 2025, a process that continues into 2026 with the finalisation of supporting guidance. This is a structural shift in the vocabulary and architecture of the framework rather than a replacement of the underlying statute, which remains Act 709 as amended.

A scope exclusion that predates the 2024 Amendment and is understood to remain unchanged by it is that the Personal Data Protection Act does not apply to the Federal Government. The exact provision establishing this exclusion has not been pinpointed in the sourcing available, but the exclusion itself, and its continuity through the amendment process, is reported consistently. This means that as the amended private-sector regime tightens, in particular through the new breach notification, Data Protection Officer, and cross-border transfer obligations addressed elsewhere, federal government processing activity remains outside the amended framework's reach, a structural gap that has not altered.

The terminology shift from data user to data controller is itself a signal of the amendment's intent to align Malaysian nomenclature more closely with the international data protection vocabulary used in frameworks such as the GDPR, even though the Malaysian regime remains its own distinct statutory creature rather than an adopted equivalent. The phase-in through 2025 means that, as at the time of this cycle, certain obligations tied to the amendment are already in force while others, in particular supporting guidance such as the Data Protection Impact Assessment and Automated Decision-Making guideline only finalised on 8 May 2026, have only recently reached completion.

No primary gazette text of Act A1727 was directly retrieved, and the pinpoint provision numbers for the federal government exclusion and for several of the amendment's new rights remain unconfirmed against the primary instrument. This is noted as a sourcing gap rather than a substantive uncertainty about whether the amendment has taken effect, which multiple secondary sources confirm consistently.

Outlook

The framework's near-term trajectory is one of continued consolidation around the 2024 Amendment's phased-in obligations, with the practical content of the regime increasingly defined by implementing guidance, such as the DPIA and Automated Decision-Making guideline, rather than by further amendment of the primary Act itself. Confirmation of the pinpoint statutory basis for the Federal Government exclusion and related provisions, ideally from a primary gazette text, would close the principal sourcing gap identified.

Periodic update · new data 2026-10-12

Two distinct developments mark Malaysia's regulatory-framework landscape this period, at different stages of maturity. The more material of the two is the Department of Personal Data Protection's publication of Public Consultation Paper No. 1/2026 on 5 October 2026, circulating a draft AI and Personal Data Protection Framework (Version 1.0) structured across 10 parts and 43 sections, accompanied by seven consultation questions. Comments on the draft are open until 23 October 2026. This is confirmed as a live, dated regulatory instrument in its consultation stage; neither its final text, its issue date as a settled instrument, nor any transition period for compliance has yet been determined, and those remain open questions this instrument's eventual finalization will need to resolve.

Separately, and at an earlier stage, the Ministry of Digital has proposed elevating the Commissioner's office into a full-fledged independent data commission, with the stated aim of enhancing enforcement and oversight powers. This proposal carries Probable confidence and no enabling instrument, bill number, or commencement date has been identified in sources reviewed this period; it is a stated policy intention rather than a drafted or tabled legislative instrument. The two developments are related in theme, both point toward strengthening Malaysia's institutional data-protection architecture, but they are at materially different stages: the AI framework is a live consultation document with a specified closing date, while the commission-elevation proposal has no identified procedural vehicle at all.

The practical significance of the AI framework consultation is that it represents Malaysia's chosen regulatory strategy for AI-driven personal data processing: rather than amending the core Personal Data Protection Act 2010 to insert AI-specific provisions, JPDP is building a freestanding, structured instrument addressing the AI lifecycle. This sector-specific approach means organizations processing personal data through AI systems in Malaysia should expect a distinct compliance instrument to sit alongside, rather than be folded into, their existing PDPA obligations once this framework is finalized.

Outlook

The consultation on the draft AI and Personal Data Protection Framework closes 23 October 2026; the period following that date is the clearest marker to watch, as it will determine whether JPDP proceeds to a finalized instrument, what any transition period looks like, and whether the records-keeping and other obligations in the draft survive consultation substantially unchanged. The proposal to elevate the Commissioner's office into an independent data commission remains, by contrast, a longer-horizon and currently unscheduled development, with no legislative vehicle yet identified to track toward a commencement date.

Periodic update · new data 2026-09-28

Malaysia's Department of Personal Data Protection (JPDP) is the jurisdiction's primary data-protection regulator, distinct from the Securities Commission's role in the crypto and digital-asset-exchange space. The foundational statute, the Personal Data Protection Act 2010, has been substantially amended by the Personal Data Protection (Amendment) Act 2024 (Act A1727), which represents the most significant legislative modernisation of Malaysia's data-protection regime since the original Act's passage. Commencement of the amendment's various provisions is being staged through Ministerial Gazette notification, meaning different substantive changes have taken effect, or will take effect, on different dates rather than through a single commencement.

The exact phased commencement schedule by individual provision was not fully retrieved this cycle, and the primary source confirms only that different provisions commence via separate Gazette notifications rather than laying out the complete provision-by-provision timetable. What is confirmed is that key substantive changes, including the breach-notification and DPO requirements discussed under Controller/Processor Duties, are already in force.

Outlook

As further Ministerial Gazette notifications bring additional Amendment Act provisions into force, the phased-commencement picture should become progressively clearer. Tracking each notification as it is published will be necessary to establish a complete effective-date map for the full amendment package.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (22)
  1. Confirmed DataGuidance — The PDPA confers powers to the Personal Data Protection Commissioner, who is assisted by the Department of Personal Data Protection (PDP) to administer and enforce the provisions of the PDPA. observed
  2. Confirmed DataGuidance — The Personal Data Protection (Amendment) Act 2024 was published in the Gazette on 17 October 2024 after receiving Royal Assent on 9 October 2024, following passage by the Senate (31 July 2024) and House of Representatives (16 July 2024). observed
  3. Confirmed DataGuidance — The Amendment Act's provisions were implemented in stages, with sections coming into effect on 1 January, 1 April, and 1 June 2025, covering biometric data, controller/processor terminology, cross-border transfer rules, DPO appointment, breach notification and portability respectively. observed
  4. Confirmed DataGuidance — The PDPA regulates the processing of personal data in commercial transactions either by an establishment in Malaysia or with equipment in Malaysia, unless the personal data only transits through Malaysia. observed
  5. Probable DataGuidance — Extraterritorial application of the PDPA turns on use of equipment located in Malaysia (an equipment-based test), rather than a GDPR-style establishment/targeting test; data merely transiting Malaysia is expressly excluded. observed
  6. Confirmed DataGuidance — PDP mandates registration for 13 designated classes/groups of data controllers under the PDPA, with penalties for non-compliance with the registration requirement. observed
  7. Confirmed DataGuidance — Controllers and processors must notify the Commissioner of DPO appointments; PDP's DPO registration manual requires such notification within 21 days of appointment. observed
  8. Probable https://onekeybiz.com/insights/malaysia-pdpa-amendment-2024-data-protection-compliance-foreign-companies.html — Personal Data Protection (Amendment) Act 2024 (Act A1727) — Amended Act 709, with headline obligations (breach notification, DPO) phased into force through 2025, replacing 'data user' with 'data controller' throughout.
  9. Probable https://www.recordinglaw.com/world-laws/world-data-privacy-laws/malaysia-data-privacy-laws/ — Personal Data Protection Act 2010 (Act 709) — The PDPA does not apply to the Federal Government, a scope exclusion unchanged by the 2024 Amendment.
  10. Confirmed Department of Personal Data Protection — Department of Personal Data Protection (JPDP) — Malaysia's primary data-protection regulator, distinct from the Securities Commission's crypto/DAX role observed
  11. Probable DataGuidance — Personal Data Protection (Amendment) Act 2024 — Received Royal Assent on 9 October 2024 and was gazetted 17 October 2024, phasing in mandatory DPO appointment and breach notification from 1 June 2025 observed
  12. Probable negaraku.md — PDPA registration regime — The 2024 Amendment did not alter pre-existing data-controller registration requirements observed
  13. Probable Orbixtech — JPDP was established on 16 May 2011 and operates under the Digital Ministry, assisting the Personal Data Protection Commissioner in enforcing the PDPA. observed
  14. Probable Orbixtech — The Personal Data Protection (Amendment) Act 2024 (Act A1727) made several core changes to the PDPA, phased in across 2025. observed
  15. Confirmed Department of Personal Data Protection — Department of Personal Data Protection (JPDP) — JPDP, under the Ministry of Digital, administers and enforces the PDPA, assisting the Personal Data Protection Commissioner. observed
  16. Probable dataprotection.gi — JPDP Public Consultation Paper No. 1/2026 — JPDP published Public Consultation Paper No. 1/2026 on 5 October 2026, a draft AI and Personal Data Protection Framework (10 parts, 43 sections) with seven consultation questions, comment period closing 23 October 2026. observed
  17. ? Primary statutory record — Personal Data Protection (Amendment) Act 2024 — Biometric data, effective 1 April 2025
  18. ? Primary statutory record — PDPA s.43A — Data portability, effective 1 June 2025
  19. Probable Malaysian Institute of Chartered Secretaries and Administrators (MAICSA) — Personal Data Protection (Amendment) Act 2024 (Act A1727) — Royal Assent 9 October 2024; published in Federal Gazette 17 October 2024 observed
  20. Confirmed DataProtection.gi (tracker) — Jabatan Perlindungan Data Peribadi (JPDP) — Securities Commission Malaysia, which holds a separate regulatory role over crypto-assets and DAX under its own statutory mandate; the two regimes run in parallel observed
  21. Probable Recording Law — Personal Data Protection Act 2010 (Act 709), s.15 — The 2024 Amendment Act did not alter the s.15 registrable-class registration duty or the registrable classes (13/14 classes) observed
  22. Probable Department of Personal Data Protection — Personal Data Protection (Amendment) Act 2024 (Act A1727) — Renamed 'data user' to 'data controller' throughout the PDPA and introduced mandatory breach notification (s.12B), a mandatory DPO duty (s.12A), biometric data as sensitive personal data, and a data portability right, phased in 1 January, 1 April and 1 June 2025. observed

#

Core consent/sensitive-data architecture is well evidenced and in force, but consent-threshold specifics (freely-given/withdrawal standard) and pseudonymisation/anonymisation treatment were not confirmed via primary-source retrieval in this run.

Primary frameworkPersonal Data Protection Act 2010, ss.6 and 40, as amended by the Personal Data Protection (Amendment) Act 2024
Traffic-light rationale — AmberCore consent/sensitive-data architecture is well evidenced and in force, but consent-threshold specifics (freely-given/withdrawal standard) and pseudonymisation/anonymisation treatment were not confirmed via primary-source retrieval in this run.

Sub-modules (4)

Lawful basesAmber

Consent is the primary lawful basis; limited statutory exceptions exist for contract performance/formation and legal-obligation compliance. Malaysia lacks a standalone legitimate-interest basis.

Claims (3):

  • Under section 6(1) of the PDPA, a data user must not process personal data unless the data subject has given consent, or, for sensitive personal data, unless processing accords with section 40.
  • Notwithstanding the general consent requirement, section 6(2) permits processing necessary for performance of, or steps toward, a contract with the data subject, or for compliance with a legal obligation.
  • Malaysia is identified, alongside China, India and Vietnam, as one of the reviewed Asia-Pacific jurisdictions that presently lacks a distinct legitimate-interest lawful basis for processing personal data.

Special categoriesGreen

Biometric data is newly classified as sensitive personal data under the Amendment Act; deceased-persons' data is expressly placed outside the Act's scope.

Claims (7):

  • The Amendment Act recognises biometric data as sensitive personal data, defined as personal data resulting from technical processing relating to the physical, physiological or behavioural characteristics of a person.
  • Data of deceased persons is excluded from the Amendment Act and placed expressly outside the PDPA's application.
  • Personal Data Protection (Amendment) Act 2024 — Biometric data is now expressly 'sensitive personal data', triggering heightened processing conditions.
  • Data processors (Malaysia) — Data processors are now directly liable for compliance with the Security Principle, not only data controllers, following the 2024 Amendment.
  • Personal Data Protection (Amendment) Act 2024 — Biometric data (fingerprints, facial recognition, voice, retinal scans) as a new category of sensitive personal data, effective 1 April 2025
  • Biometric data is classified as sensitive personal data under the Amendment Act.
  • Personal Data Protection (Amendment) Act 2024 (Act A1727) — Biometric data added as sensitive personal data, effective 1 April 2025 (Phase 2 commencement)

Pseudonymisation and anonymisationRed

No PDPA provision defining pseudonymisation or an anonymisation safe-harbour was located in the reviewed primary text or amendment commentary.

Claims (1):

  • No express PDPA provision defining pseudonymisation or providing an anonymisation safe-harbour was identified in the reviewed Act text or Amendment Act commentary.
Category narrative 83 words

The PDPA operates on a consent-centric lawfulness model rather than a GDPR-style multi-basis Article 6 structure: general personal data requires data-subject consent (with limited contract/legal-obligation exceptions), and sensitive personal data requires compliance with the dedicated section 40 regime. Malaysia is noted among APAC jurisdictions as presently lacking a stand-alone 'legitimate interest' basis. The 2024 Amendment Act's headline change to this module is the addition of biometric data as a new sensitive-personal-data category, alongside express exclusion of deceased persons' data from the Act's application.

Periodic update · new data 2026-11-04

The principal development affecting lawful processing in Malaysia is the extension of the sensitive personal data category to include biometric data, such as fingerprint and facial recognition data, under section 4 of the Personal Data Protection Act 2010 as amended by the Personal Data Protection (Amendment) Act 2024. Before this change, biometric identifiers sat in a comparatively ambiguous position within the statute, and organisations deploying biometric authentication, access control, or surveillance technologies could process such data without necessarily meeting the heightened consent and processing conditions that apply to sensitive categories. The amendment closes that gap, bringing biometric processing within the same elevated threshold already applied to categories such as health and religious data.

The practical effect is to raise the compliance bar for a growing category of commercial and institutional deployment. Biometric authentication has expanded rapidly across banking, workplace access control, and consumer-facing applications in Malaysia, and organisations that adopted such technology under the pre-amendment regime are now operating under a stricter lawful basis requirement than when they first deployed it. This is a structural reclassification rather than an enforcement event, and its significance lies in how it reframes the baseline obligation facing an entire category of processing activity, rather than in any single compliance action taken under it so far.

No other sensitive-category or lawful-basis development was identified. The reclassification sits within the broader phased implementation of the Amendment Act across 2025, and its practical enforcement is likely to be read alongside the Department of Personal Data Protection's finalised accountability guidance, including the data protection impact assessment guideline, given that biometric processing is explicitly treated as a high-risk factor under that framework.

Outlook

Organisations relying on biometric data for authentication or identification purposes face a compliance landscape in which the sensitive-category threshold is now settled law rather than an open question. The absence of published enforcement activity specifically targeting biometric processing to date suggests the Department of Personal Data Protection may be allowing a period of adjustment before testing the new classification through enforcement, consistent with the broader phased rollout of the Amendment Act. Organisations should expect that the reclassification will increasingly intersect with the data protection impact assessment expectations set out in the Department's May 2026 guidance, given biometric data's status as both a sensitive category and a high-risk processing factor.

2 earlier distinct updates
Periodic update · new data 2026-10-25

The 2024 Amendment is understood to have brought biometric data expressly within the category of sensitive personal data under the Malaysian framework, a reclassification that triggers the heightened processing conditions attached to that category. Prior to this change, biometric identifiers sat in a less clearly defined position within the statutory taxonomy of personal data, and their express inclusion as sensitive personal data represents a tightening of the conditions under which organisations may lawfully process fingerprint, facial recognition, or other biometric identifiers in Malaysia.

A second, structurally significant change introduced by the same amendment is that data processors are now understood to be directly liable for compliance with the Security Principle, rather than that obligation resting solely with data controllers as under the original 2010 Act. This extends accountability for data security failures to the processor layer of the data-handling chain for the first time, meaning that an organisation engaged purely as a processor, rather than as the controller determining the purposes of processing, can now be held directly responsible for security principle compliance in its own right.

Both of these developments should be read together as part of the same amendment's broader effort to tighten the conditions attached to higher-risk categories of data and distribute accountability more evenly across the data-handling chain. The biometric reclassification raises the bar for lawful processing of a category of data that is increasingly used in digital onboarding, authentication, and surveillance contexts, while the processor liability extension closes what had been a gap in the original 2010 framework, under which a processor handling data on behalf of a controller could not be held directly accountable for security failures regardless of its own conduct.

The sourcing for both changes rests on secondary commentary rather than a primary gazette pinpoint, and the exact provisions establishing the biometric reclassification and the processor liability extension have not been located. The substance of both changes, however, is reported consistently and is dated to the same 1 June 2025 phase-in point as the amendment's other headline obligations.

Outlook

The practical effect of the biometric reclassification will likely become clearer as organisations handling biometric data for authentication or surveillance purposes adjust their lawful-processing bases to meet the heightened conditions attached to sensitive personal data. Similarly, the processor liability extension for the Security Principle will be tested in practice as processors, rather than only controllers, come under direct scrutiny for security failures, though no such test has yet been identified in the available sourcing.

Periodic update · new data 2026-09-28

Malaysia's category of sensitive personal data has been expanded by the Personal Data Protection (Amendment) Act 2024 to include biometric data, specifically fingerprints, facial recognition data, voice data and retinal scans, effective 1 April 2025. This addition subjects biometric data to the same heightened processing threshold already applicable to other sensitive-personal-data categories under the PDPA, meaning controllers processing biometric data for identity verification, authentication or similar purposes must now satisfy the corresponding stricter lawful-basis requirements applicable to sensitive categories rather than the general lawful-processing threshold.

This reclassification is particularly relevant given the growing use of biometric authentication in Malaysian consumer-facing financial and digital services. Controllers that had previously processed biometric identifiers under the general lawful-processing threshold, prior to 1 April 2025, would need to have transitioned their lawful-basis analysis to satisfy the sensitive-category requirements from that effective date forward.

Outlook

Watch for JPDP guidance clarifying the practical lawful-basis expectations for biometric processing specifically, given that this is a newly-created sensitive category rather than one with an established body of Malaysian regulatory interpretation. Sectors making heavy use of biometric authentication, including financial services, should be an early focus for any JPDP compliance-monitoring activity.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (12)
  1. Confirmed DataGuidance (hosted copy of official Act text) — Under section 6(1) of the PDPA, a data user must not process personal data unless the data subject has given consent, or, for sensitive personal data, unless processing accords with section 40. observed
  2. Confirmed DataGuidance (hosted copy of official Act text) — Notwithstanding the general consent requirement, section 6(2) permits processing necessary for performance of, or steps toward, a contract with the data subject, or for compliance with a legal obligation. observed
  3. Probable PDPC Singapore — Malaysia is identified, alongside China, India and Vietnam, as one of the reviewed Asia-Pacific jurisdictions that presently lacks a distinct legitimate-interest lawful basis for processing personal data. observed
  4. Confirmed IAPP — The Amendment Act recognises biometric data as sensitive personal data, defined as personal data resulting from technical processing relating to the physical, physiological or behavioural characteristics of a person. observed
  5. Confirmed IAPP — Data of deceased persons is excluded from the Amendment Act and placed expressly outside the PDPA's application. observed
  6. Uncertain DataGuidance (hosted copy of official Act text) — No confirmed primary-source detail was retrieved in this research pass specifying the PDPA's precise consent-validity thresholds (e.g., freely-given, specific, withdrawal mechanics) as amended. observed
  7. Uncertain DataGuidance (hosted copy of official Act text) — No express PDPA provision defining pseudonymisation or providing an anonymisation safe-harbour was identified in the reviewed Act text or Amendment Act commentary. observed
  8. Probable https://onekeybiz.com/insights/malaysia-pdpa-amendment-2024-data-protection-compliance-foreign-companies.html — Personal Data Protection (Amendment) Act 2024 — Biometric data is now expressly 'sensitive personal data', triggering heightened processing conditions.
  9. Probable https://onekeybiz.com/insights/malaysia-pdpa-amendment-2024-data-protection-compliance-foreign-companies.html — Data processors (Malaysia) — Data processors are now directly liable for compliance with the Security Principle, not only data controllers, following the 2024 Amendment.
  10. Probable Resguard Solutions — Personal Data Protection (Amendment) Act 2024 — Biometric data (fingerprints, facial recognition, voice, retinal scans) as a new category of sensitive personal data, effective 1 April 2025 observed
  11. Probable RecordingLaw — Biometric data is classified as sensitive personal data under the Amendment Act. observed
  12. Probable Zenweb — Personal Data Protection (Amendment) Act 2024 (Act A1727) — Biometric data added as sensitive personal data, effective 1 April 2025 (Phase 2 commencement) observed

#

Access, correction and (newly) portability rights are well evidenced and in force; restriction/objection rights and precise response deadlines remain unconfirmed gaps.

Primary frameworkPersonal Data Protection Act 2010, Division 4 (ss.30-37), as amended by the Personal Data Protection (Amendment) Act 2024
Traffic-light rationale — AmberAccess, correction and (newly) portability rights are well evidenced and in force; restriction/objection rights and precise response deadlines remain unconfirmed gaps.

Sub-modules (5)

Access rightGreen

Access Principle (s.12) and Division 4 right of access to personal data are confirmed in force.

Claims (1):

  • Under the Access Principle (section 12) and Division 4 of the PDPA, a data subject shall be given access to his personal data held by a data user, except where compliance with the access request is refused under the Act.

Rectification and erasureAmber

A right to correct personal data exists (ss.34-37); no GDPR-style general 'right to erasure' beyond the controller's retention-destruction duty was confirmed.

Claims (2):

  • The PDPA provides a statutory right to correct personal data (sections 34-37), including circumstances in which a data user may refuse a correction request and must notify the data subject of such refusal.
  • Personal Data Protection Act 2010 — The PDPA grants a right to correct inaccurate data but does not include a general right to erasure comparable to GDPR's right to be forgotten.

Restriction and objectionRed

No explicit restriction-of-processing or objection/profiling opt-out right was confirmed via retrieved Malaysia-specific sources in this run.

Claims (1):

  • No explicit standalone right to restrict processing or to object to processing/profiling (analogous to GDPR Arts 18/21) was identified in the reviewed PDPA text or Amendment Act commentary.

Data portabilityGreen

The Amendment Act introduces a portability right, qualified by technical feasibility and format compatibility, effective from the final commencement stage.

Claims (4):

  • The Amendment Act grants data subjects a right to data portability, allowing transfer of their data between controllers, subject to the technical feasibility and compatibility of the data format.
  • Personal Data Protection (Amendment) Act 2024 — A new statutory right to data portability is introduced, phased in through 2025.
  • From 1 June 2025, data subjects may request direct transmission of their personal data to another controller.
  • Personal Data Protection Act 2010 (Act 709), as amended — Data portability right under s.43A PDPA, commenced 1 June 2025, letting a data subject request transmission of personal data to another controller of their choice

Deadlines and response windowsRed

No confirmed Malaysia-specific statutory day-count for responding to access/correction requests was retrieved in this run.

Claims (1):

  • No confirmed Malaysia-specific statutory response-window (day count) for access or correction requests under PDPA sections 31/35 was retrieved in this research pass.
Category narrative 80 words

The PDPA's Division 4 (ss.30-37) establishes a right of access and a right to correct personal data, underpinned by the Access Principle (s.12). The 2024 Amendment Act adds a new right to data portability, subject to technical feasibility and format compatibility. However, unlike the GDPR, no explicit standalone right to restriction of processing or to object (including profiling opt-out) was confirmed, and the specific statutory response-window (day count) for access/correction requests was not confirmed via primary-source retrieval in this run.

Periodic update · new data 2026-11-04

Malaysia's data subject rights framework gained a new right from 1 June 2025, when section 43A of the Personal Data Protection Act 2010, inserted by the Personal Data Protection (Amendment) Act 2024, came into effect. The new provision allows a data subject to request that their personal data be transmitted directly to another controller, a portability right that did not previously exist under the 2010 Act's original rights catalogue, which focused on access, correction, and withdrawal of consent rather than transfer between controllers. The right is qualified by technical feasibility and format compatibility, meaning a controller is not obliged to effect a transfer where doing so is not technically practicable or where the receiving system cannot accommodate the format of the data held.

The qualified nature of the right is significant for how it will function in practice. Unlike portability rights framed as near-absolute obligations, Malaysia's formulation builds in a feasibility test that gives controllers a defensible basis for declining a request, which is likely to narrow the circumstances in which the right is exercised successfully, particularly across sectors with heterogeneous or legacy data systems. The right nonetheless represents a genuine expansion of the data subject's toolkit, moving Malaysia's rights framework closer to the portability models found in more developed data protection regimes, and it is reasonable to expect increased data subject requests for transfer in sectors, such as banking and telecommunications, where switching between providers is already a live commercial dynamic.

No other data subject rights development, such as changes to access, correction, or erasure rights, was identified. The portability right's introduction should be read as a standalone, dated development rather than part of a broader rights overhaul at this time.

Outlook

The practical test of the new portability right will be how the feasibility and format-compatibility qualifiers are applied in practice, particularly in sectors with legacy infrastructure. Absent further guidance from the Department of Personal Data Protection narrowing or clarifying what counts as technically infeasible, controllers retain considerable discretion in responding to transfer requests, and the right's real-world effect may develop unevenly across sectors depending on each sector's technical readiness.

3 earlier distinct updates
Periodic update · new data 2026-10-25

The Malaysian Personal Data Protection Act grants data subjects the right to correct inaccurate data, but it does not include a general right to erasure comparable to the right to be forgotten found in frameworks such as the GDPR. This is a structural feature of the Malaysian regime rather than a gap introduced by the 2024 Amendment, and it remains the position as: a data subject who wishes to have inaccurate personal data corrected has a statutory basis to pursue that outcome, but one who wishes to have accurately recorded personal data deleted outright, absent a correction basis, does not have an equivalent general statutory right under the Malaysian framework as currently understood.

Against that structural backdrop, the 2024 Amendment is understood to have introduced a new statutory right to data portability, phased in through 2025 alongside the amendment's other headline obligations. This is a new addition to the Malaysian data subject rights catalogue rather than a modification of an existing right, and it brings the Malaysian framework a step closer to the fuller suite of rights found in more comprehensive international frameworks, even though the erasure gap identified above means the Malaysian catalogue remains narrower than those benchmarks in at least that one respect.

The pinpoint statutory provision establishing the new portability right has not been located in the sourcing available, and the practical mechanics of how a data subject exercises that right, including any format or timeframe requirements, remain unconfirmed pending retrieval of the primary gazette text or implementing guidance.

Outlook

The data subject rights catalogue should be watched for whether the Department of Personal Data Protection issues further guidance clarifying the practical exercise of the new portability right, and for whether any future amendment addresses the continuing absence of a general erasure right, which remains the most significant structural gap between the Malaysian framework and more comprehensive international benchmarks.

Periodic update · new data 2026-10-18

Malaysia's data-subject rights framework gained a materially new entitlement with the introduction of a data-portability right under section 43A of the Personal Data Protection Act, which came into force on 1 June 2025 as part of Phase 3 of the Personal Data Protection (Amendment) Act 2024. This right did not exist under the Act's original 2010 text and represents an expansion beyond the access and correction rights data subjects had previously held, allowing data subjects a statutory basis to have their personal data transferred between controllers.

Alongside this expansion, secondary commentary from the third quarter of 2026 reports that JPDP enforcement attention has, in part, been directed toward organisations failing to honour data subject access requests within a 21-day period. The precise statutory provision establishing that 21-day deadline within the Personal Data Protection Act was not independently confirmed in the sources available this cycle, so the figure should be treated as an enforcement-practice reference point rather than a confirmed statutory citation pending further verification.

Taken together, these developments describe a rights framework that is both expanding in scope, through the new portability right, and being actively policed in its existing form, through continued attention to access-request timeliness. The portability right in particular brings Malaysia's regime closer in substance to data-portability provisions found in other major data-protection frameworks, though the operative mechanics of how portability requests must be structured and fulfilled by controllers were not detailed in the sources reviewed.

Outlook

The data-portability right under section 43A is now a settled feature of Malaysian data protection law, having been in force since 1 June 2025. Attention going forward is more likely to concentrate on enforcement practice around existing rights, particularly subject access request timeliness, than on further statutory expansion of the rights catalogue itself, absent any indication of a further amendment round.

Periodic update · new data 2026-09-28

The Personal Data Protection (Amendment) Act 2024 introduces a new right of data portability for Malaysian data subjects, understood to be a significant addition to the rights available under the original 2010 Act, which did not include a portability right in its original form. This brings Malaysia's data-subject-rights framework closer to the fuller suite of rights found in more recently-modernised data-protection regimes internationally.

The precise operational scope and mechanics of the new portability right, including which categories of data it applies to and what format requirements apply to a portability request, were not independently confirmed with primary-source detail this cycle. The confidence on this development is accordingly qualified rather than fully confirmed, reflecting reliance on secondary characterisation of the Amendment Act's rights provisions rather than a directly parsed primary text describing the portability mechanism in full.

Outlook

Further JPDP guidance or a Ministerial Gazette notification specifying the operational mechanics of the data-portability right would materially increase confidence in this development. Controllers should treat the right as introduced in principle by the 2024 Amendment Act, pending clearer operational guidance on request-handling mechanics.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (9)
  1. Confirmed DataGuidance (hosted copy of official Act text) — Under the Access Principle (section 12) and Division 4 of the PDPA, a data subject shall be given access to his personal data held by a data user, except where compliance with the access request is refused under the Act. observed
  2. Confirmed DataGuidance (hosted copy of official Act text) — The PDPA provides a statutory right to correct personal data (sections 34-37), including circumstances in which a data user may refuse a correction request and must notify the data subject of such refusal. observed
  3. Confirmed IAPP — The Amendment Act grants data subjects a right to data portability, allowing transfer of their data between controllers, subject to the technical feasibility and compatibility of the data format. observed
  4. Uncertain DataGuidance (hosted copy of official Act text) — No explicit standalone right to restrict processing or to object to processing/profiling (analogous to GDPR Arts 18/21) was identified in the reviewed PDPA text or Amendment Act commentary. observed
  5. Uncertain DataGuidance — No confirmed Malaysia-specific statutory response-window (day count) for access or correction requests under PDPA sections 31/35 was retrieved in this research pass. observed
  6. Probable https://onekeybiz.com/insights/malaysia-pdpa-amendment-2024-data-protection-compliance-foreign-companies.html — Personal Data Protection (Amendment) Act 2024 — A new statutory right to data portability is introduced, phased in through 2025.
  7. Probable SimplyData — Personal Data Protection Act 2010 — The PDPA grants a right to correct inaccurate data but does not include a general right to erasure comparable to GDPR's right to be forgotten. observed
  8. Probable dataprotection.gi — From 1 June 2025, data subjects may request direct transmission of their personal data to another controller. observed
  9. Probable NHIMG — Personal Data Protection Act 2010 (Act 709), as amended — Data portability right under s.43A PDPA, commenced 1 June 2025, letting a data subject request transmission of personal data to another controller of their choice observed

#

DPO, breach-notification, security and retention duties are strongly evidenced and in force; DPIA/ROPA/joint-controller equivalents remain unconfirmed gaps versus the GDPR baseline.

Primary frameworkPersonal Data Protection Act 2010, as amended by the Personal Data Protection (Amendment) Act 2024
Traffic-light rationale — AmberDPO, breach-notification, security and retention duties are strongly evidenced and in force; DPIA/ROPA/joint-controller equivalents remain unconfirmed gaps versus the GDPR baseline.

Sub-modules (7)

Accountability & DPIARed

A general accountability principle underlies the PDPA; no DPIA-specific obligation was confirmed for Malaysia in this run.

Claims (5):

  • No PDPA/Amendment-Act provision imposing a formal Data Protection Impact Assessment obligation (analogous to GDPR Art 35) was confirmed in the reviewed Malaysia-specific materials.
  • Department of Personal Data Protection (JPDP) — On 8 May 2026, JPDP issued three additional guidelines covering Data Protection Impact Assessments, Data Protection by Design, and Automated Decision-Making and Profiling
  • JPDP issued its final DPIA, Data Protection by Design and Automated Decision-Making guideline on 8 May 2026, following a consultation.
  • JPDP issued final DPIA, Data Protection by Design, and Automated Decision-Making/Profiling guidelines on 8 May 2026, concluding its 2025 consultation.
  • JPDP DPIA / Data Protection by Design / ADM guidelines — JPDP issued final guidelines on DPIA, Data Protection by Design, and Automated Decision-Making and Profiling on 8 May 2026, concluding consultations opened in 2025.

DPO requirementsGreen

Mandatory DPO appointment for qualifying controllers/processors, with notification to the Commissioner within 21 days, effective from the final 2025 commencement stage.

Claims (8):

  • The Amendment Act introduces a mandatory Data Protection Officer appointment obligation for qualifying data controllers and processors.
  • Controllers and processors must notify the Data Protection Commissioner of DPO appointments, via a registration manual requiring notification within 21 days of appointment.
  • Data Protection Officer (Malaysia) — A DPO must be a Malaysian resident for at least 180 days per year and fluent in Bahasa Malaysia and English.
  • Controllers/processors (Malaysia) — A controller or processor must appoint a DPO from 1 June 2025 where it processes personal data of more than 20,000 subjects, or sensitive data of more than 10,000 subjects.
  • DPO Appointment Guideline — Controllers and processors must appoint at least one DPO from 1 June 2025; the guideline's numeric headcount/activity threshold was not located, only a qualitative 'large-scale data processing' description
  • The Amendment Act introduces a mandatory DPO appointment duty for organisations processing personal data at scale or handling sensitive categories.
  • PDPA (Act 709, as amended by Act A1727) — From 1 June 2025, data controllers and processors must appoint at least one DPO where they process the data of more than 20,000 data subjects generally, or sensitive personal data of more than 10,000 data subjects.
  • Department of Personal Data Protection (JPDP) — A DPO must be appointed from 2025-06-01 where processing involves 20,000+ data subjects, sensitive/financial data of 10,000+ subjects, or regular systematic monitoring; registration with the Commissioner within 21 days of appointment.

Ropa requirementsRed

No Article-30-style records-of-processing obligation was confirmed for Malaysia in the reviewed materials.

Claims (1):

  • No PDPA/Amendment-Act obligation to maintain formal records of processing activities (analogous to GDPR Art 30) was confirmed in the reviewed Malaysia-specific materials.

Joint controller arrangementsRed

No explicit joint-controller regime analogous to GDPR Art 26 was confirmed for Malaysia.

Claims (1):

  • No PDPA provision establishing a joint-controller regime analogous to GDPR Art 26 was identified in the reviewed Act text or Amendment Act commentary.

Security measuresGreen

The Amendment Act extends the security principle to data processors directly, not solely controllers.

Claims (1):

  • The amended PDPA enhances data subjects' rights to data portability and requires data processors, not just controllers, to adhere to the security principle.

Breach notificationGreen

Mandatory notification of the Commissioner within 72 hours of becoming aware of a breach, with sanctions for non-compliance.

Claims (8):

  • Data controllers must notify the Commissioner of a data breach within 72 hours after becoming aware of the breach, and must also notify affected data subjects within specified time frames.
  • Enhanced enforcement powers under the Amendment Act increase fines for PDPA violations to up to MYR1 million, extend the maximum imprisonment term to three years, and empower the Commissioner to conduct proactive compliance audits.
  • Data Breach Notification Guideline — Controllers must notify the Commissioner of a personal data breach causing or likely to cause significant harm, or of significant scale (affecting more than 1,000 data subjects), within 72 hours of occurrence
  • Data controllers (Malaysia) — Controllers must notify the Commissioner within 72 hours of becoming aware of a breach and, where significant harm is likely, notify affected individuals.
  • Personal Data Protection (Amendment) Act 2024 — Malaysia's first mandatory data-breach-notification requirement, implemented via Commissioner's Circular No. 1/2025, with maximum fine raised to RM1,000,000 for a data-protection-principle breach
  • New s.12B introduces mandatory breach-notification obligations for breaches causing or likely to cause significant harm.
  • PDPA s.12B — A controller that has reason to believe a personal-data breach has occurred causing or likely to cause 'significant harm' must notify within 72 hours.
  • Department of Personal Data Protection (JPDP) — Under PDPA s.4(4) (as amended), a data controller must notify the Commissioner within 72 hours where a breach causes or is likely to cause 'significant harm' (s.12B(2)); the clock runs from discovery. Failure to notify without written reasons for delay carries a fine of up to RM250,000 and/or up to 2 years' imprisonment.

Retention and disposalGreen

Data users must take reasonable steps to destroy or permanently delete personal data no longer required for its processing purpose.

Claims (1):

  • It is the duty of a data user to take all reasonable steps to ensure that all personal data is destroyed or permanently deleted if it is no longer required for the purpose for which it was processed.
Category narrative 59 words

The Amendment Act materially expands controller/processor duties: mandatory DPO appointment, mandatory 72-hour breach notification to the Commissioner, and extension of the security principle directly to data processors (not just controllers). A pre-existing retention/disposal duty requires destruction of data no longer needed. However, GDPR-equivalent DPIA, ROPA (Article 30 records) and joint-controller-arrangement provisions were not confirmed in the reviewed Malaysia-specific materials.

Periodic update · new data 2026-11-08

Malaysia's controller and processor obligations under the Personal Data Protection Act, as amended by Act A1727, have been reinforced on several fronts. Since 1 June 2025, data controllers and processors are understood to be required to appoint at least one data protection officer where they process the personal data of more than 20,000 data subjects generally, or sensitive personal data of more than 10,000 data subjects. This threshold-based appointment duty sets a scale-dependent compliance obligation that larger controllers and processors operating in Malaysia are understood to be subject to.

The Department of Personal Data Protection is understood to have issued final guidelines on data protection impact assessments, data protection by design, and automated decision-making and profiling on 8 May 2026, concluding consultations that had been opened in 2025. These guidelines give practical shape to accountability obligations for controllers whose processing involves automated decision-making or profiling, and their finalisation after a multi-year consultation period is understood to mark a settling of the regulator's expectations in this area, albeit one documented through secondary commentary rather than confirmed against the department's own primary guidance text.

A further obligation reported concerns breach notification. Under what is understood to be section 12B of the Act, a controller that has reason to believe a personal-data breach has occurred, where that breach causes or is likely to cause significant harm to affected individuals, must notify within 72 hours. The precise effective date of this provision has not been confirmed, so its notification clock should be read as reported rather than independently verified against a primary legal text.

Outlook

Controllers and processors in Malaysia should expect continued elaboration of accountability obligations, particularly around automated decision-making, now that the Department of Personal Data Protection has finalised its guidelines in this area. The 72-hour breach notification duty under section 12B, once its effective date is confirmed, is likely to become a focal point of compliance attention given the short notification window and the significant-harm threshold that triggers it.

5 earlier distinct updates
Periodic update · new data 2026-11-04

Controllers and processors in Malaysia face the most concentrated set of new obligations of any module. The Personal Data Protection (Amendment) Act 2024 introduced a mandatory data protection officer appointment duty for organisations that process personal data at scale or handle sensitive categories, moving Malaysia from a regime with no statutory designated-officer requirement to one with a defined, if not yet fully quantified, threshold-based duty. In parallel, a new section 12B creates a mandatory breach-notification obligation, triggered where a breach causes or is likely to cause significant harm; the Commissioner's accompanying guideline sets an expectation that notification to the Commissioner occur within 72 hours, a timeframe that mirrors notification windows familiar from more established breach-notification regimes elsewhere.

These statutory duties were joined on 8 May 2026 by the Department of Personal Data Protection's finalisation of three guidelines first put out for consultation in 2025: a data protection impact assessment guideline, a data protection by design guideline, and an automated decision-making and profiling guideline. Notably, the data protection by design guideline is stated to be voluntary rather than mandatory, which tempers the accountability expansion somewhat; organisations are encouraged toward privacy-by-design practice rather than compelled to adopt it as a matter of strict legal duty. The data protection impact assessment guideline, by contrast, operates within a framework in which certain processing, including biometric processing and processing involving artificial-intelligence-driven features, is treated as carrying elevated risk warranting assessment.

The combination of a new officer-appointment duty, a new breach-notification duty with an indicative 72-hour benchmark, and finalised accountability guidance represents a genuine escalation of the controller and processor duty framework relative to the 2010 baseline, even though some elements, such as the design guideline, remain voluntary rather than mandatory. The exact headcount or risk threshold triggering the data protection officer duty, and the precise commencement date for section 12B, have not been independently confirmed and remain open questions for organisations assessing their own obligations.

Outlook

Organisations processing personal data at scale in Malaysia should expect the data protection officer appointment duty and the breach-notification obligation to be the two developments requiring the most immediate operational attention, given their mandatory character, while treating the data protection by design guideline as good practice rather than strict compliance. Clarification of the precise thresholds and commencement dates referenced above, were it to be published, would materially sharpen organisations' ability to assess their own exposure under this expanded duty framework.

Periodic update · new data 2026-10-25

Malaysia's controller and processor duties have been substantially reshaped by the 2024 Amendment, with the mandatory 72-hour breach notification requirement and the compulsory appointment of a Data Protection Officer reported as having taken effect on 1 June 2025. Under the breach notification duty, a controller must notify the Commissioner within 72 hours of becoming aware of a breach and, where significant harm to affected individuals is likely, must also notify those individuals directly. This replaces what had previously been a framework without a clear mandatory breach notification timeline.

The Data Protection Officer appointment duty applies, per the thresholds reported, to a controller or processor that processes personal data of more than 20,000 subjects, or sensitive personal data of more than 10,000 subjects, from 1 June 2025. Beyond the appointment threshold itself, a Data Protection Officer appointed under the Malaysian framework is understood to be subject to residency and language conditions: Malaysian residency for at least 180 days per year, and fluency in both Bahasa Malaysia and English. These conditions are notable because they go beyond a simple appointment requirement and constrain who may practically serve in the role, which has implications for multinational organisations that might otherwise prefer to centralise the Data Protection Officer function outside Malaysia.

A further, more recent development is the finalisation by the Department of Personal Data Protection of its Data Protection Impact Assessment, Data Protection by Design, and Automated Decision-Making guideline on 8 May 2026, following a consultation process. As a guidance instrument rather than a binding legal provision, this guideline does not itself create new statutory obligations, but it gives practical shape to the accountability expectations that sit alongside the amendment's binding duties, in particular by setting out how organisations are expected to conduct impact assessments and apply data protection by design principles, including in the context of automated decision-making.

Taken together, the breach notification duty, the Data Protection Officer appointment threshold and its accompanying residency and language conditions, and the now-finalised DPIA and Automated Decision-Making guideline represent a substantially more developed accountability architecture than existed under the original 2010 Act, with the core binding duties already in force and the implementing guidance only now reaching completion.

Outlook

With the DPIA and Automated Decision-Making guideline only finalised on 8 May 2026, the practical application of accountability expectations under this module is likely to mature over the coming period as organisations begin to apply the guideline in practice. The residency and language conditions attached to the Data Protection Officer role are a specific point multinational organisations operating in Malaysia will need to factor into their compliance structures, and no enforcement action testing any of these duties under the new regime has yet been identified in the available sourcing.

Periodic update · new data 2026-10-18

Malaysia's controller and processor obligations under the Personal Data Protection Act were substantially reshaped by Phase 3 of the 2024 Amendment Act, which took effect on 1 June 2025 and brought mandatory Data Protection Officer appointment, mandatory breach notification, and direct statutory liability for data processors into force together. Before this change, statutory liability under the Act's Security Principle attached only to data users; Phase 3 extended that liability directly to processors, a structural change to how responsibility is allocated across the controller-processor relationship.

The mandatory DPO appointment requirement, effective from the same 1 June 2025 date, is implemented through the Commissioner's DPO Appointment Guideline Circular No. 1/2025, issued 25 February 2025. Organisations meeting the Circular's prescribed thresholds must appoint a DPO, formally notify the Commissioner of that appointment, and publish a dedicated DPO contact email address. The precise numeric thresholds that trigger the mandatory-appointment obligation were not independently retrieved from the Circular's text this cycle, so organisations should treat the appointment trigger as confirmed in principle but not yet verified in its specific quantitative detail.

Breach notification is now a concrete, time-bound obligation. A reportable personal-data breach must be notified to the Commissioner as soon as practicable and no later than 72 hours from its occurrence. Where significant harm to affected individuals is likely, those individuals must also be notified, without unnecessary delay. The consequence for failing to notify the Commissioner within the 72-hour window is a fine of up to RM250,000, imprisonment of up to two years, or both. This notification regime has applied since 1 June 2025, giving organisations operating in Malaysia over a year of operating experience under the obligation by the time of this review.

Separately, the JPDP finalised three companion pieces of guidance on 8 May 2026, concluding a public consultation that ran through 2025: final guidelines on Data Protection Impact Assessments, on Data Protection by Design, and on Automated Decision-Making and Profiling. The DPIA and Data Protection by Design guidelines give controllers and processors settled reference points for accountability-by-design obligations that had previously existed only in the bare statutory language of the amended Act.

Outlook

With DPO appointment, breach notification, and processor liability all now over a year into force, and the DPIA/Data Protection by Design guidelines finalised as of May 2026, the controller-processor duties module has moved from a phase of statutory change into a phase of operational bedding-in. The open item of greatest practical consequence is the precise numeric threshold for mandatory DPO appointment under Circular No. 1/2025, which remains to be independently confirmed against the primary Circular text.

Periodic update · new data 2026-10-12

Malaysia's core breach-notification duties under the Personal Data Protection Act 2010, as amended, remain unchanged and in force this period, providing the settled baseline against which the new draft AI framework's proposed accountability obligations should be read. Under section 12B(1), a data controller must notify the Commissioner as soon as practicable, and no later than 72 hours from occurrence, where a breach causes or is likely to cause significant harm, or is of significant scale, defined as affecting more than 1,000 data subjects; failure to comply is an offence carrying a fine of up to RM250,000 and/or imprisonment of up to two years. Under section 12B(2), where a breach causes or is likely to cause significant harm to a data subject, the controller must separately notify the affected data subject without unnecessary delay. Both provisions have been in force since the 1 June 2025 phased commencement of the amendment and are unchanged this period.

Against that settled baseline, the draft AI and Personal Data Protection Framework circulated via Consultation Paper No. 1/2026 proposes a new accountability overlay specific to AI-driven processing. Section 40.4 of the draft proposes records covering eight distinct areas, namely purpose and design, data types and sources, legal basis, assessments and approvals, significant changes, incidents, and provider oversight, which organizations would be required to make available to the Commissioner on request under section 40.5. This is confirmed as part of the live draft text under consultation until 23 October 2026, but it is not yet in force and carries no commencement date; it would, if adopted, sit alongside the existing breach-notification duties as an additional accountability and documentation obligation specific to AI systems processing personal data, rather than replacing or amending the existing section 12B notification framework.

The practical relationship between the two is additive rather than substitutive: an organization operating an AI system that also experiences a qualifying personal-data breach would, under the draft framework as proposed, face both the existing 72-hour Commissioner-notification duty under section 12B(1) and the proposed AI-specific records-availability duty under section 40.5, should the draft be finalized substantially as circulated.

Outlook

The marker to watch is whether the accountability and records-keeping provisions in section 40.4 and 40.5 of the draft AI framework survive the consultation period, closing 23 October 2026, substantially unchanged, and what transition period is attached to any finalized version. The existing breach-notification framework under section 12B is stable and not expected to change as a direct result of the AI framework consultation, since the two instruments are designed to operate as separate, additive obligations rather than a single integrated provision.

Periodic update · new data 2026-09-28

Malaysia's controller-duties landscape changed substantially through the Personal Data Protection (Amendment) Act 2024. Two new duties stand out as first-ever requirements for Malaysian data controllers: a mandatory Data Protection Officer appointment requirement for larger data handlers, implemented via Commissioner's Circular No. 2/2025, and Malaysia's first mandatory data-breach-notification requirement, implemented via Commissioner's Circular No. 1/2025. Both requirements accompany a raised maximum fine, now RM1,000,000 for breach of any single data-protection principle, more than tripling the prior RM300,000 ceiling.

Separately, Section 129 of the PDPA was amended to replace the terminology Data User with Data Controller, effective 1 April 2025, aligning Malaysian terminology more closely with international data-protection vocabulary and, more substantively, clarifying the accountability relationship the amended Act establishes. The Department of Personal Data Protection is understood to have issued three additional implementing guidelines on 8 May 2026, covering Data Protection Impact Assessments, Data Protection by Design, and Automated Decision-Making and Profiling. These guidelines' binding status and precise effective dates were not independently confirmed this cycle, so they are presented at qualified confidence pending fuller primary-source review.

Outlook

Confirmation of the binding status of the three 8 May 2026 guidelines, particularly the Automated Decision-Making and Profiling guideline, is the key open item for this module. Controllers should treat the DPO and breach-notification requirements as firmly in force, since these trace to confirmed primary and near-primary sourcing, while treating the three newer guidelines as provisional pending that confirmation.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (25)
  1. Confirmed DataGuidance — The Amendment Act introduces a mandatory Data Protection Officer appointment obligation for qualifying data controllers and processors. observed
  2. Confirmed DataGuidance — Controllers and processors must notify the Data Protection Commissioner of DPO appointments, via a registration manual requiring notification within 21 days of appointment. observed
  3. Confirmed DataGuidance — Data controllers must notify the Commissioner of a data breach within 72 hours after becoming aware of the breach, and must also notify affected data subjects within specified time frames. observed
  4. Confirmed IAPP — Enhanced enforcement powers under the Amendment Act increase fines for PDPA violations to up to MYR1 million, extend the maximum imprisonment term to three years, and empower the Commissioner to conduct proactive compliance audits. observed
  5. Confirmed DataGuidance — The amended PDPA enhances data subjects' rights to data portability and requires data processors, not just controllers, to adhere to the security principle. observed
  6. Confirmed DataGuidance (hosted copy of official Act text) — It is the duty of a data user to take all reasonable steps to ensure that all personal data is destroyed or permanently deleted if it is no longer required for the purpose for which it was processed. observed
  7. Uncertain DataGuidance — No PDPA/Amendment-Act provision imposing a formal Data Protection Impact Assessment obligation (analogous to GDPR Art 35) was confirmed in the reviewed Malaysia-specific materials. observed
  8. Uncertain DataGuidance — No PDPA/Amendment-Act obligation to maintain formal records of processing activities (analogous to GDPR Art 30) was confirmed in the reviewed Malaysia-specific materials. observed
  9. Uncertain DataGuidance (hosted copy of official Act text) — No PDPA provision establishing a joint-controller regime analogous to GDPR Art 26 was identified in the reviewed Act text or Amendment Act commentary. observed
  10. Probable dataprotection.gi — Data Protection Officer (Malaysia) — A DPO must be a Malaysian resident for at least 180 days per year and fluent in Bahasa Malaysia and English. observed
  11. Probable https://practiceguides.chambers.com/practice-guides/data-protection-privacy-2026/malaysia/trends-and-developments/O24504 — Data Breach Notification Guideline — Controllers must notify the Commissioner of a personal data breach causing or likely to cause significant harm, or of significant scale (affecting more than 1,000 data subjects), within 72 hours of occurrence
  12. Probable negaraku.md — Controllers/processors (Malaysia) — A controller or processor must appoint a DPO from 1 June 2025 where it processes personal data of more than 20,000 subjects, or sensitive data of more than 10,000 subjects. observed
  13. Probable Incorp Asia — Data controllers (Malaysia) — Controllers must notify the Commissioner within 72 hours of becoming aware of a breach and, where significant harm is likely, notify affected individuals. observed
  14. Probable https://www.recordinglaw.com/world-laws/world-data-privacy-laws/malaysia-data-privacy-laws/ — DPO Appointment Guideline — Controllers and processors must appoint at least one DPO from 1 June 2025; the guideline's numeric headcount/activity threshold was not located, only a qualitative 'large-scale data processing' description
  15. Probable SimplyData — Personal Data Protection (Amendment) Act 2024 — Malaysia's first mandatory data-breach-notification requirement, implemented via Commissioner's Circular No. 1/2025, with maximum fine raised to RM1,000,000 for a data-protection-principle breach observed
  16. Probable OneKey Biz — Department of Personal Data Protection (JPDP) — On 8 May 2026, JPDP issued three additional guidelines covering Data Protection Impact Assessments, Data Protection by Design, and Automated Decision-Making and Profiling observed
  17. Probable https://www.recordinglaw.com/world-laws/world-data-privacy-laws/malaysia-data-privacy-laws/ — JPDP issued its final DPIA, Data Protection by Design and Automated Decision-Making guideline on 8 May 2026, following a consultation.
  18. Probable negaraku.md — The Amendment Act introduces a mandatory DPO appointment duty for organisations processing personal data at scale or handling sensitive categories. observed
  19. Probable OneKey Biz — JPDP issued final DPIA, Data Protection by Design, and Automated Decision-Making/Profiling guidelines on 8 May 2026, concluding its 2025 consultation. observed
  20. Probable RecordingLaw — New s.12B introduces mandatory breach-notification obligations for breaches causing or likely to cause significant harm. observed
  21. Probable negaraku.md — PDPA (Act 709, as amended by Act A1727) — From 1 June 2025, data controllers and processors must appoint at least one DPO where they process the data of more than 20,000 data subjects generally, or sensitive personal data of more than 10,000 data subjects. observed
  22. Probable https://www.recordinglaw.com/world-laws/world-data-privacy-laws/malaysia-data-privacy-laws/ — JPDP DPIA / Data Protection by Design / ADM guidelines — JPDP issued final guidelines on DPIA, Data Protection by Design, and Automated Decision-Making and Profiling on 8 May 2026, concluding consultations opened in 2025.
  23. Probable Resguard Solutions — PDPA s.12B — A controller that has reason to believe a personal-data breach has occurred causing or likely to cause 'significant harm' must notify within 72 hours. observed
  24. Probable dataprotection.gi — Department of Personal Data Protection (JPDP) — Under PDPA s.4(4) (as amended), a data controller must notify the Commissioner within 72 hours where a breach causes or is likely to cause 'significant harm' (s.12B(2)); the clock runs from discovery. Failure to notify without written reasons for delay carries a fine of up to RM250,000 and/or up to 2 years' imprisonment. observed
  25. Probable negaraku.md — Department of Personal Data Protection (JPDP) — A DPO must be appointed from 2025-06-01 where processing involves 20,000+ data subjects, sensitive/financial data of 10,000+ subjects, or regular systematic monitoring; registration with the Commissioner within 21 days of appointment. observed

#

Transfer mechanism and TIA obligation are well evidenced and in force; the specific whitelist, adequacy-received status, and SCC/BCR/localisation architecture remain unconfirmed.

Primary frameworkPersonal Data Protection Act 2010, Part V, as amended by the Personal Data Protection (Amendment) Act 2024
Traffic-light rationale — AmberTransfer mechanism and TIA obligation are well evidenced and in force; the specific whitelist, adequacy-received status, and SCC/BCR/localisation architecture remain unconfirmed.

Sub-modules (6)

Transfer mechanismsGreen

Transfers permitted to adequate/whitelisted countries, under public-interest circumstances, or with data-subject consent.

Claims (5):

  • The PDPA permits international transfers of personal data where the receiving country has adequate data protection laws (a 'whitelisted' jurisdiction) or under circumstances of public interest; consent-based transfer remains an available mechanism.
  • PDPA s.129(2)-(3) — Cross-border transfer where the destination has a law substantially similar to the PDPA or ensures equivalent protection, or a s.129(3) exception applies; the controller itself must make this determination
  • Personal Data Protection (Amendment) Act 2024 — The 2024 Amendment abolished the prior statutory whitelist of permitted transfer destinations; cross-border transfers now require an adequacy or comparable-protection basis.
  • The Cross Border Personal Data Transfer Guideline (29 April 2025) replaced the prior statutory whitelist with a substantially-similar-laws or adequate-safeguards test.
  • JPDP cross-border transfer mechanism — Secondary commentary reports JPDP published a 2026 whitelist of approved cross-border-transfer destination jurisdictions and introduced model contractual clauses as an alternative compliance mechanism for non-whitelisted destinations.

Adequacy receivedRed

No evidence located of Malaysia having received a formal adequacy determination from another regime (e.g., EU/UK).

Claims (1):

  • No evidence was located in this research pass that Malaysia has received a formal adequacy determination from the EU, UK or another comprehensive-regime regulator.

Adequacy grantedAmber

No published list of countries Malaysia has designated as having 'adequate' protection was retrieved in this run, though PDP issued cross-border transfer guidelines in April 2025.

Claims (1):

  • PDP published cross-border data transfer guidelines in April 2025 implementing the amended transfer regime, though the specific countries treated as having 'adequate' protection were not enumerated in the retrieved sources.

SCCs and BCRsAmber

Malaysia's transfer regime relies on a whitelist-plus-consent model rather than an EU-style SCC/BCR mechanism.

Claims (1):

  • Malaysia's cross-border transfer regime is structured around whitelisted-country adequacy and consent-based mechanisms rather than a distinct SCC or BCR instrument comparable to the EU model.

Transfer impact assessmentGreen

The Amendment Act introduces a Transfer Impact Assessment requirement for cross-border transfers.

Claims (3):

  • The Amendment Act revises cross-border transfer mechanisms to require Transfer Impact Assessments (TIAs) by data controllers, including a more rigorous assessment of the receiving country's data protection framework.
  • JPDP issued a Cross-Border Personal Data Transfer Guideline on 29 April 2025 to implement the adequacy/TIA basis for transfers abroad.
  • Personal Data Protection Act 2010 (Act 709), as amended — Data controller itself (not JPDP) must determine whether a destination jurisdiction's law is substantially similar to, or equivalent to, the PDPA before any cross-border transfer, per amended s.129(2)-(3)

Data localisationRed

No general data-localisation mandate was confirmed for commercial personal data in the reviewed sources.

Claims (1):

  • No general data-localisation mandate applicable to commercial personal data was identified in the reviewed PDPA/Amendment Act materials.
Category narrative 76 words

The PDPA permits cross-border transfers to jurisdictions with adequate data protection laws ('whitelisted' countries), under circumstances of public interest, or with data-subject consent. The 2024 Amendment Act tightens this regime by requiring data controllers to undertake Transfer Impact Assessments and a more rigorous assessment of the receiving country's protections, while leaving existing mechanisms such as consent-based transfers unchanged. No formal SCC or BCR instrument, published adequacy whitelist, or data-localisation mandate was confirmed in the reviewed sources.

Periodic update · new data 2026-11-08

Secondary commentary reports that the Department of Personal Data Protection published a 2026 whitelist of approved destination jurisdictions for cross-border personal data transfers, and introduced model contractual clauses as an alternative compliance mechanism for transfers to destinations not on that whitelist. This would represent a structural addition to Malaysia's cross-border transfer regime, moving it toward a dual-track model combining an approved-destination list with a contractual fallback mechanism comparable in structure, though not necessarily in content, to mechanisms used elsewhere.

This reported development has not been confirmed against the department's own primary guidance, and it should accordingly be read as a reported rather than verified change to the transfer regime. The underlying structural question, whether Malaysia is moving from a case-by-case transfer assessment toward a more codified whitelist-and-clauses model, is significant enough to warrant continued attention even while the primary-source confirmation is pending.

Outlook

Confirmation of the whitelist and model contractual clauses against the Department of Personal Data Protection's own published guidance would be the key marker to watch. If confirmed, organisations transferring personal data out of Malaysia would gain a clearer, more codified pathway for destinations both on and off the approved list, reducing reliance on ad hoc case-by-case transfer assessments.

3 earlier distinct updates
Periodic update · new data 2026-11-04

Malaysia's cross-border data transfer regime changed in character, not merely in detail, with the Cross Border Personal Data Transfer Guideline taking effect on 29 April 2025. The guideline replaced the Personal Data Protection Act's prior statutory whitelist, a fixed list of destination jurisdictions to which transfers were permitted without further assessment, with a test asking whether the destination's laws are substantially similar to the Personal Data Protection Act or whether adequate safeguards have otherwise been demonstrated by the transferring organisation.

This is a shift from a binary, list-based mechanism to an assessment-based one, and it carries two distinct consequences. First, it removes the predictability of a fixed list, under which an organisation could determine permissibility of a transfer simply by checking a destination against an approved roster. Second, it shifts the burden of assessment onto the transferring organisation itself, which must now be prepared to demonstrate either that the destination jurisdiction's laws meet a substantially similar standard or that it has implemented adequate safeguards of its own, such as contractual mechanisms, in the absence of such a finding. This is a more flexible but also a more demanding standard, placing Malaysia's transfer framework closer in structure to adequacy-and-safeguards models found in more developed cross-border regimes, rather than the simpler whitelist approach it replaces.

No further detail on how "substantially similar" is to be assessed in practice, nor any published list of jurisdictions found to meet that standard, was identified. The guideline's operation in practice will likely depend significantly on forthcoming Department of Personal Data Protection interpretive guidance or case-by-case regulatory engagement.

Outlook

Organisations transferring personal data out of Malaysia should expect to bear a greater documentation and assessment burden under the substantially-similar-laws test than they did under the prior whitelist, particularly where transfers go to jurisdictions not previously confirmed as approved destinations. Any future Department of Personal Data Protection guidance clarifying the substantially-similar-laws standard, or any indication of which jurisdictions have been assessed as meeting it, would be a significant practical development for organisations relying on this transfer mechanism and is worth monitoring closely.

Periodic update · new data 2026-10-25

The 2024 Amendment is reported to have abolished the prior statutory whitelist of permitted cross-border transfer destinations that previously governed the export of personal data from Malaysia. In its place, outbound transfers now require an adequacy basis or a basis of comparable protection, a structurally significant change from a fixed list-based approach to a more substantive, case-by-case assessment of the destination's protective standard. This moves the Malaysian cross-border transfer regime toward the kind of adequacy-and-safeguards architecture more commonly associated with comprehensive international data protection frameworks, away from the simpler whitelist approach the original 2010 Act had relied upon.

To give that new adequacy or comparable-protection test practical content, the Department of Personal Data Protection is understood to have issued a Cross-Border Personal Data Transfer Guideline on 29 April 2025. This guideline is reported to implement, among other things, a Transfer Impact Assessment mechanism, through which an organisation assessing whether it may lawfully transfer personal data outside Malaysia would evaluate the comparable-protection basis for the destination jurisdiction. The guideline's issuance roughly two months before the amendment's other headline duties took effect on 1 June 2025 suggests the Department sought to have implementing guidance in place ahead of, or close to, the point at which the underlying statutory change took practical effect.

This is a module where the structural direction of change is clear, from a whitelist to an adequacy and comparable-protection test, but where the granular mechanics of how organisations are expected to conduct a Transfer Impact Assessment in practice depend on the content of the 29 April 2025 guideline, the detail of which has not been independently retrieved beyond its existence and stated purpose.

Outlook

The practical operation of the Transfer Impact Assessment mechanism under the 29 April 2025 guideline is the central matter to watch for this module, as organisations that previously relied on the now-abolished whitelist adjust their cross-border data flows to the new adequacy and comparable-protection test. Confirmation of how the Department of Personal Data Protection applies or enforces this new test in practice, including whether any adequacy determinations for specific destination jurisdictions have been or will be issued, remains an open question not yet resolved in the available sourcing.

Periodic update · new data 2026-09-28

Malaysia has officially launched its Guidelines for Cross-Border Personal Data Transfer (CBPDT Guidelines) as part of the phased implementation of the 2024 PDPA Amendment package. This is reported to move Malaysia's cross-border transfer approach beyond the original mechanism under the 2010 Act, which prohibited transfer of personal data outside Malaysia unless the destination country appeared on a government-approved whitelist, a narrow and administratively rigid approach compared to guideline-based mechanisms found in more recently modernised regimes.

The primary text of the CBPDT Guidelines was not directly retrieved this cycle, so the precise mechanics of the new approach, including whether it introduces standard-contractual-clause-style mechanisms, binding corporate rules, or another transfer basis alongside or instead of the whitelist, remain unconfirmed at primary-source level. This development is accordingly reported at qualified rather than fully assertive confidence.

Outlook

Retrieval and review of the CBPDT Guidelines' full primary text is the clear next step for this module. Until that review is completed, controllers relying on the new guidelines for cross-border transfers should treat the guidance as officially launched but not yet fully characterised in this brief's evidence base.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (12)
  1. Confirmed IAPP — The PDPA permits international transfers of personal data where the receiving country has adequate data protection laws (a 'whitelisted' jurisdiction) or under circumstances of public interest; consent-based transfer remains an available mechanism. observed
  2. Confirmed DataGuidance — The Amendment Act revises cross-border transfer mechanisms to require Transfer Impact Assessments (TIAs) by data controllers, including a more rigorous assessment of the receiving country's data protection framework. observed
  3. Uncertain DataGuidance — PDP published cross-border data transfer guidelines in April 2025 implementing the amended transfer regime, though the specific countries treated as having 'adequate' protection were not enumerated in the retrieved sources. observed
  4. Uncertain DataGuidance — No evidence was located in this research pass that Malaysia has received a formal adequacy determination from the EU, UK or another comprehensive-regime regulator. observed
  5. Probable IAPP — Malaysia's cross-border transfer regime is structured around whitelisted-country adequacy and consent-based mechanisms rather than a distinct SCC or BCR instrument comparable to the EU model. observed
  6. Uncertain DataGuidance — No general data-localisation mandate applicable to commercial personal data was identified in the reviewed PDPA/Amendment Act materials. observed
  7. Probable RecordingLaw — JPDP issued a Cross-Border Personal Data Transfer Guideline on 29 April 2025 to implement the adequacy/TIA basis for transfers abroad. observed
  8. Probable Lexology — PDPA s.129(2)-(3) — Cross-border transfer where the destination has a law substantially similar to the PDPA or ensures equivalent protection, or a s.129(3) exception applies; the controller itself must make this determination observed
  9. Probable https://onekeybiz.com/insights/malaysia-pdpa-amendment-2024-data-protection-compliance-foreign-companies.html — Personal Data Protection (Amendment) Act 2024 — The 2024 Amendment abolished the prior statutory whitelist of permitted transfer destinations; cross-border transfers now require an adequacy or comparable-protection basis.
  10. Probable RecordingLaw — The Cross Border Personal Data Transfer Guideline (29 April 2025) replaced the prior statutory whitelist with a substantially-similar-laws or adequate-safeguards test. observed
  11. Uncertain SimplyData — JPDP cross-border transfer mechanism — Secondary commentary reports JPDP published a 2026 whitelist of approved cross-border-transfer destination jurisdictions and introduced model contractual clauses as an alternative compliance mechanism for non-whitelisted destinations. observed
  12. Probable Lexology (law firm client alert) — Personal Data Protection Act 2010 (Act 709), as amended — Data controller itself (not JPDP) must determine whether a destination jurisdiction's law is substantially similar to, or equivalent to, the PDPA before any cross-border transfer, per amended s.129(2)-(3) observed

#

Financial-sector overlay mechanism is evidenced; other sectoral overlays are unconfirmed gaps in this research pass.

Primary frameworkPersonal Data Protection Act 2010, ss.23-29 (Codes of Practice)
Traffic-light rationale — AmberFinancial-sector overlay mechanism is evidenced; other sectoral overlays are unconfirmed gaps in this research pass.

Sub-modules (7)

Financial sector overlayAmber

PDP designates industry classes required to register and approves/registers sector Codes of Practice, including for financial-sector data users.

Claims (3):

  • PDP can designate the industry classes and business entities required to register, and approve and register Personal Data Protection Codes of Practice for various industry sectors, including the financial sector.
  • Financial Services Act 2013 s.133 — A standalone confidentiality duty on financial institutions, breach carrying a fine up to RM10,000,000, imprisonment up to 5 years, or both — materially higher than PDPA's RM1,000,000 cap
  • Financial Services Act 2013 (Act 758), s.133 — Fine of up to RM10 million, imprisonment of up to 5 years, or both

Health sector overlayRed

No Malaysia-specific health-sector data-protection overlay was confirmed in this run.

Claims (1):

  • No confirmed Malaysia-specific health-sector data-protection overlay statute or Code of Practice was located in this research pass.

Telecoms and eprivacyRed

No Malaysia-specific telecoms/ePrivacy overlay was confirmed in this run.

Claims (1):

  • No confirmed Malaysia-specific telecoms/ePrivacy overlay statute was located in this research pass.

Employment dataRed

No Malaysia-specific employment-data overlay was confirmed in this run.

Claims (1):

  • No confirmed Malaysia-specific employment-data overlay was located in this research pass.

Credit and scoringRed

No Malaysia-specific credit-scoring overlay was confirmed in this run.

Claims (1):

  • No confirmed Malaysia-specific credit-scoring overlay was located in this research pass.

educationRed

No Malaysia-specific education-sector overlay was confirmed in this run.

Claims (1):

  • No confirmed Malaysia-specific education-sector overlay was located in this research pass.

insuranceRed

No Malaysia-specific insurance-sector overlay was confirmed in this run.

Claims (1):

  • No confirmed Malaysia-specific insurance-sector overlay was located in this research pass.
Category narrative 51 words

The PDPA is the general commercial-transactions statute, and PDP is empowered to designate industry classes for registration and to approve sector-specific Codes of Practice (including for the financial sector). Beyond the financial-sector overlay, no health-, telecoms-, employment-, credit-scoring-, education- or insurance-specific overlay statute was confirmed via Malaysia-specific retrieval in this run.

Sources and claims (9)
  1. Probable DataGuidance — PDP can designate the industry classes and business entities required to register, and approve and register Personal Data Protection Codes of Practice for various industry sectors, including the financial sector. observed
  2. Uncertain DataGuidance — No confirmed Malaysia-specific health-sector data-protection overlay statute or Code of Practice was located in this research pass. observed
  3. Uncertain DataGuidance — No confirmed Malaysia-specific telecoms/ePrivacy overlay statute was located in this research pass. observed
  4. Uncertain DataGuidance — No confirmed Malaysia-specific employment-data overlay was located in this research pass. observed
  5. Uncertain DataGuidance — No confirmed Malaysia-specific credit-scoring overlay was located in this research pass. observed
  6. Uncertain DataGuidance — No confirmed Malaysia-specific education-sector overlay was located in this research pass. observed
  7. Uncertain DataGuidance — No confirmed Malaysia-specific insurance-sector overlay was located in this research pass. observed
  8. Probable Chambers Practice Guides — Financial Services Act 2013 s.133 — A standalone confidentiality duty on financial institutions, breach carrying a fine up to RM10,000,000, imprisonment up to 5 years, or both — materially higher than PDPA's RM1,000,000 cap observed
  9. Probable KembaraXtra — Financial Services Act 2013 (Act 758), s.133 — Fine of up to RM10 million, imprisonment of up to 5 years, or both observed

#

No comprehensive adtech/commercial-privacy regime was confirmed for Malaysia in this research session; this is treated as an explicit evidentiary gap rather than a substantive finding of 'no regulation'.

Traffic-light rationale — RedNo comprehensive adtech/commercial-privacy regime was confirmed for Malaysia in this research session; this is treated as an explicit evidentiary gap rather than a substantive finding of 'no regulation'.

Sub-modules (6)

Cookies and trackersRed

No Malaysia-specific cookie/tracker consent rule confirmed.

Claims (1):

  • No Malaysia-specific cookie/tracker consent regime was identified in the sources reviewed in this research pass.

Dark patternsRed

No Malaysia-specific dark-pattern prohibition confirmed.

Claims (1):

  • No Malaysia-specific dark-pattern prohibition was identified in the sources reviewed in this research pass.

Opt out signalsRed

No Malaysia-specific recognition of Global Privacy Control/DAA-style opt-out signals confirmed.

Claims (1):

  • No Malaysia-specific recognition of technical opt-out signals (e.g., Global Privacy Control, DAA) was identified in the sources reviewed in this research pass.

Clean rooms and dcrRed

No Malaysia-specific clean-room/data-collaboration-room rule confirmed.

Claims (1):

  • No Malaysia-specific clean-room or data-collaboration-room rule was identified in the sources reviewed in this research pass.

Cross context advertisingRed

No Malaysia-specific cross-context-advertising ('sale'/'share') rule confirmed.

Claims (1):

  • No Malaysia-specific cross-context-advertising rule analogous to CPRA 'sale'/'share' concepts was identified in the sources reviewed in this research pass.

Direct marketingRed

A search for a PDPA direct-marketing/Do-Not-Call provision returned Singapore PDPA results (section 43/DNC Provisions), which were deliberately excluded as out-of-scope for the MY JID; no Malaysia-specific direct-marketing suppression regime was confirmed.

Claims (1):

  • A targeted search for a Malaysian PDPA direct-marketing/consent-suppression provision (analogous to a 'section 43' Do-Not-Call regime) returned only Singapore PDPA materials; no Malaysia-specific direct-marketing suppression mechanism was confirmed in this research pass.
Category narrative 50 words

No Malaysia-specific cookie/tracker consent regime, dark-pattern prohibition, opt-out-signal (GPC/DAA) recognition, clean-room rule, cross-context-advertising rule, or direct-marketing/Do-Not-Call regime was confirmed in this research pass. A targeted search for a PDPA direct-marketing provision returned only Singapore PDPA 'Do Not Call' materials, underscoring a JID-disambiguation risk that was deliberately avoided rather than mis-attributed.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (6)
  1. Uncertain DataGuidance — No Malaysia-specific cookie/tracker consent regime was identified in the sources reviewed in this research pass. observed
  2. Uncertain DataGuidance — No Malaysia-specific dark-pattern prohibition was identified in the sources reviewed in this research pass. observed
  3. Uncertain DataGuidance — No Malaysia-specific recognition of technical opt-out signals (e.g., Global Privacy Control, DAA) was identified in the sources reviewed in this research pass. observed
  4. Uncertain DataGuidance — No Malaysia-specific clean-room or data-collaboration-room rule was identified in the sources reviewed in this research pass. observed
  5. Uncertain DataGuidance — No Malaysia-specific cross-context-advertising rule analogous to CPRA 'sale'/'share' concepts was identified in the sources reviewed in this research pass. observed
  6. Uncertain DataGuidance (hosted copy of official Act text) — A targeted search for a Malaysian PDPA direct-marketing/consent-suppression provision (analogous to a 'section 43' Do-Not-Call regime) returned only Singapore PDPA materials; no Malaysia-specific direct-marketing suppression mechanism was confirmed in this research pass. observed

#

Biometric-data governance is confirmed and in force; all other sub-modules in this space remain unconfirmed gaps.

Primary frameworkPersonal Data Protection Act 2010, as amended by the Personal Data Protection (Amendment) Act 2024 (biometric data provisions)
Traffic-light rationale — AmberBiometric-data governance is confirmed and in force; all other sub-modules in this space remain unconfirmed gaps.

Sub-modules (6)

Profiling restrictionsRed

No profiling-restriction provision analogous to GDPR Art 22 confirmed.

Claims (1):

  • No PDPA/Amendment-Act provision restricting automated profiling analogous to GDPR Article 22 was identified in the reviewed materials.

Automated decision making transparencyRed

No ADM-transparency/explanation right confirmed.

Claims (2):

  • No PDPA/Amendment-Act automated-decision-making transparency or explanation right was identified in the reviewed materials.
  • JPDP's ADM and Profiling Guideline (8 May 2026) states AI should not be the sole basis for decisions about a data subject.

AI risk assessmentsRed

No AI-specific risk-assessment obligation confirmed.

Claims (3):

  • No AI-specific risk-assessment obligation interfacing with the PDPA was identified in the reviewed materials.
  • JPDP published a draft AI and Personal Data Protection Framework for public consultation, closed 23 October 2026.
  • JPDP — Data Protection Impact Assessment, Data Protection by Design, and Automated Decision-Making and Profiling, following a 2025 public consultation

Biometric regimeGreen

Biometric data is now categorised as sensitive personal data under the Amendment Act, subject to stricter processing requirements.

Claims (2):

  • Biometric data is now recognised as sensitive personal data under the Amendment Act, subject to stricter processing requirements than general personal data.
  • PDPA (biometric data) — Act A1727 expressly recognises biometric data, including fingerprints and facial-recognition data, as a type of sensitive personal data under the PDPA.

Genetic dataRed

No Malaysia-specific genetic-data-specific regime confirmed in this run.

Claims (1):

  • No Malaysia-specific genetic-data-specific processing regime distinct from the general sensitive-personal-data category was confirmed in this research pass.

State surveillance carveoutsRed

No state-surveillance carveout provision confirmed in this run.

Claims (1):

  • No PDPA provision on national-security/state-surveillance carveouts and their limits was confirmed in this research pass.
Category narrative 36 words

The Amendment Act's classification of biometric data as sensitive personal data is the principal confirmed finding in this module. No profiling-restriction, ADM-transparency, AI-specific risk-assessment, genetic-data-specific, or state-surveillance-carveout provision was confirmed via Malaysia-specific retrieval in this run.

Periodic update · new data 2026-11-08

The clearest regulatory signal on algorithmic governance in Malaysia is the Department of Personal Data Protection's Public Consultation Paper No. 1/2026, published 5 October 2026, setting out a draft Artificial Intelligence and Personal Data Protection Framework across ten parts and forty-three sections, with seven consultation questions and a comment period that closed 23 October 2026. This is the most substantial indicator yet of how the regulator intends to approach the intersection of artificial intelligence and personal data processing, though it remains at the consultation stage with no finalised outcome yet located.

On the biometric side, Act A1727 is reported to have expressly recognised biometric data, including fingerprints and facial-recognition data, as a category of sensitive personal data under the Personal Data Protection Act. This is understood to place biometric processing under the heightened obligations that attach to sensitive personal data more generally, though the precise effective date of this recognition has not been confirmed. Read together, the AI framework consultation and the biometric sensitive-data recognition point toward an escalating regulatory interest in automated and biometric processing, an area that had previously received comparatively less explicit statutory attention than other parts of the Act.

Outlook

The trajectory in this area is escalating. The outcome of the AI and Personal Data Protection Framework consultation, once known, will be the central development to track, given its scope across ten parts and forty-three sections. In parallel, confirmation of the effective date for biometric data's recognition as sensitive personal data would clarify when the heightened compliance obligations attaching to biometric processing, such as fingerprint and facial-recognition data, formally took hold.

5 earlier distinct updates
Periodic update · new data 2026-11-04

This is the module with the most forward-looking activity. The Department of Personal Data Protection published Public Consultation Paper No. 1/2026 on 5 October 2026, circulating a draft AI and Personal Data Protection Framework running to ten parts and forty-three sections, with the consultation window closing 23 October 2026. This represents Malaysia's first dedicated attempt at a standalone artificial-intelligence governance framework situated within its data protection law, as distinct from general data protection provisions applied incidentally to artificial-intelligence systems. The scale of the draft, spanning forty-three sections across ten parts, suggests a comprehensive rather than narrow approach, though the substance of what the finalised framework will require is not yet published, and the outcome of the consultation and any transition arrangements remain open.

This consultation follows, and builds on, the Department's Automated Decision-Making and Profiling Guideline, finalised 8 May 2026 alongside the data protection impact assessment and data protection by design guidelines. That guideline already states that artificial intelligence should not be the sole basis for a decision about a data subject, establishing a human-in-the-loop expectation ahead of any broader artificial-intelligence-specific statute or framework, and separately treats artificial-intelligence-driven features as a factor that elevates the risk rating of a processing activity for data protection impact assessment purposes. Read together, the sole-basis limitation and the forthcoming framework under consultation indicate that Malaysia is building its algorithmic governance approach incrementally, first through guidance interpreting the existing Act, and now through a dedicated instrument intended to sit alongside it.

No biometric-specific surveillance instrument beyond the sensitive-category reclassification addressed under lawful processing was identified, and no facial-recognition-specific or public-surveillance-specific regulatory development was identified. The module's activity is concentrated specifically on the automated decision-making and artificial-intelligence dimension rather than on surveillance technology more broadly.

Outlook

The finalisation of the draft AI and Personal Data Protection Framework, now past its public consultation deadline, is the clearest upcoming development to track in this module. Its eventual scope, whether it introduces new registration, risk-assessment, or audit obligations beyond the existing sole-basis and data protection impact assessment requirements, and any transition period for affected organisations, are all presently unknown and will determine how significant a shift this represents relative to the incremental guidance-based approach taken to date.

Periodic update · new data 2026-10-25

Two developments bear directly on algorithmic, biometric, and surveillance governance in Malaysia, even though neither takes the form of a dedicated standalone statute addressing these subjects. The first is the 2024 Amendment's express reclassification of biometric data as sensitive personal data, which raises the conditions attached to processing fingerprint, facial recognition, or other biometric identifiers, a category of data that underpins much contemporary surveillance and authentication technology. The second is the Department of Personal Data Protection's finalisation, on 8 May 2026 following consultation, of its Data Protection Impact Assessment, Data Protection by Design, and Automated Decision-Making guideline.

The Automated Decision-Making guideline is particularly notable for this governance area because it addresses, specifically, the expectations placed on organisations that deploy automated decision-making systems, setting out how data protection by design principles and impact assessments should be applied in that context. As a guidance instrument rather than binding law, it does not itself create a dedicated statutory right for data subjects to contest automated decisions, and no such dedicated automated-decision-making rights provision has been located in the Malaysian framework, distinct from the general processing obligations the guideline elaborates upon.

Taken together, the biometric reclassification and the finalised Automated Decision-Making guideline represent material, if incremental, steps toward a more developed governance architecture for algorithmic and biometric processing in Malaysia. The biometric reclassification operates through the general sensitive-data processing conditions rather than through surveillance-specific rules, and the Automated Decision-Making guideline operates through accountability and impact-assessment expectations rather than through a dedicated data-subject right, meaning this remains an area built from general data protection mechanisms applied to specific technologies, rather than a bespoke algorithmic governance regime.

Outlook

How organisations deploying automated decision-making systems in Malaysia apply the newly finalised guideline in practice, and whether the Department of Personal Data Protection follows the guideline's finalisation with enforcement or further interpretive guidance specific to algorithmic or biometric processing, are the matters to watch. No dedicated automated-decision-making rights provision or surveillance-specific statute has been identified, so this governance area continues to be built on the general sensitive-data and accountability provisions discussed above.

Periodic update · new data 2026-10-18

The JPDP finalised its Automated Decision-Making and Profiling guideline on 8 May 2026, concluding a public consultation that ran through 2025 and issuing the guideline alongside companion Data Protection Impact Assessment and Data Protection by Design guidelines from the same process. This gives Malaysian organisations their first dedicated regulatory reference point for ADM transparency obligations, addressing a category of processing that had previously been governed only by the Personal Data Protection Act's general principles without sector- or technique-specific elaboration.

On the surveillance-governance side, Malaysia's regime retains a notably broad carve-out for government processing. Section 3(1) of the Personal Data Protection Act exempts both Federal and State Governments from the Act's application entirely. This is a wide exemption model: rather than limiting the carve-out to defined national-security or law-enforcement functions, it removes government processing generally from the Act's scope, a structural feature that distinguishes Malaysia's approach from frameworks that confine government exemptions to narrower, purpose-specific categories.

These two developments sit somewhat in tension with one another: the new ADM/Profiling guideline extends transparency expectations onto private-sector and commercial processing of personal data through automated systems, while the section 3(1) exemption means that equivalent government use of automated decision-making or profiling systems falls outside the Act's reach altogether. Readers should treat the ADM guideline's practical scope as bounded by this exemption rather than as a universal algorithmic-governance standard applicable across all processing in Malaysia.

Outlook

The finalisation of the ADM/Profiling guideline on 8 May 2026 gives this module its most significant marker to date, and organisations deploying automated decision-making or profiling systems commercially should expect this guideline to become the reference point regulators apply when assessing transparency compliance. The breadth of the section 3(1) government exemption remains a structural feature of the regime rather than a recent development, but its interaction with the new ADM guideline is likely to remain a point of definitional interest as the guideline beds in.

Periodic update · new data 2026-10-12

The most material development in Malaysia's data-protection regime this period sits squarely within this module: the Department of Personal Data Protection's publication, on 5 October 2026, of Public Consultation Paper No. 1/2026, circulating a draft AI and Personal Data Protection Framework. The draft instrument is structured across 10 parts and 43 sections and covers the AI lifecycle, with seven consultation questions posed for public comment. Comments close 23 October 2026. This is confirmed as a live, dated regulatory development; it is the clearest signal this period of Malaysia's direction on algorithmic governance specifically as it intersects with personal-data processing.

The draft framework's approach, building a standalone, structured instrument covering the AI lifecycle rather than amending the core Personal Data Protection Act 2010 to insert AI-specific provisions, supports a broader judgment that Malaysia is addressing AI-driven personal-data processing through sector-specific instrument design rather than omnibus statutory amendment. This is a Probable-confidence judgment resting on the shape of the current consultation document rather than on any stated regulatory-strategy announcement, and it should be read as an interpretation of the pattern rather than a confirmed policy statement from JPDP itself.

Separately, the Digital Minister has stated that guidelines on automated decision-making and profiling are among several guidelines expected to be issued in 2026, alongside other promised guidelines; this remains unconfirmed as issued in sources reviewed this period and carries Uncertain confidence. The relationship between this promised, standalone automated-decision-making guidance and the broader draft AI framework circulated via Consultation Paper No. 1/2026 is not clarified in sources reviewed: it is unclear whether automated-decision-making and profiling guidance will be absorbed into the finalized AI framework or issued as a separate instrument.

No biometric-specific or surveillance-specific instrument change was identified for Malaysia this period beyond the AI framework consultation itself; the existing biometric reclassification as sensitive personal data under the Personal Data Protection (Amendment) Act 2024 remains a settled, unchanged feature of the regime and is not analyzed further here.

Outlook

The clearest marker to watch is the outcome of the consultation period closing 23 October 2026: whether JPDP proceeds to finalize the AI and Personal Data Protection Framework substantially as drafted, what transition period is attached, and whether the promised automated-decision-making and profiling guidelines are folded into that finalized framework or issued separately. Given that neither the final AI framework text nor the promised automated-decision-making guidelines have been confirmed as issued, this module's trajectory remains escalating but unresolved, with the next concrete development most likely to follow the consultation close rather than occurring within the consultation window itself.

Periodic update · new data 2026-09-28

Two related developments define this module for Malaysia this cycle. First, biometric data, including fingerprints, facial recognition, voice and retinal scans, was added as a new category of sensitive personal data by the 2024 Amendment Act, effective 1 April 2025. Second, the Department of Personal Data Protection is understood to have issued an Automated Decision-Making and Profiling guideline on 8 May 2026, reportedly concluding a 2025 public consultation process on that topic.

Together, these developments suggest Malaysia is building out algorithmic and biometric governance as a connected regulatory theme rather than addressing each in isolation: biometric data's elevation to sensitive-category status creates a heightened lawful-processing threshold for the data most commonly used in automated identity-verification and profiling systems, while the ADM and Profiling guideline speaks directly to the governance of automated decision processes that may draw on such data. However, the binding status and precise effective date of the ADM and Profiling guideline were not independently confirmed this cycle, so this connection should be read as a structural observation rather than a confirmed compliance requirement.

Outlook

Confirmation of the ADM and Profiling guideline's binding status is the priority item to track. If confirmed as binding, it would represent a meaningful addition to Malaysia's governance framework for automated systems processing the newly-sensitive biometric-data category.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (10)
  1. Confirmed DataGuidance — Biometric data is now recognised as sensitive personal data under the Amendment Act, subject to stricter processing requirements than general personal data. observed
  2. Uncertain DataGuidance — No PDPA/Amendment-Act provision restricting automated profiling analogous to GDPR Article 22 was identified in the reviewed materials. observed
  3. Uncertain DataGuidance — No PDPA/Amendment-Act automated-decision-making transparency or explanation right was identified in the reviewed materials. observed
  4. Uncertain DataGuidance — No AI-specific risk-assessment obligation interfacing with the PDPA was identified in the reviewed materials. observed
  5. Uncertain DataGuidance (hosted copy of official Act text) — No Malaysia-specific genetic-data-specific processing regime distinct from the general sensitive-personal-data category was confirmed in this research pass. observed
  6. Uncertain DataGuidance (hosted copy of official Act text) — No PDPA provision on national-security/state-surveillance carveouts and their limits was confirmed in this research pass. observed
  7. Probable Department of Personal Data Protection — JPDP published a draft AI and Personal Data Protection Framework for public consultation, closed 23 October 2026. observed
  8. Probable dataprotection.gi — JPDP's ADM and Profiling Guideline (8 May 2026) states AI should not be the sole basis for decisions about a data subject. observed
  9. Probable Resguard Solutions — PDPA (biometric data) — Act A1727 expressly recognises biometric data, including fingerprints and facial-recognition data, as a type of sensitive personal data under the PDPA. observed
  10. Uncertain Wong & Partners (Baker McKenzie) — JPDP — Data Protection Impact Assessment, Data Protection by Design, and Automated Decision-Making and Profiling, following a 2025 public consultation observed

#

No comprehensive children/vulnerable-groups regime was confirmed for Malaysia in this research session; this is an explicit evidentiary gap requiring primary-source escalation, not a substantive finding of 'no protection exists'.

Traffic-light rationale — RedNo comprehensive children/vulnerable-groups regime was confirmed for Malaysia in this research session; this is an explicit evidentiary gap requiring primary-source escalation, not a substantive finding of 'no protection exists'.

Sub-modules (5)

Age verificationRed

No Malaysia-specific age-of-consent threshold for data processing was confirmed.

Claims (1):

  • No express age-of-consent threshold for personal-data processing was identified in the reviewed PDPA/Amendment Act materials.

Minor profiling bansRed

No Malaysia-specific minor-profiling ban was confirmed.

Claims (1):

  • No minor-specific profiling ban was identified in the reviewed PDPA/Amendment Act materials.

Education settingsRed

No Malaysia-specific education-settings data rule was confirmed.

Claims (1):

  • No education-settings-specific data-protection rule was identified in the reviewed PDPA/Amendment Act materials.

Dependent adultsRed

No Malaysia-specific dependent-adult (elderly/incapacitated) protection was confirmed.

Claims (1):

  • No dependent-adult (elderly/mentally-incapacitated) protection provision was identified in the reviewed PDPA/Amendment Act materials.
Category narrative 47 words

No Malaysia-specific age-of-consent, parental-consent mechanism, minor-profiling ban, education-settings rule, or dependent-adult protection was confirmed via Malaysia-specific retrieval in this research pass. Searches for PDPA children/minor provisions in the Amendment Act returned no Malaysia-specific results; adjacent PDPC Singapore children's-data guidance was excluded as out-of-scope for the MY JID.

Sources and claims (5)
  1. Uncertain DataGuidance (hosted copy of official Act text) — No express age-of-consent threshold for personal-data processing was identified in the reviewed PDPA/Amendment Act materials. observed
  2. Uncertain DataGuidance (hosted copy of official Act text) — No express parental/guardian-consent mechanism for processing a minor's personal data was identified in the reviewed PDPA/Amendment Act materials. observed
  3. Uncertain DataGuidance (hosted copy of official Act text) — No minor-specific profiling ban was identified in the reviewed PDPA/Amendment Act materials. observed
  4. Uncertain DataGuidance (hosted copy of official Act text) — No education-settings-specific data-protection rule was identified in the reviewed PDPA/Amendment Act materials. observed
  5. Uncertain DataGuidance (hosted copy of official Act text) — No dependent-adult (elderly/mentally-incapacitated) protection provision was identified in the reviewed PDPA/Amendment Act materials. observed

#

Statutory powers and penalties are well evidenced and in force; enforcement-activity, funding, collective-redress, private-right-of-action and within-180-day developments remain unconfirmed gaps.

Primary frameworkPersonal Data Protection Act 2010, as amended by the Personal Data Protection (Amendment) Act 2024
Traffic-light rationale — AmberStatutory powers and penalties are well evidenced and in force; enforcement-activity, funding, collective-redress, private-right-of-action and within-180-day developments remain unconfirmed gaps.

Sub-modules (6)

Regulator powers and penaltiesGreen

Fines up to MYR1 million and imprisonment up to three years, plus proactive audit powers, confirmed under the Amendment Act.

Claims (7):

  • The Amendment Act increases maximum fines for PDPA violations to MYR1 million, extends the maximum imprisonment term to three years, and empowers the Commissioner to conduct proactive audits of organisations.
  • The Amendment Act raised the maximum fine for breaching the data protection principles from RM300,000 to RM1,000,000.
  • Personal Data Protection (Amendment) Act 2024 — The maximum fine for breaching a data-protection principle was raised from RM300,000 to RM1,000,000, with imprisonment extended from 2 to 3 years, effective 1 April 2025.
  • PDPA s.5(2) — Maximum fine for breach of any of the seven Principles raised from RM300,000 to RM1,000,000, and maximum imprisonment from 2 to 3 years, effective 1 April 2025
  • Personal Data Protection (Amendment) Act 2024 — A separate penalty of up to RM250,000 applies specifically for breach-notification failures, distinct from the general data-protection-principle fine.
  • Personal Data Protection (Amendment) Act 2024 — Maximum fine for breach of any single PDPA principle raised to RM1,000,000, more than tripling the prior RM300,000 cap
  • PDPA ss.6-12 (data protection principles) — Act A1727 raised the maximum fine for breach of the PDPA's data protection principles to RM1,000,000 and/or up to 3 years' imprisonment (from a prior cap reported at RM300,000/2 years).

Enforcement activity indexRed

No confirmed record of Malaysia PDPC enforcement decisions/fines in the last 12 months was retrieved in this run.

Claims (4):

  • No specific record of Malaysia PDPC enforcement decisions or imposed fines within the last 12 months was located in this research pass.
  • From 2017 through 2025, JPDP required 33 data controllers to pay compounded fees for PDPA violations, with 8 cases proceeding to prosecution; the highest single compound was RM108,000.
  • JPDP's enforcement calendar reportedly intensified through 2026.
  • JPDP inspection-activity list — JPDP's published inspection-activity list records four inspection visits and two enforcement activities against unregistered data controllers in its most recent reporting cycle.

Regulator funding and capacityRed

No confirmed data on PDP's funding or headcount was retrieved in this run.

Claims (1):

  • No confirmed data on PDP's operating budget or headcount was located in this research pass.

Collective redress and class actionsRed

No confirmed collective-redress or class-action mechanism under the PDPA was retrieved in this run.

Claims (1):

  • No confirmed collective-redress or class-action mechanism available to data subjects under the PDPA was located in this research pass.

Private right of actionRed

No confirmed private right of direct court action for data subjects under the PDPA was retrieved in this run.

Claims (1):

  • No confirmed private right of action allowing data subjects direct court recourse (independent of Commissioner enforcement) under the PDPA was located in this research pass.

Recent developments 180dRed

The most recent confirmed dated development identified (PDP cross-border transfer guidance, dated October 2025) predates the 180-day window from this run's date (2026-08-05); no confirmed developments within the last 180 days were retrieved.

Claims (1):

  • The most recent confirmed dated Malaysia development in this research pass is PDP's cross-border data transfer guidance dated October 2025, which precedes the 180-day window measured from this run's date (2026-08-05); no confirmed developments from February-August 2026 were retrieved.
Category narrative 81 words

The Amendment Act materially strengthens the Commissioner's enforcement toolkit: fines for violations rise to up to MYR1 million, imprisonment terms extend to up to three years, and the Commissioner gains proactive audit powers. No confirmed enforcement-activity data (fines/decisions) for the last 12 months, regulator funding/headcount signals, collective-redress mechanism, or private right of action were retrieved in this research pass; the most recent confirmed dated development (PDP cross-border transfer guidance, October 2025) falls outside the 180-day recent-developments window as of this run.

Periodic update · new data 2026-11-08

Act A1727 is reported to have raised the maximum fine for breach of the Personal Data Protection Act's data protection principles to RM1,000,000, together with a custodial penalty of up to three years' imprisonment, from a prior cap reported at RM300,000 and two years' imprisonment. This is a substantial increase in the statutory penalty ceiling, though it rests on a single secondary source and its precise effective date has not been confirmed, so the increase should be read as reported rather than independently verified against the primary legislative text.

On enforcement activity, the Department of Personal Data Protection's own published inspection-activity list records four inspection visits and two enforcement activities directed at unregistered data controllers in its most recent reporting cycle. This gives a limited but directly sourced picture of the regulator's operational enforcement tempo, distinct from the reported statutory penalty increase, and indicates that at least part of current enforcement attention is directed at controllers that have not registered as required.

Outlook

Confirmation of the effective date for the raised RM1,000,000 maximum fine would be the key development to track, since it would clarify when the heightened penalty exposure took hold for breaches of the data protection principles. On the operational side, the recorded inspection and enforcement activity against unregistered controllers suggests registration compliance remains an active enforcement focus, and continued monitoring of the department's own inspection-activity disclosures would clarify whether this tempo is sustained or increasing.

4 earlier distinct updates
Periodic update · new data 2026-11-04

The enforcement and redress landscape in Malaysia tightened materially on the statutory side. The Personal Data Protection (Amendment) Act 2024 raised the maximum fine for breach of the data protection principles from RM300,000 to RM1,000,000, a more than threefold increase, with the unlawful processing or sale of personal data under section 16 carrying a separate maximum of RM500,000 and up to three years' imprisonment. This is a substantial recalibration of the financial consequences of non-compliance, and it is reasonable to expect it to sharpen organisational attention to compliance investment in a way that the prior, comparatively modest, penalty ceiling did not.

Separately, reporting characterised the Department of Personal Data Protection's 2026 enforcement calendar as more active than in prior years, citing an increased volume of penalty notices and breach notifications processed. This characterisation was not substantiated by specific enforcement figures or the Department's own annual report, and should accordingly be treated as an unconfirmed, lower-confidence signal pending corroboration from a primary source, rather than as an established finding on a par with the statutory penalty increase.

The combination of a sharply higher penalty ceiling and reports of increased enforcement activity, if the latter is borne out by future primary-source confirmation, would represent a genuine shift in Malaysia's enforcement posture from a regime with comparatively low financial deterrence to one with meaningfully elevated stakes for non-compliance. At this stage, the confirmed element of that shift is the statutory penalty increase itself; the broader claim of intensified enforcement activity remains to be independently verified.

Outlook

The higher penalty ceiling is now settled law and organisations should treat it as the operative standard going forward. Whether the reported intensification of enforcement activity through 2026 is confirmed by the Department of Personal Data Protection's own published figures, such as an annual report or enforcement statistics release, is the development most worth tracking next, since it would determine whether the higher penalty ceiling is being actively tested through live enforcement action or remains, for now, principally a deterrent on the statute book.

Periodic update · new data 2026-10-25

The 2024 Amendment raised the maximum fine for breaching a data protection principle from RM300,000 to RM1,000,000, more than tripling the prior ceiling, and extended the maximum term of imprisonment from two to three years, with this change reported as effective 1 April 2025. A separate, specific penalty of up to RM250,000 is understood to apply distinctly to breach-notification failures, a penalty category that did not exist as a separate head under the original 2010 Act and that sits alongside, rather than replacing, the general data-protection-principle fine.

This tenfold-plus increase in the maximum general fine represents one of the most structurally significant single changes within the 2024 Amendment, substantially raising the financial exposure a data controller or processor faces for a principle breach. However, no enforcement action applying this new, higher ceiling has been located in the available sourcing, meaning the practical severity of the new regime, as distinct from its statutory maximum, remains untested.

Context for this is provided by the Department of Personal Data Protection's enforcement activity under the prior framework: from 2017 through 2025, the Department required 33 data controllers to pay compounded fees for PDPA violations, with 8 of those cases proceeding to prosecution, and the highest single compound fee recorded at RM108,000. These figures predate the new RM1,000,000 ceiling and the extended imprisonment term, and were generated entirely under the prior, lower penalty structure, so they offer a historical baseline for enforcement activity levels rather than any indication of how the Department will exercise its substantially expanded powers going forward.

The gap between the historical compound-fee pattern, with a highest recorded figure of RM108,000, and the new RM1,000,000 statutory maximum is considerable, and the question of whether the Department's practical enforcement behaviour will scale toward that new ceiling, or continue to operate at levels closer to its historical pattern, is not yet answered by any case identified.

Outlook

The first enforcement action, if any, to apply the new RM1,000,000 maximum fine or the separate RM250,000 breach-notification penalty will be the clearest signal of how the Department of Personal Data Protection intends to use its substantially expanded powers in practice. Until such an action is identified, the historical compounding pattern described above, which predates the new ceiling, remains the only available indicator of the Department's enforcement behaviour, and it should be read with the caveat that it was generated entirely under the prior, lower penalty structure.

Periodic update · new data 2026-10-18

Malaysia's enforcement framework under the Personal Data Protection Act was structurally strengthened by Phase 2 of the 2024 Amendment Act, effective April 2025. The maximum fine for breach of any of the Act's seven data-protection principles rose from RM300,000 to RM1,000,000, more than tripling the prior ceiling, while the maximum term of imprisonment for the same breaches rose from two years to three. This escalation applies across the full range of principle-level breaches, not to any single provision, making it the most consequential enforcement-capacity change in the amendment package.

The JPDP's historical enforcement record, covering 2017 through 2025, shows 33 data controllers required to pay compounded fees for violations, with 8 of those cases proceeding to court prosecution rather than being resolved by compounding. The highest publicly reported compound within that period reached RM108,000, imposed for simultaneous breaches of the General, Disclosure and Retention Principles. This record describes an enforcement body that has historically relied predominantly on compounded settlement rather than full prosecution, though the escalated penalty ceiling introduced in April 2025 raises the potential scale of future compounded or prosecuted outcomes considerably.

More recent reporting from the third quarter of 2026 describes a compliance order and a significant financial penalty issued by the JPDP against a major retail group, over inadequate database access controls said to have exposed customer personal data. The retail group has not been named in the reporting reviewed, and the specific penalty amount was not stated. The action has nonetheless been characterised as a signal that the regulator intends to use its expanded post-amendment powers actively, rather than confining enforcement to the compounded-fee pattern that characterised the 2017-2025 period.

Outlook

The combination of a tripled maximum fine, an extended maximum prison term, and a Q3 2026 enforcement action attributed to a major retail group together suggest Malaysia's enforcement posture is shifting from the historically compounding-dominant pattern toward a more assertive use of the Commissioner's expanded powers. Further detail on the Q3 2026 action, including the identity of the retail group and the exact penalty imposed, would clarify whether this represents a genuine step-change in enforcement intensity or an isolated high-profile case.

Periodic update · new data 2026-09-28

Malaysia's enforcement architecture for data-protection-principle breaches was materially strengthened by the Personal Data Protection (Amendment) Act 2024, which raised the maximum fine for breach of any single data-protection principle to RM1,000,000, more than tripling the prior RM300,000 cap. This increase accompanies, rather than stands apart from, the Amendment Act's new mandatory breach-notification and DPO-appointment duties: a controller that fails to meet the new notification or DPO obligations now faces meaningfully higher financial exposure than under the pre-amendment penalty regime.

The raised penalty ceiling is a clear, dated, and materially significant change to Malaysia's enforcement posture, and is corroborated at Confirmed confidence given its clear sourcing. It signals a shift toward a penalty regime intended to function as a genuine deterrent rather than one calibrated to a lower cost-of-doing-business threshold, which is a pattern seen in other jurisdictions modernising decade-old data-protection statutes.

Outlook

Watch for the first enforcement actions brought under the raised RM1,000,000 ceiling, which would provide an early indication of how JPDP intends to calibrate penalties in practice under the new maximum. Any enforcement action combining a breach-notification failure with a substantive data-protection-principle breach would be a particularly significant early test of the new penalty regime.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (15)
  1. Confirmed IAPP — The Amendment Act increases maximum fines for PDPA violations to MYR1 million, extends the maximum imprisonment term to three years, and empowers the Commissioner to conduct proactive audits of organisations. observed
  2. Uncertain DataGuidance — No specific record of Malaysia PDPC enforcement decisions or imposed fines within the last 12 months was located in this research pass. observed
  3. Uncertain DataGuidance — No confirmed data on PDP's operating budget or headcount was located in this research pass. observed
  4. Uncertain DataGuidance (hosted copy of official Act text) — No confirmed collective-redress or class-action mechanism available to data subjects under the PDPA was located in this research pass. observed
  5. Uncertain DataGuidance (hosted copy of official Act text) — No confirmed private right of action allowing data subjects direct court recourse (independent of Commissioner enforcement) under the PDPA was located in this research pass. observed
  6. Uncertain DataGuidance — The most recent confirmed dated Malaysia development in this research pass is PDP's cross-border data transfer guidance dated October 2025, which precedes the 180-day window measured from this run's date (2026-08-05); no confirmed developments from February-August 2026 were retrieved. observed
  7. Probable Resguard Solutions — The Amendment Act raised the maximum fine for breaching the data protection principles from RM300,000 to RM1,000,000. observed
  8. Probable negaraku.md — Personal Data Protection (Amendment) Act 2024 — The maximum fine for breaching a data-protection principle was raised from RM300,000 to RM1,000,000, with imprisonment extended from 2 to 3 years, effective 1 April 2025. observed
  9. Probable InCorp Malaysia — PDPA s.5(2) — Maximum fine for breach of any of the seven Principles raised from RM300,000 to RM1,000,000, and maximum imprisonment from 2 to 3 years, effective 1 April 2025 observed
  10. Probable negaraku.md — Personal Data Protection (Amendment) Act 2024 — A separate penalty of up to RM250,000 applies specifically for breach-notification failures, distinct from the general data-protection-principle fine. observed
  11. Probable https://malaysia.incorp.asia/blogs/pdpa-malaysia-compliance-2026-new-rules/ — Personal Data Protection (Amendment) Act 2024 — Maximum fine for breach of any single PDPA principle raised to RM1,000,000, more than tripling the prior RM300,000 cap
  12. Probable RecordingLaw — From 2017 through 2025, JPDP required 33 data controllers to pay compounded fees for PDPA violations, with 8 cases proceeding to prosecution; the highest single compound was RM108,000. observed
  13. Uncertain SimplyData.com.my — JPDP's enforcement calendar reportedly intensified through 2026. observed
  14. Uncertain Orbixtech — PDPA ss.6-12 (data protection principles) — Act A1727 raised the maximum fine for breach of the PDPA's data protection principles to RM1,000,000 and/or up to 3 years' imprisonment (from a prior cap reported at RM300,000/2 years). observed
  15. Probable OneKey Biz — JPDP inspection-activity list — JPDP's published inspection-activity list records four inspection visits and two enforcement activities against unregistered data controllers in its most recent reporting cycle. observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 125 claim(s) (125 category placement(s)), 53 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: not upheld (1 confirmed against the cited source; 2 contradicted by the cited source; 7 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (37 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsdeadlines and response windows
Art. 14Data Subject Rightsaccess right
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrestriction and objection
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy received
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacydata localisation
Art. 49Cross-Border & Adequacytransfer impact assessment
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressprivate right of action
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties