Which law covers a DIFC subsidiary?
The DIFC law, for an entity incorporated in the DIFC (Article 6). The federal law steps aside for free zones with their own data protection law (Article 2(2)(g)).
UAE PDPL. DIFC. ADGM.
In a UAE group, the first inventory question is which regime each entity sits in: federal, DIFC or ADGM. The same value can change label between them.
By Dipal Panchal, co-founder and CEO · Last reviewed: November 8, 2026
Federal Decree-Law No. 45 of 2021 has been in force since January 2, 2022 (Article 31). It covers data subjects who live or work in the UAE, controllers and processors in the UAE for any data subject, and those abroad for data subjects in the UAE (Article 2(1)).
Article 2(2) leaves out government data, governmental entities that control or process personal data, and data held by security and judicial authorities. It also leaves out health and banking data that have their own protection law, and free zones with their own data protection law, such as the DIFC and ADGM.
The UAE Data Office, set up by Decree-Law No. 44 of 2021, supervises the federal law; a new federal authority announced on June 14, 2026 has no decree or start date yet. Its Executive Regulations were due within six months of issue (Article 28); none appear on official UAE sites today. This page is general information, not legal advice.
How a reviewer labels values for a group with an onshore bank, a DIFC entity and a clinic. Types are the reviewer’s labels, not IRIS detections, and a value can change label with the regime.
| Value | Detected type | Label | Reason | Kept or rejected |
|---|---|---|---|---|
| 784-1990-… (15 digits) in kyc.emirates_id | Emirates ID number | Personal data in all three regimes | Starts with 784, the UAE code; shortened placeholder | Kept |
| Spouse and two children in hr.family | Family details | Sensitive under federal Article 1 only | A category the federal list names and the DIFC and ADGM lists don’t | Kept |
| Union dues in payroll (DIFC entity) | Trade union membership | Special category under the DIFC law | Listed by DIFC; neither the federal law nor ADGM lists it | Kept |
| Criminal record check in hr.vetting | Criminal record | Sensitive in all three regimes | Each list names criminal records or convictions | Kept |
| Type 2 diabetes in clinic.notes (onshore) | Health data | Outside the PDPL where health law governs it | Article 2(2)(e); Federal Law No. 2 of 2019 covers health ICT | Kept |
| DXB-04 in branches.code | Branch code | Not personal data | A site code that identifies no person | Rejected |
Each cell is the regime’s own rule, pinpointed where we read the text. Where the federal law waits on Executive Regulations, the cell says so.
| Question | Federal PDPL | DIFC law | ADGM regulations |
|---|---|---|---|
| Who it covers | Data subjects in the UAE; UAE-based controllers for any data subject; foreign ones for UAE data subjects (Art. 2(1)) | Entities incorporated in the DIFC, wherever they process, and processing in the DIFC under stable arrangements (Art. 6) | Entities established in ADGM, for processing in the context of their activities |
| Regulator | UAE Data Office (Decree-Law No. 44 of 2021) | Commissioner of Data Protection (Article 43) | Office of Data Protection, led by its Commissioner |
| Sensitive data | Family, racial origin, political or philosophical views, religion, criminal record, biometric and health data (Art. 1) | Special categories, including communal origin, criminal record and trade union membership (Schedule 1) | Special categories, including criminal convictions; trade union membership isn’t listed (section 7) |
| Breach notice to the regulator | On becoming aware; the period is left to the Executive Regulations (Article 9(1)) | As soon as practicable, for a breach compromising confidentiality, security or privacy (Art. 41) | Without undue delay and, where feasible, within 72 hours of discovery (guidance, Part 5) |
| Requests from people | Information, portability, correction, erasure, restriction and objection (Articles 13–18) | One month from the request; two more for complex or numerous requests, with notice and reasons (Art. 33) | Two months from receipt; one more where necessary (section 10) |
| Record of processing | A record naming data categories and who may access them (Article 7(4)); processors keep one (Article 8(7)) | A written record of processing activities (Article 15) | A record of processing activities (section 28) |
| Data protection officer | Where processing is high risk, or covers large volumes of sensitive data (Article 10) | For DIFC bodies and systematic high-risk processing (Article 16) | Public authorities; core large-scale tracking of people, or special-category processing (section 35) |
| Maximum fine | None set yet: Article 26 leaves penalties to a Cabinet decision, not found today | Schedule 2 lists up to USD 100,000 per contravention; Article 62(3) allows general fines beyond that | Up to USD 28 million under section 55(1) |
| Bank rules on top | CBUAE Consumer Protection Standards: logs of staff access to consumer data, and immediate notice of significant breaches | DFSA rules for authorized firms; not covered here | FSRA rules for financial firms; not covered here |
The DIFC law, for an entity incorporated in the DIFC (Article 6). The federal law steps aside for free zones with their own data protection law (Article 2(2)(g)).
Not where banking and credit data has its own protection law (Article 2(2)(f)); CBUAE rules then drive the evidence. Other personal data the bank holds stays in scope.
The PDPL says on becoming aware but leaves the period to Executive Regulations not yet found. A bank still tells the Central Bank at once of significant breaches.
No. The work has four parts: people and skills, policy and process, technology, and assurance. The regime map in step 1 is policy work; IRIS is one component inside technology.
Checked on u.ae, difc.com and centralbank.ae on November 7 and 8, 2026. Next review by February 6, 2027, or as soon as the Executive Regulations appear.
| Item | Status | Instrument |
|---|---|---|
| Federal PDPL | Issued September 20, 2021; in force January 2, 2022 | Decree-Law No. 45 of 2021, Article 31 |
| Executive Regulations | Due within six months of issue; none found on official UAE sources today | Decree-Law No. 45 of 2021, Article 28 |
| Compliance period | Six months from the Executive Regulations, extendable once by the Cabinet | Article 29 |
| Federal penalties | No Cabinet decision setting them found today | Article 26 |
| Regulator | The UAE Data Office, still listed as active; a new authority announced June 14, 2026 has no decree or start date yet | Decree-Law No. 44 of 2021; Dubai Media Office, June 14, 2026 |
| DIFC | In force since July 1, 2020; amended by DIFC Laws Amendment Law No. 1 of 2025, in effect July 15, 2025 | DIFC Law No. 5 of 2020, consolidated July 2025 |
| ADGM | Data Protection Regulations 2021, in force for every entity since February 14, 2022 | ADGM Data Protection Regulations 2021 |
| Review | Editorial review by Sylox; not reviewed by a lawyer | Last reviewed November 8, 2026 |
IRIS doesn’t certify compliance. IRIS maps its evidence to UAE PDPL controls through its unified compliance framework. A scored readiness view for UAE PDPL isn’t in v1; ask us if you need one.
Federal Article 7(4): the data categories in each system: IRIS produces part of this, for the sources you connect and the data types IRIS detects.
Federal Article 7(4): who may access each dataset: IRIS produces part of this, where the source exposes permission data.
Federal Article 20(1)(a): how stored values are protected: IRIS produces part of this, checks sampled values for encryption, masking or hashing, once activated on your install.
DIFC Art. 15(1)(d) and Reg. 2.1.4(d), ADGM section 28: data categories and where they sit: IRIS produces part of this, for the sources you connect.
Every regime: what each scan covered and couldn’t read: IRIS produces this.
Explore evidenceOur recommended order; none of the three regimes prescribes one. The evidence-readiness checklist then lists what to keep for an audit.
What to keep for each regulator’s questions, and how to show it is complete.
Each duty beside the SAMA and NCA controls a bank examiner tests, and the transfer rules.
Evidence for each regime’s record, traced to the source, table and scan date.
IRIS maps its evidence to UAE PDPL controls through its unified compliance framework. Its evidence supports your own assessment under each regime. A scored UAE PDPL readiness view isn’t in v1; ask us if you need one.
No, not as a built-in pattern today. Add the fifteen-digit 784 format as a custom pattern; IRIS already recognizes payment-card numbers and IBANs.
No pack maps them. For the sources you connect, the same scan gives the data categories a DIFC Article 15 or ADGM section 28 record needs; which regime applies stays your call.
Start with one entity’s main database: a free assessment scans it with a read-only login you create.