Regulatory reference tables

MENA Jurisdictional Comparison Matrix

The matrix maps the eight core MENA jurisdictions (UAE, Saudi Arabia, Qatar, Bahrain, Kuwait, Oman, Egypt, Jordan) across twenty-five compliance dimensions. The dimensions cover the data protection foundation, the AI-specific provisions, the supervisory architecture, and the operational obligations the institutions operating in each jurisdiction must satisfy.

A.1.1 Data Protection Foundation (Dimensions 1 through 10)

A.1.2 AI-Specific Provisions (Dimensions 11 through 17)

A.1.3 Supervisory Architecture and Operational Obligations (Dimensions 18 through 25)

The matrix is the navigation aid. The chapters specify what the matrix indexes. The institution operating across multiple jurisdictions calibrates discipline to the strictest applicable obligation per dimension, then operationalizes the calibrated discipline as the regional baseline the MESA framework Chapter 4 specifies sustains.

Three operational notes anchor the matrix interpretation. Each of the three corrects a convergence assumption the regional comparison literature repeats and the operating institution inherits.

The first note is the consent standard. The eight frameworks do not converge on a single formulation. Three of them (UAE, Saudi Arabia, Qatar) specify explicit, specific, and informed consent. The remaining five specify explicit consent without the further qualifiers. A single consent-management discipline still satisfies all eight perimeters, though for a different reason than convergence. Building to the strictest formulation subsumes the looser ones by construction. The institution operationalizes one consent posture because the strictest formulation contains the others, not because eight legislatures agreed.

The second note is the breach-notification timeline, and it is the note the institution most often gets wrong. The 72-hour figure is genuinely shared as the regulator-facing leg across the region. It is not the binding constraint. Jordan requires notification to affected data subjects within 24 hours under Article 20(A)(1), with 72 hours applying only to the regulator leg. Egypt requires immediate notification where national security is engaged, and three working days to the data subject after the report to the Centre. Oman carries two separate 72-hour legs, one to the Competent Administration and one to the data subject where serious harm or high risk is present. An institution that built a uniform 72-hour posture on the strength of the shared regulator deadline breaches Jordanian law on every incident it handles. The incident-response discipline the Chapter 13 Data Governance Stack specifies is calibrated to 24 hours on the data-subject leg and to the regulator cadence separately. One posture remains achievable. It is a 24-hour posture, not a 72-hour posture.

The third note is the cross-border architecture divergence. Saudi Arabia is not a localization outlier, and the belief that it is has funded in-Kingdom infrastructure the law does not require. The Saudi PDPL and its Implementing Regulations impose no storage-residency obligation. Article 29 is the article that permits transfer under conditions, and the 2023 amendment moved the Kingdom further toward conditions plus safeguards rather than toward residency. The binding architectural constraint in the region is Egyptian. Article 14 of Law 151 of 2020 treats storing personal data abroad, including hosting in a cloud region outside Egypt, as a cross-border transfer. It is permitted only to a destination meeting the equivalent-protection threshold and only under an explicit PDPC license, which is a discrete paid regulatory filing. The Chapter 9 Cross-Border AI Architecture Patterns operationalize the divergence through the Sovereign Silos, Federated, and Regional Hub patterns. The institution selects the pattern against the Egyptian licensing constraint and the Saudi transfer conditions, not against a Saudi residency mandate that the statute does not contain.

The matrix is not the discipline. The matrix is the dimensional map the discipline operates against. The institution that mistakes the matrix for the discipline produces compliance documentation without the operational substrate the supervisor inspects through the documentation. The institution that operates the discipline against the matrix produces the operational substrate the documentation traces and the supervisor recognizes.

Global Regulatory Regimes Comparison

The global regimes are the extraterritorial reality MENA institutions operating internationally inhabit. The matrix maps five regimes across ten dimensions.

The global regimes are not optional for MENA institutions serving international markets. The EU AI Act reaches MENA institutions whose AI system output is used in the EU. PIPL reaches MENA institutions processing Chinese personal information. American sectoral discipline reaches MENA institutions with US-listed exposure. The extraterritorial reality is the current operational condition the institutions operating across the perimeters inhabit.

Where most observers see five distinct global regimes, I see one convergence vocabulary the international standards layer (ISO/IEC 42001, OECD, UNESCO) increasingly codifies and the regional regimes increasingly translate. The institution that built MESA discipline against the convergence vocabulary operates across the regimes through the structural commonality. The institution that built compliance against the regimes one at a time operates against the divergence at each perimeter and accumulates the operational overhead the convergence would have absorbed.

