ADGM Data Protection Regulations 2021

The Abu Dhabi Global Market's Data Protection Regulations 2021 (consolidated version, August 2025) as 88 machine-evaluable rules, every binding sentence accounted for and each rule citing its section. Covers lawful bases and consent, special category data and its conditions, data subject rights, solely automated decisions, processors and records, security and deletion (including keeping data to train AI systems), breach notification within 72 hours, impact assessments, Data Protection Officers, and transfers outside ADGM. Compiled from the official consolidated text in the ADGM rulebook; not issued or attested by ADGM.

Answers: Whether personal data may be processed, shared, transferred outside ADGM, used for automated decisions or for marketing under the ADGM Data Protection Regulations, and what the Controller or Processor must do first.

Publisher
The Nomos Exchange
Version
1.0.0
Jurisdiction
ADGM, AE, GCC
Sector
Data Protection, Privacy, Cross-sector
Rules
88
Verification tier
Compiled
Published
2026-11-15
Price
Free to query

Rules

  1. 2. The Regulations do not apply to non-automated Processing of data that is not, and is not meant to be, part of a Filing System.
  2. 2. Processing by a natural person for purely personal or household activity is outside the Regulations.
  3. 2. Processing by public authorities to prevent, investigate, detect or prosecute crime or execute criminal penalties is outside the Regulations.
  4. 3. The Regulations apply to Processing in the context of the activities of an ADGM Establishment of a Controller or Processor, wherever it takes place, and to no other.
  5. 4. Personal Data is Processed lawfully, fairly and transparently.
  6. 4. Personal Data is not further Processed incompatibly with the purposes it was collected for; Archiving and Research Purposes are deemed compatible.
  7. 4. Personal Data is adequate, relevant and limited to what is necessary.
  8. 4. Personal Data is accurate and kept up to date; inaccurate data is erased or rectified without delay.
  9. 4. Personal Data is not kept in identifying form longer than necessary, except for Archiving and Research Purposes with appropriate safeguards.
  10. 4. The Controller is responsible for, and can demonstrate, compliance with the principles.
  11. 5. Processing is lawful only on consent, contract, a legal obligation, vital interests, a public task, or legitimate interests.
  12. 5. Legitimate interests are not a basis where the Data Subject's interests or rights override them, in particular for a Child.
  13. 5. Legitimate interests are not a basis for Processing necessary for a public-task purpose under s. 5(1)(e).
  14. 5. Before Processing for another purpose, the Controller assesses compatibility with the original purpose.
  15. 6. Where Processing is based on Consent, the Controller can demonstrate it.
  16. 6. A request for Consent in a declaration covering other matters is clearly distinguishable and in plain language.
  17. 6. When the Data Subject withdraws Consent, Processing on that Consent may not continue.
  18. 6. Withdrawing Consent is as easy as giving it, and the Data Subject is told of the right first.
  19. 6. Consent is not freely given where the Data Subject has no genuine choice or a contract is made conditional on unnecessary Consent.
  20. 7. Processing Special Categories of Personal Data is prohibited unless one of the conditions in s. 7(2)(a) to (k) applies.
  21. 7. The employment-law and substantial-public-interest conditions are met only with an appropriate policy document in place.
  22. 8. Where the Controller can show it cannot identify the Data Subject, it tells them so where possible.
  23. 9. Processing for Archiving and Research Purposes has safeguards and does not cause substantial damage or distress.
  24. 9. Archiving and Research Processing is not used for measures or decisions about a particular Data Subject, unless for approved medical research.
  25. 10. Information and communications to Data Subjects are concise, transparent, intelligible, accessible and in plain language.
  26. 10. The Controller facilitates the exercise of rights and refuses a request only where it cannot identify the Data Subject, the request is unreasonable or excessive, or an exemption applies.
  27. 10. The Controller answers a rights request without undue delay and within two months of receipt.
  28. 10. An extended response is given within the one further month allowed.
  29. 10. Where the Controller does not act on a request, it tells the Data Subject the reasons and of their right to complain and seek a judicial remedy.
  30. 10. Information and actions under ss. 11 to 20 and 33 are free of charge unless the request is unreasonable or excessive.
  31. 11. When collecting from the Data Subject, the Controller gives them the information s. 11(1)-(2) lists.
  32. 11. Before Processing data collected from the Data Subject for a new purpose, the Controller informs them, unless they already have the information.
  33. 12. Where data was not obtained from the Data Subject, the Controller gives the s. 12 information within the time s. 12(3) sets, unless an exemption in s. 12(5) applies.
  34. 12. Before Processing indirectly obtained data for a new purpose, the Controller informs the Data Subject.
  35. 13. The Data Subject gets confirmation, access, the s. 13(1) information and a copy, unless an exemption applies.
  36. 13. A copy is not given where it would adversely affect the rights of others.
  37. 14. Inaccurate data is rectified and incomplete data completed without undue delay, unless technically infeasible as disclosed at collection.
  38. 15. Where a ground in s. 15(1) applies, the data is erased without undue delay, unless an exception in s. 15(3)-(4) applies.
  39. 15. Where the Controller made the data public and must erase it, it takes reasonable steps to inform Controllers Processing it.
  40. 16. Where a ground in s. 16(1) applies, Processing is restricted on request.
  41. 16. Restricted data is only stored, or Processed with consent, for legal claims, to protect another person's rights or for important public interest.
  42. 16. The Data Subject is informed before a restriction is lifted.
  43. 17. Each Recipient is told of a rectification, erasure or restriction, unless impossible or disproportionate.
  44. 17. The Data Subject is told about those Recipients on request.
  45. 18. Where Processing is based on consent or contract and automated, the Data Subject receives their data in a portable format or has it transmitted, except for public-task Processing.
  46. 18. Portability does not adversely affect the rights of others.
  47. 19. After an objection to Processing based on s. 5(1)(e) or (f), Processing stops unless legitimate grounds override the Data Subject or it is needed for legal claims.
  48. 19. Where the Data Subject objects to direct marketing, the data is not Processed for it.
  49. 19. An objection to Archiving and Research Processing is honoured unless it is necessary for a public-interest task.
  50. 19. The rights to object are brought explicitly to the Data Subject's attention at the latest at the first communication.
  51. 20. A decision based solely on automated Processing with legal or similarly significant effects is made only when necessary for a contract, on explicit consent, or as authorised by law with notice.
  52. 20. For contract and consent decisions, the Data Subject can obtain human intervention, express their view and contest the decision.
  53. 20. Automated decisions are not based on Special Categories of Personal Data unless explicit consent or substantial public interest applies with safeguards.
  54. 22. The Controller implements, reviews and updates measures to ensure and demonstrate compliance.
  55. 23. Systems are designed for compliance, and by default only necessary data is Processed.
  56. 24. The Controller pays the Data Protection Fee and notifies the Commissioner of Data Protection when it starts Processing.
  57. 24. The Renewal Fee is paid within one month after each anniversary.
  58. 25. Joint Controllers set their respective responsibilities in a transparent arrangement, unless Applicable Law does.
  59. 26. The Controller uses only Processors that provide sufficient guarantees.
  60. 26. A Processor does not engage another Processor without the Controller's prior written authorisation.
  61. 26. Processing by a Processor is governed by a written contract with the terms s. 26(3) requires.
  62. 26. A Processor immediately tells the Controller of an instruction it believes contravenes the Regulations.
  63. 26. A sub-processor is bound by contract to the same data protection obligations.
  64. 27. No one with access Processes Personal Data except on the Controller's instructions, unless Applicable Law requires it.
  65. 28. The Controller keeps a written record of Processing activities with the listed contents, available to the Commissioner of Data Protection.
  66. 28. The Processor keeps a written record of the Processing it carries out for each Controller.
  67. 29. The Controller and Processor cooperate, on request, with the Commissioner of Data Protection.
  68. 30. Appropriate measures ensure security appropriate to the risk.
  69. 30. Persons acting under the Controller's or Processor's authority Process data only on instructions, unless required by law.
  70. 31. When the basis for Processing ends or erasure is required, all the data is deleted, anonymised, pseudonymised, encrypted or put beyond further use, unless kept for legal claims or law, public-interest research or lawful AI training.
  71. 31. Before relying on the research or AI-training retention exemptions, a DPIA is carried out, and the data is used only as needed.
  72. 31. There is a policy and process for data kept under s. 31(4) once the grounds no longer apply.
  73. 32. A Personal Data Breach is notified to the Commissioner of Data Protection without undue delay and, where feasible, within 72 hours, unless unlikely to risk rights.
  74. 32. A Processor notifies the Controller of a breach without undue delay.
  75. 32. Every Personal Data Breach is documented with its facts, effects and remedial action.
  76. 33. A breach likely to result in a high risk is communicated to the Data Subjects without undue delay, unless an exemption in s. 33(3) applies.
  77. 34. Before Processing likely to result in a high risk, the Controller carries out a DPIA with the listed contents, with its DPO's advice.
  78. 34. The Controller reviews Processing against the DPIA, at least when the risk changes.
  79. 34. Where the DPIA shows a high risk, the Commissioner of Data Protection is notified before the Processing.
  80. 35. A qualified DPO is appointed where Processing is by a public authority, involves large-scale systematic monitoring, or large-scale Special Categories.
  81. 35. The Commissioner of Data Protection is notified within one month of a DPO's appointment or resignation.
  82. 36. The DPO is involved, resourced, protected from dismissal for their tasks, reports to the highest management and is bound by confidentiality.
  83. 40. Personal Data is transferred outside ADGM only on an adequacy decision, appropriate safeguards or a derogation.
  84. 42. A transfer on appropriate safeguards uses one of the instruments s. 42(3) lists, or s. 42(4) safeguards the Commissioner has authorised.
  85. 42. Ad hoc contractual clauses and administrative arrangements need the Commissioner of Data Protection's authorisation.
  86. 44. Without adequacy or safeguards, a transfer takes place only on one of the conditions in s. 44(1).
  87. 44. Public authorities exercising public powers cannot rely on the consent and contract derogations.
  88. 45. On a request for data from a public authority outside ADGM, the Controller or Processor checks its validity and proportionality, assesses the impact and seeks assurances.

Query this authority

People, software and AI agents can ask it whether an action may proceed and get AUTHORIZED, DENIED or ESCALATED with the rule that decided it: POST https://exchange.nomosprotocol.com/api/exchange/artifacts/adgm-data-protection-regulations-2021/query. SDK, MCP and REST.