A narrow, dated note on UAE instruments relevant to AI-agent oversight. The UAE has no comprehensive AI statute: three regimes (federal, DIFC and ADGM) apply depending on establishment, processing scope and sector, and they can overlap. Each entry names the instrument's exact status. A charter, a supervisory guidance note and binding free-zone regulation are different things, and this note keeps them apart.
These pages describe the product and cite public instruments. They are not legal advice, not a certification, and not a statement that any instrument applies to your organisation. The official source is authoritative; applicability questions belong to your advisers.
Instruments, by status
| Instrument | Status | What it addresses |
|---|---|---|
| Personal Data Protection Law, Federal Decree-Law No. 45 of 2021 | Binding law, in force 2 January 2022. Secondary reporting and commentary available as of mid-2026 indicated that the executive regulations had not yet been published, which leaves parts of the law's practical application uncertain; check the publication status against current official sources before relying on it. A federal Artificial Intelligence and Data Authority was approved on 14 June 2026 to consolidate AI and data functions. | Federal personal-data processing, including automated processing, subject to statutory exclusions: certain government, health and banking data are carved out, and the financial free zones have their own regimes. Using AAES does not discharge the controller's duties; other parties' obligations depend on their roles. |
| Data Protection Law No. 5 of 2020 and Regulation 10 · DIFC | Binding in the DIFC. Regulation 10 on autonomous and semi-autonomous systems was enacted 1 September 2023 and moved to full enforcement on 1 January 2026. Consultation Paper No. 3 of 2026 (closed 18 July 2026) proposes amendments, including a Regulation 11 on certification schemes (a proposal, not final). | AI-specific binding rules for autonomous and semi-autonomous systems processing personal data: impact and risk assessment, transparency notices, human-intervention design. Regulation 10.3.3 prohibits using, operating, providing, offering or otherwise making a system available for commercial use to engage in the High Risk Processing Activities specified in sub-clause (a) of the definition in Schedule 1, Article 3 of the Law, unless the Commissioner has established applicable audit and certification requirements, the system meets those requirements, it processes personal data solely for human-defined or human-approved purposes, and the deployer or operator has appointed an Autonomous Systems Officer (cumulative conditions, not alternatives). The deployer carries controller-style duties. |
| Data Protection Regulations 2021 and FSRA cyber-risk requirements · ADGM | Binding in the ADGM. The FSRA's Cyber Risk Management framework (GEN 3.5, announced 29 July 2025) became mandatory for Authorised Persons and Recognised Bodies on 31 January 2026, including 24-hour material-incident notification to the FSRA. | Data protection and cyber resilience inside Abu Dhabi's financial free zone; AI systems sit inside both frameworks rather than a dedicated AI rule. |
| Guidance note on responsible AI and machine learning · Central Bank of the UAE (February 2026) | Supervisory guidance for licensed financial institutions: formally guidance, treated as an expectation in supervision. | Board accountability, model inventories with risk ratings, annual bias testing, consumer opt-out for high-impact decisions, and the expectation that human-out-of-the-loop operation is reserved for low-risk processes. The institution remains accountable for third-party AI. |
| UAE AI Charter (2024) | Policy instrument, non-binding. | Principles that shape procurement and vendor diligence rather than enforceable duties. |
What AAES records may contribute
| Expectation | AAES contribution | Capability status |
|---|---|---|
| Named accountability (CBUAE board accountability; DIFC deployer duties) | Every registered agent has a named accountable manager, a configured association rather than a statutory appointment; approvals are attributable to a named person; agent identities cannot act as approvers through the supported AAES approval path. | Implemented. |
| Human intervention in high-impact processing (DIFC Regulation 10; CBUAE human-in-the-loop expectation) | Actions the operator registers as irreversible (a registration classification, not an independent assessment of effects) require approval by an authorized person, bound to one intent and the exact payload, with expiry. An approval record does not by itself show the approver had adequate information, time or practical power to intervene. | Implemented. |
| Records that may assist a regulator's review (DIFC audit expectations; CBUAE inventory and testing) | Sealed, hash-chained decision records with offline integrity verification by the client's own reviewer. | Implemented. An independently controlled witness can be configured separately; that is not an external assessment, and the default deployment has none. |
AAES decision records may support review of access and approval controls. They do not establish lawful processing, model fairness, suitability, or compliance with any instrument as a whole.
Within the configured trust model, integrity verification checks the exported records; it does not establish that every action was recorded, that an external action succeeded, or that recorded assertions are true. Approval records do not by themselves establish meaningful human oversight. Enforcement depends on control of the credential path, and actions bypassing AAES are not recorded.
Residual responsibility and explicit gaps
- The client remains the regulated entity. Which of the three regimes (federal, DIFC or ADGM) applies to you is a threshold legal question for your advisers, not this page's.
- Work outside AAES is invisible to AAES. Records cover actions routed through AAES; they say nothing about actions on bypass paths.
- No independent certification or assessment of AAES exists. No SOC 2 report, no penetration test. AAES's records do not establish satisfaction of any applicable DIFC certification requirement.
- Status changes. The DIFC amendments proposed in 2026 may be finalised, and the federal authority may begin operating, after this note's review date. Re-check the primary source before relying on the status shown here.
Bring the instruments your risk team cites to a scoped evaluation.
Related pages:
This note: https://aaes.ai/library/jurisdictions/united-arab-emirates.html
Hong Kong note: https://aaes.ai/library/jurisdictions/hong-kong.html
Singapore note: https://aaes.ai/library/jurisdictions/singapore.html
Trust model: https://aaes.ai/library/trust-model.html
Scope an evaluation: https://aaes.ai/contact.html?ref=library-evaluation