The convergence vocabulary carries one hazard, and it is worth naming here rather than discovering it in a filing. The vocabulary makes the regimes legible to each other, which tempts the institution to complete an unfamiliar regime by importing a familiar construct. The penalty row above records what that costs. European and British law resolve the fixed-sum-versus-percentage question with an explicit tie-breaker; Chinese law does not, and Article 66 of the PIPL leaves the selection to the enforcing authority. American model risk guidance was modernized in 2026 and then placed generative and agentic systems outside its own scope, so the institution that treats SR 26-2 as its AI instrument has documented the wrong perimeter. Convergence is a translation aid. It is not a completion rule.

Penalty Provisions by Jurisdiction

Penalty is not punishment. It is the cost calibration the supervisory framework applies to the gap between the discipline the institution declared and the discipline the operational substrate produced.

The provisions below support the materiality analysis the institutions operating across the regulatory landscape conduct. They are inputs to the risk-tolerance calibration the Chapter 14 Vendor Risk Lifecycle specifies, the financial-impact dimension the Chapter 11 Governance Office Blueprint incorporates, and the cost-of-non-compliance analysis the Chapter 12 MRM Stack supports.

A.3.1 What the Statutes Actually Publish

The institution that arrives at the penalty question expecting a graduated schedule per violation category will not find one. Across the eight MENA jurisdictions, one publishes a single administrative maximum, one publishes a maximum that reaches only one article, one publishes a low fixed band doubled for corporate offenders, one publishes criminal minimum-to-maximum bands per offence, one publishes a daily accrual capped as a percentage of revenue, one publishes nothing at all, and two could not be confirmed against a primary source. The graduated per-violation band tables common in vendor comparison material are a construction laid over the statutes. They are not in the statutes.

The distinction is not pedantic, because the three structures behave differently under modelling. A maximum is a ceiling the supervisor may reach at its discretion, and the realistic settlement sits far below it. A criminal minimum-to-maximum band is a sentencing range a court applies per offence, and offences aggregate rather than cap. A daily accrual is an exposure that compounds while the breach persists, which makes remediation speed the variable rather than violation gravity. An institution that treats all three as a lookup value produces a materiality number that does not survive its first conversation with counsel.

Every figure below is stated with the instrument and, where the primary text supplies one, the article. Where no figure is published, or where the published figure could not be confirmed against the instrument itself, the table says so rather than supplying a proxy.

A.3.2 United Arab Emirates

Two operational notes follow. The first is that the absence of a published federal figure is not the absence of exposure. The DIFC and ADGM regimes enforce now, and the federal supervisory posture consolidates through direction and order rather than through fines. The second is that a compliance grace period, reported at six to twelve months, begins only once the federal Executive Regulations are gazetted. The institution that read "no published fine" as "no deadline" read the wrong sentence.

A.3.3 Saudi Arabia

The Saudi PDPL publishes two figures and no schedule. There is no graduated band per violation category, no separate localization penalty, and no statutory minimum. The SDAIA committee rules that govern how violations are assessed carry no monetary amounts of their own. An institution modelling Saudi exposure models against SAR 5,000,000 administrative, SAR 3,000,000 criminal, and the doubling provision. Anything more granular than that is inference wearing the clothes of law.

A.3.4 Qatar and Kuwait

Neither jurisdiction's penalty provisions could be confirmed against a primary source for this edition. The Qatari PDPPL and the Kuwaiti Data Privacy Protection Regulation both carry enforcement provisions. The figures circulating in secondary comparison material could not be traced to the instruments themselves, and the pattern established across the six jurisdictions that were reachable is that such figures are usually wrong by an order of magnitude or more.

This edition therefore prints no Qatari or Kuwaiti penalty figure. Counsel in each jurisdiction should be instructed to supply the current amounts from the gazetted text before any materiality analysis relies on them. A blank cell that says so is worth more to the risk committee than a plausible number with no provenance.

A.3.5 Bahrain

Bahrain carries the smallest published exposure in the region by roughly two orders of magnitude. The governance implication is the opposite of permission. Where the fine is immaterial, the fine is not the constraint, and the institution operating in Bahrain calibrates to the license and the supervisory relationship rather than to the penalty column.

A.3.6 Oman

The Omani figure most often quoted in comparison material is OMR 500,000, and it is real. Quoting it as the maximum fine without the Article 29 qualifier overstates a corporate institution's realistic exposure by roughly five times, because Article 30 states a ceiling of OMR 100,000 for a legal person. Counsel should be asked to confirm how Articles 29 and 30 interact for a corporate defendant before either figure enters a risk model. The Omani transition period ended February 5, 2026, and the PDPL is now fully enforceable, so the question is no longer prospective.

A.3.7 Egypt

Egypt's penalty architecture is criminal rather than administrative, and this is the single most misread fact in the regional comparison literature. Fines are imposed by the Economic Courts as minimum-to-maximum bands per offence. Offences aggregate. There is no general administrative maximum, and the frequently quoted EGP 5,000,000 is offence-specific rather than a ceiling on Egyptian exposure.

Two corrections to the common presentation follow from the table. The first is that imprisonment terms in the Egyptian PDPL are stated as minima of three months, not as maxima of five and three years. The direction of the error matters, because a maximum invites the institution to treat custody as a remote tail risk while a minimum removes the court's discretion to go lower. The second is that EGP 10,000,000 is not a sensitive-data category. It is the Article 48 recidivism doubling, which means it becomes reachable only after a first conviction.

The article-by-article mapping of offences should be confirmed with Egyptian counsel against the gazetted Arabic text before it is relied on. The Executive Regulations, issued by Minister of Communications Decree 816 of 2025, came into force November 2, 2025 and opened a one-year compliance transition running to approximately November 1, 2026. That date is the most actionable Egyptian fact a compliance officer holds, because the Centre being operational is not the same thing as the Centre enforcing.

A.3.8 Jordan

Jordan is the structural outlier rather than the magnitude outlier. The daily accrual makes Jordanian exposure a function of remediation speed rather than of violation gravity. An institution that takes ninety days to close a finding has accrued JOD 45,000 before any criminal band applies, and the finding does not have to be serious for the meter to run. The revenue cap becomes the binding constraint only for institutions large enough that 3 percent of prior-year revenue arrives before remediation completes. Article 23 gave a further year to conform, so full compliance has been required since March 17, 2025.

A.3.9 Global Regime Penalty Comparison

The PIPL divergence deserves its own note, because the comparison habit runs in the direction that hides it. European and British law resolve the fixed-sum-versus-percentage question with an explicit tie-breaker. Chinese law does not. Article 66 sets both figures as ceilings and leaves the selection to the enforcing authority. An institution that modelled Chinese exposure by importing the European tie-breaker modelled a rule that does not exist in the instrument it was modelling, and modelled it in the direction that overstates. This is the convergence vocabulary doing what convergence vocabularies do when nobody checks the source text.

The penalty provisions are inputs, not endpoints. The institution that operates against the published figure rather than against the discipline the figure indexes will discover that the figure moved while the discipline did not, or worse, that the figure was never in the statute at all. The discipline operating against the substrate survives both the revisions the regulatory evolution will continue to produce and the errors the secondary literature will continue to propagate.

AI Use Case to Regulatory Regime Cross-Reference Matrix

The use case is the operational unit the discipline applies to. The matrix supports the use-case approval discipline Chapter 12 specifies through the MRM Stack and the Tier 1, Tier 2, Tier 3 classification the Governance Office Blueprint Chapter 11 operationalizes.

One naming caution applies before the matrix is read. The Tier 1, Tier 2 and Tier 3 labels in the final column are this book's own classification, defined by the Chapter 12 risk matrix as Chapter 16 extends it for generative systems. They are not a regulator's vocabulary, and in particular they are not SDAIA's. SDAIA classifies AI systems across four named levels: little or no risk, limited risk, high risk, and unacceptable risk. Systems at unacceptable risk are prohibited; systems at high risk carry pre-deployment and post-deployment conformity assessment; systems at limited risk are subject to the AI Ethics Principles; systems at little or no risk are encouraged rather than required to comply. An institution that walks into a SDAIA engagement speaking of Tier 1 systems is speaking a vocabulary the supervisor does not use.

The matrix is the operational vocabulary for the use-case approval committee. The institution operates against the matrix to identify the applicable regulatory regimes per use case, then operationalizes the discipline the regimes require through the MRM Stack the Chapter 12 specifies and the Governance Office Blueprint the Chapter 11 operationalizes.

Four use-case classifications deserve specific operational note. The first classification is the Tier 1 high-stakes consumer-facing AI (credit scoring, insurance underwriting, healthcare diagnostic, HR resume screening, biometric identification, educational scoring). These use cases attract the strictest convergent obligations across MENA, EU, and US regimes. The discipline calibrated to EU AI Act Annex III high-risk obligations the Chapter 2 specifies satisfies most other regimes by transitivity. The second classification is the algorithmic trading and securities-adjacent AI. These use cases attract sectoral securities-regulator obligations across SCA, CMA Saudi Arabia, QFMA, FRA Egypt, and SEC. Kuwait's Capital Markets Authority operates under the Executive Bylaws of Law 7 of 2010, none of whose modules is an algorithmic-trading instrument, so Kuwaiti exposure on this classification runs through general market-conduct supervision rather than a dedicated rule. The discipline calibrated to SR 26-2 model risk management satisfies most of these regimes structurally, with one exclusion the institution must hold in view: footnote 3 of SR 26-2 places generative and agentic AI outside its scope, so a trading system built on a generative or agentic component is not covered by the discipline that covers the conventional model beside it. The third classification is the Sharia-AI overlay for Islamic finance products. These use cases attract the AAOIFI and IFSB standards in addition to the conventional regimes. The Chapter 7 Sharia AI Governance specifies the discipline. The fourth classification is the generative AI for content production and the customer-service chatbot use cases. These use cases attract transparency obligations under EU AI Act limited-risk provisions, SDAIA Generative AI Guidelines, and China Generative AI Measures (if China-facing). The discipline calibrated to disclosure and content-moderation obligations the Chapter 16 Generative AI Governance specifies satisfies the convergent transparency requirement, and it is the discipline that covers what SR 26-2 declines to reach.

The matrix is the input. The use-case approval committee is the operational discipline. The Tier classification (Tier 1, Tier 2, Tier 3) the Governance Office Blueprint Chapter 11 operationalizes is the structural output the matrix produces. The institution that operates the matrix without the committee produces classification without discipline. The institution that operates the committee without the matrix produces discipline without dimensional grounding. Both are required, integrated through the operational cadence the Chapter 11 specifies.

Regulatory Authority Catalogue

The supervisory dialogue is conducted with named authorities. The catalogue specifies the authorities by jurisdiction with the supervisory style the institution operationalizes engagement against.

The authorities catalogue is the supervisory-engagement map. The institution that has cultivated relationships with the relevant authorities operates within the supervisory dialogue. The institution that has not operates against the supervisory inquiry when it arrives without the relationship the dialogue would have produced.

Regulatory Timeline (2018 through 2028)

The regulatory landscape is not static. The timeline indexes the key dates and milestones across the 2018 through 2028 horizon the institutions operating across the regulatory evolution must plan against.

The timeline is the strategic-planning input. The institution that has built discipline against the timeline operates ahead of the regulatory evolution. The institution that has not operates against each new milestone as a surprise the operational substrate is not prepared for.

Operational Notes on Table Maintenance

The tables are not finished documents. They are the operational substrate the institutional discipline must maintain through the supervisory cycles.

The discipline operates through four practices.

The first practice is quarterly review by the Governance Office Chapter 11 specifies. The review examines each table for regulatory changes, supervisory guidance, enforcement developments, and milestone advancement. The review output is a table-revision log the discipline operates against.

The second practice is supervisory-engagement integration. The relationships the Section A.5 catalogue indexes are the source of regulatory intelligence the tables capture. The supervisory dialogue is not an isolated function. It is the input the table-maintenance discipline depends on.

The third practice is cross-jurisdictional reconciliation. The institutions operating across multiple jurisdictions reconcile the table entries against the operational discipline applied per jurisdiction. The reconciliation surfaces the discipline asymmetries the multi-jurisdictional architecture must accommodate.

The fourth practice is the operational vocabulary calibration. The terms the tables use must match the terms the supervisory dialogue uses. The calibration is conducted by the operational compliance function and validated through the supervisory engagement.

Where most observers see reference tables, I see the operational vocabulary the institutional discipline depends on for the supervisory dialogue.

Stillness is not inactivity. It is the calibration that exposes the gap between the regulatory landscape the institution last documented and the regulatory landscape the supervisory dialogue currently inhabits. The institutions that have built table-maintenance discipline operate within the regulatory reality the supervisor inhabits. The institutions that have not operate against the regulatory landscape the deck described before the supervisory landscape moved.