DIFC Data Protection Law (DIFC Law No. 5 of 2020)

The DIFC Data Protection Law (DIFC Law No. 5 of 2020, consolidated to July 2025) as 199 evaluable rules, each citing its Article and quoting the law word for word. Answer 12 plain yes/no questions about an action and get a firm answer: an ordinary action with nothing to declare is allowed; anything the law restricts is denied or sent to a person, with the article that decided it. Covers application (Art. 6), principles, lawfulness, special categories, consent and legitimate interests (Art. 9-13), accountability, records, the DPO and impact assessments (Art. 14-21), cessation, joint controllers and processors (Art. 22-25), transfers out of the DIFC and data sharing (Art. 26-28), information to data subjects (Art. 29-31), data subject rights (Art. 32-40), breach notification (Art. 41-42), codes, certification, directions and fines (Art. 46-62, Schedule 2) and exemptions (Art. 65). A reference conversion by NOMOS, not an official instrument of the DIFC Commissioner of Data Protection. Not legal advice.

Answers: Whether personal data may be processed, shared or transferred out of the DIFC under the DIFC Data Protection Law, what the Controller or Processor must do first, and which contraventions carry an administrative fine.

Publisher
The Nomos Exchange
Version
1.2.0
Jurisdiction
AE, DIFC, GCC
Sector
Data Protection, Privacy, Cross-sector
Rules
199
Verification tier
Compiled
Published
2026-11-14
Price
Free to query

Rules

  1. 6. The Law applies to Processing by automated means, or of Personal Data in a Filing System, by a DIFC-incorporated Controller or Processor or in the DIFC as part of stable arrangements.
  2. 6. The Law does not apply to Processing by a natural person in a purely personal or household activity with no connection to a commercial purpose.
  3. 9. Personal Data must be Processed lawfully, fairly and in a transparent manner in relation to the Data Subject.
  4. 9. Personal Data must be Processed for specified, explicit and legitimate purposes determined at the time of collection.
  5. 9. Personal Data must not be Processed in a way that is incompatible with the purposes determined at collection.
  6. 9. Personal Data must be Processed in a manner that permits ready access to it for compliance with the Law, in particular Articles 9, 14 and 33.
  7. 9. Personal Data must be relevant and limited to what is necessary for the purposes determined at collection.
  8. 9. Personal Data must be Processed in accordance with the application of Data Subject rights under the Law.
  9. 9. Personal Data must be accurate and, where necessary, kept up to date, including via erasure or rectification without undue delay.
  10. 9. Personal Data must be kept in a form that permits identification of the Data Subject for no longer than necessary for the purposes.
  11. 9. Personal Data must be kept secure with appropriate technical or organisational measures against unauthorised or unlawful Processing and accidental loss, destruction or damage.
  12. 9. The Controller or Processor must be able to demonstrate to the Commissioner its compliance with Article 9(1).
  13. 10. Personal Data may be Processed only on one of the Article 10 lawful bases (consent,contract,legal_obligation,vital_interests,difc_body_task,difc_body_powers,difc_body_vested_powers,legitimate_interests).
  14. 10. Legitimate interests are not a lawful basis where they are overridden by the interests or rights of the Data Subject.
  15. 11. Special Categories of Personal Data may not be Processed unless one of the Article 11 conditions applies (explicit_consent,employment,vital_interests_incapable,non_profit_body,made_public_by_data_subject,legal_claims,applicable_law_requirement,aml_ctf_crime,health_or_social_care,protecting_public_from_misconduct,bias_protection,substantial_public_interest), in addition to Articles 9 and 10.
  16. 11. A non-profit body relying on Article 11(d) may Process only data of members, former members or regular contacts, and may not disclose it to a Third Party without consent.
  17. 11. Where Special Categories are Processed to comply with a specific requirement of Applicable Law, the Controller must give the Data Subject clear notice as soon as reasonably practicable, unless that law prohibits notice.
  18. 11. The Article 11(i) health and social care condition applies only where the data is processed by or under a health professional, or another person, bound by secrecy under Applicable Law.
  19. 12. Consent relied on under Article 10(a) or 11(a) must be freely given by a clear affirmative act showing an unambiguous indication of consent.
  20. 12. Consent made a condition of an act is not freely given for Processing not reasonably necessary for that act, or for excessive categories of Personal Data.
  21. 12. Where Processing is based on consent, the Controller must be able to demonstrate that consent was freely given.
  22. 12. Where Processing covers multiple purposes, consent must be obtained for each purpose in a clearly distinguishable, intelligible and accessible form.
  23. 12. A request for consent to Processing must be clearly distinguishable from consent sought for other matters.
  24. 12. At the time consent is obtained the Data Subject must be informed of the right to withdraw it and how.
  25. 12. Withdrawing consent should not require undue effort and should be at least as easy as giving it.
  26. 12. Other than for a Single Discrete Incident, a Controller relying on consent should assess its ongoing validity.
  27. 12. Where the ongoing assessment concludes the Data Subject would no longer expect the Processing, he must be contacted without delay and asked to re-affirm consent.
  28. 12. Consent is deemed withdrawn if there is no positive re-affirmation within a reasonable period after the Data Subject was contacted.
  29. 12. The Controller must be able to demonstrate to the Commissioner methods and procedures for recording consent and its withdrawal, periodically evaluated.
  30. 12. Where consent-based Processing is not a Single Discrete Incident and continues, the Data Subject should periodically be able to re-affirm or withdraw consent.
  31. 13. A public authority subject to DIFC law may not rely on legitimate interests to Process Personal Data.
  32. 13. A Controller in a Group may have a legitimate interest in transferring Personal Data within its Group for internal administrative purposes.
  33. 13. Processing necessary and proportionate to prevent fraud or ensure network and information security is a legitimate interest of the Controller.
  34. 14. A Controller or Processor must establish a program to demonstrate compliance, proportionate to its scale, resources, data and risks.
  35. 14. Technical and organisational measures must ensure security appropriate to the risks of the Processing and against all unlawful Processing.
  36. 14. Measures must ensure that by default only Personal Data necessary for each specific purpose is Processed.
  37. 14. Measures must be reviewed and updated where necessary to reflect legal, operational and technical developments.
  38. 14. Processing must be designed to reinforce data protection principles, and by default only necessary data is Processed and not made accessible to an indefinite number of persons.
  39. 14. A Controller offering online services through a platform must default to the minimum Personal Data and let users actively choose and easily change privacy preferences.
  40. 14. A Controller or Processor must implement and maintain a written data protection policy proportionate to its Processing and consistent with the Law.
  41. 14. A Controller or Processor must register with the Commissioner by filing a notification of Processing operations and keep it up to date.
  42. 14. A notification of Processing operations must be accompanied by the prescribed fee.
  43. 15. A Controller must keep a written record of its Processing activities with at least the Article 15(1) information.
  44. 15. A Processor must keep a written record of all categories of Processing carried out on behalf of a Controller.
  45. 16. A DPO must be appointed by a DIFC Body (other than the Courts in their judicial capacity), by a Controller or Processor performing High Risk Processing Activities systematically or regularly, or where the Commissioner requires one.
  46. 16. Where no DPO is required, responsibility for data protection oversight and compliance must be clearly allocated and the persons named to the Commissioner on request.
  47. 16. A Group may appoint a single DPO only if he is easily accessible from each entity in the Group.
  48. 16. The DPO must reside in the UAE unless employed within the Group and performing a similar function for it internationally.
  49. 16. The DPO's contact details must be published so third parties can reach the DPO without disproportionate effort, and the DPO's identity confirmed to the Commissioner in writing on request.
  50. 17. A DPO must know the Law, be able to perform the Article 18 tasks, act independently, report to senior management, and have sufficient resources and access to information.
  51. 17. A DPO must be transparent and cooperative with the Commissioner and notify it of all relevant information, except privileged material or material under a conflicting non-disclosure obligation.
  52. 18. A Controller or Processor must involve its DPO properly and in time, give it sufficient resources, and let it act independently.
  53. 18. A DPO may hold other roles, but additional tasks must not cause a conflict of interest or prevent proper performance of the DPO role.
  54. 18. A DPO must at least monitor compliance, inform and advise, advise on impact assessments, cooperate with and be the contact point for the Commissioner, and act on its findings.
  55. 19. Where a DPO is required, the DPO must assess the Controller's Processing at least once a year and submit the Annual Assessment to the Commissioner.
  56. 19. The Annual Assessment must report the Controller's Processing activities and state whether it intends High Risk Processing in the next period.
  57. 20. A Controller must carry out a data protection impact assessment before High Risk Processing Activities, unless it relies on a current Group assessment or Article 20(9) applies.
  58. 20. Where a DPO is appointed, the DPO must oversee data protection impact assessments.
  59. 20. An impact assessment must contain at least a description, a necessity and proportionality assessment, a lawful-basis analysis, a risk assessment and the measures envisaged.
  60. 20. Where appropriate, the Controller should seek the input of Data Subjects or their representatives on the intended Processing.
  61. 20. A Controller must review whether Processing follows its impact assessment, regularly and whenever the risk changes.
  62. 20. A Processor appointed or being appointed must give the Controller all information reasonably requested for the impact assessment.
  63. 21. A Controller must consult the Commissioner where an impact assessment shows the risks remain particularly high despite the measures taken.
  64. 21. A Controller must implement without delay any direction the Commissioner makes after a consultation, including discontinuing the Processing.
  65. 21. Where the Commissioner determines the Processing is unlawful, the Controller or Processor must cease it immediately unless the Commissioner directs otherwise.
  66. 21. When consulting the Commissioner, the Controller must provide responsibilities, purposes and means, safeguards, DPO contact details, the impact assessment and anything else requested.
  67. 21. A Processor appointed or being appointed must assist the Controller in any prior consultation with the Commissioner.
  68. 22. When the basis for Processing ends, all Personal Data, including Processors' copies, must be deleted, anonymised, pseudonymised or encrypted, or else archived beyond further use, unless an Article 22(4) ground applies.
  69. 22. Where data is archived beyond further use, the Controller and Processor must have, follow and be able to demonstrate a strategy for its permanent deletion, anonymisation, pseudonymisation or encryption.
  70. 22. Before relying on the research or AI-training retention grounds, the Controller or Processor must carry out an Article 20 impact assessment.
  71. 22. Processing of Personal Data kept under Article 22(4) must be limited to what is necessary for that purpose.
  72. 22. A Controller or Processor must have a policy and process for Article 22(4) data and delete or protect it when the grounds no longer apply.
  73. 23. Joint Controllers must define their responsibilities in a legally binding written agreement covering Data Subject rights and information.
  74. 23. The joint controller agreement, or an appropriate summary, must be made available to affected Data Subjects.
  75. 24. Processing by a Processor must be governed by a legally binding written agreement; starting without one is a breach by both.
  76. 24. A Controller may only use Processors that provide sufficient assurances of appropriate technical and organisational measures.
  77. 24. A Processor may not engage a Sub-processor without the Controller's prior written authorisation; a general authorisation requires conditions enabling the Sub-processor's assurances.
  78. 24. Under a general authorisation, the Processor must inform the Controller of intended Sub-processor changes and take account of good-faith objections.
  79. 24. A Processor may not engage a Sub-processor unless a written agreement with the Article 24(5) content fully delegates its obligations.
  80. 24. Each Controller-Processor and Processor-Sub-processor agreement must set out the Article 24(5)(a) particulars and include the Article 24(5)(b) commitments.
  81. 24. A Processor or Sub-processor must immediately tell the Controller or Processor if it believes the Processing infringes the Law.
  82. 25. Persons acting under a Controller's or Processor's authority with access to Personal Data must not Process it except on the Controller's instructions, unless Applicable Law requires it.
  83. 26. Personal Data may be transferred out of the DIFC only with adequate protection (Art. 26) or under Article 27 safeguards, derogations or limited circumstances.
  84. 27. A transfer on appropriate safeguards needs one of the Article 27(2) instruments and enforceable Data Subject rights and effective remedies.
  85. 27. A transfer on a derogation must rely on one of the specific Article 27(3) derogations.
  86. 27. The international financial markets derogation does not apply where the Controller's interests are overridden by the Data Subject's legitimate interests in his particular situation.
  87. 27. Binding Corporate Rules may be relied on only for lawful transfers within the Group and once reviewed and approved by the Commissioner.
  88. 27. A transfer with no other ground may take place only if it is not repetitive, concerns few Data Subjects, serves compelling legitimate interests not overridden, and follows a documented assessment with safeguards.
  89. 27. The Controller must inform the Commissioner of any Article 27(4) transfer and inform the Data Subject of it and the compelling legitimate interests.
  90. 27. A public authority may not rely on the explicit-consent or contract derogations, or on the limited-circumstances transfer.
  91. 27. A request to the Commissioner to approve Binding Corporate Rules approved elsewhere must include the full copy and approval status, the transfers, and evidence of any powers to bind.
  92. 27. If Binding Corporate Rules are amended, a revised copy showing all edits must be given to the Commissioner without delay.
  93. 27. Binding Corporate Rules whose revision the Commissioner rejected may no longer be relied on.
  94. 27. A Controller or Processor must confirm to the Commissioner in writing each year that its approved Binding Corporate Rules are unchanged and used for the same transfers.
  95. 28. On a Requesting Authority's request, the Controller or Processor should check its validity and proportionality, assess and mitigate the risks, and seek written assurances where practicable.
  96. 28. Personal Data may be disclosed to a Requesting Authority only after reasonable steps confirm the request is valid and proportionate, with notice to the Controller where possible.
  97. 29. When collecting Personal Data from the Data Subject, the Controller must give at least the Article 29(1) information, concisely and in plain language, unless he already has it.
  98. 29. If the Processing will restrict rectification, erasure or objection, the Controller must explain the impact clearly and be satisfied the Data Subject understands and acknowledges it.
  99. 30. Where Personal Data is not obtained from the Data Subject, the Controller must give him at least the Article 30(1) information, unless an Article 30(3) exception applies.
  100. 30. The Article 30 information must be provided no later than one month after obtaining the Personal Data.
  101. 30. Where the data is used to communicate with the Data Subject, the information must be provided at the latest at the first communication.
  102. 30. Where disclosure to a Processor or Third Party is envisaged, the information must be provided at the latest when the data is first disclosed.
  103. 31. Article 29 and 30 information must be in writing (electronically where appropriate), or orally at the Data Subject's request with his identity verified.
  104. 31. A Controller relying on public policies for Article 29/30 information must clearly direct the Data Subject to them, and they must be concise, transparent and in plain language.
  105. 32. When consent is withdrawn the Controller must apply Article 22, cease Processing as soon as reasonably practicable and ensure its Processors do the same.
  106. 33. A Data Subject's Article 33(1) request must be met without charge within one month, or within a further two months where notice of an extension was given within the first month.
  107. 33. Failing to rectify or erase because it is technically infeasible is compliant only if the Controller collected the data from the Data Subject and told him explicitly and prominently at collection.
  108. 33. On request, the Controller must erase the Data Subject's Personal Data where an Article 33(2) ground applies, unless it must retain it under Applicable Law or for legal claims.
  109. 33. Where a Data Subject suffers adverse effects because the Controller cannot rectify data (not caused by his own inaccurate data), the Controller must give all reasonable assistance to mitigate them.
  110. 33. Where rectification, erasure or objection is properly exercised, the Controller must direct all recipients and Processors to rectify, erase, or cease and return or erase the data.
  111. 33. Where requests are manifestly unfounded or excessive, the Controller may charge a reasonable fee or refuse with written reasons.
  112. 33. A Controller relying on Article 33(7) or 33(8) must record each instance and its reasons in a register.
  113. 33. Where the Controller reasonably doubts the requester's identity it may ask for more information, and the response period starts only when identity is reasonably established.
  114. 33. A copy given under Article 33(1)(b) must not disclose other individuals' Personal Data in a way that may infringe their rights; it may be redacted.
  115. 33. Information supplied under Article 33 must reflect the data when the request was received, allowing only changes that would have been made anyway.
  116. 33. The Controller may restrict information under Article 33(1) only to the extent and for as long as necessary and proportionate for an Article 33(15) purpose.
  117. 33. Where information is restricted, the Data Subject must be told in writing without undue delay of the restriction, its reasons and his rights, unless telling him would undermine the restriction.
  118. 34. After a justified objection the Controller's Processing must no longer include the Personal Data, and Article 22 applies; an Article 34(1)(a) objection is justified unless compelling grounds override it or the Article 34(3) disclosure was made.
  119. 34. Before Personal Data is first disclosed to or used for third parties' direct marketing, the Data Subject must be informed and expressly offered the right to object.
  120. 34. A Data Subject may object at any time to Processing for direct marketing, including related Profiling, and the Processing must stop.
  121. 34. No later than its first communication, the Controller must bring the Article 34(1) rights explicitly to the Data Subject's attention, prominently and separately.
  122. 35. While Processing is restricted under Article 35(1), only storage, legal claims, protection of another person's rights, Substantial Public Interest, or consented Processing may continue.
  123. 35. A Controller lifting a restriction must inform the Data Subject in writing.
  124. 36. The Controller must tell each recipient of any rectification, erasure or restriction under Articles 33-35, unless impossible or disproportionate.
  125. 36. If the Data Subject asks, the Controller must tell him who the recipients are.
  126. 37. Where Processing is based on consent or contract and automated, the Data Subject may receive his data in a machine-readable format or have it transmitted directly, unless that infringes another person's rights.
  127. 38. A Data Subject may object to a solely automated decision with legal or serious effects and require manual review, unless an Article 38(2) ground applies (which never applies to a minor).
  128. 38. A Controller may rely on the contract or explicit-consent grounds only with suitable safeguards including manual review.
  129. 38. Decisions may not be based solely on automated Processing of Special Categories unless the Data Subject explicitly consented or Substantial Public Interest applies with safeguards.
  130. 39. A Controller may not discriminate against a Data Subject for exercising Part 6 rights, unless the difference is objectively and reasonably related to the value of his data.
  131. 39. Incentives for Processing are permitted only with clearly communicated terms, process and Processing, compliance with the Law, and withdrawal without penalty at any time.
  132. 39. Incentive schemes must not be coercive or unreasonable, including where the chance of reward is disproportionately low against the value of the data.
  133. 40. A Controller must offer at least two non-onerous methods for Data Subjects to request to exercise their rights.
  134. 40. A Controller with a website must offer at least one free method via the website without requiring an account.
  135. 40. At least one method should correspond to the contact details given under Article 29 or 30.
  136. 41. A Controller must notify the Commissioner of a Personal Data Breach compromising a Data Subject's confidentiality, security or privacy as soon as practicable.
  137. 41. A Processor must notify the relevant Controller without undue delay after becoming aware of a Personal Data Breach.
  138. 41. A Controller or Processor must fully co-operate with the Commissioner's investigation of a Personal Data Breach.
  139. 41. The breach notification must describe the breach, give a contact point, the likely consequences and the measures taken; information not yet available may follow in phases.
  140. 41. A Controller must document every Personal Data Breach in writing, sufficiently for the Commissioner to verify compliance, and make it available without delay on request.
  141. 42. Where a breach is likely to result in a high risk to Data Subjects, the Controller must tell them as soon as practicable, by public communication where individual communication is disproportionate.
  142. 42. If there is an immediate risk of damage to the Data Subject, the Controller must promptly communicate with him.
  143. 42. The communication to Data Subjects must describe the breach in clear and plain language with the Article 41(4)(b)-(d) information and, where possible, recommendations.
  144. 46. A Controller or Processor must give the Commissioner access to premises, equipment and information required for an audit, except privileged or conflicting non-disclosure material.
  145. 48. A code of conduct must contain mechanisms enabling its association or body to monitor compliance by those applying it.
  146. 49. An accredited monitoring body must act on infringements of the code, including suspension or exclusion, and inform the Commissioner with reasons.
  147. 50. Certification may only be issued by a certification body approved under Article 51, or by the Commissioner.
  148. 50. A certification remains valid for at most three years, renewable while the conditions are met.
  149. 50. The approved body or Commissioner must withdraw the certification of a Controller or Processor that no longer meets the requirements.
  150. 51. A body applying for accreditation must provide in writing all information necessary or requested by the Commissioner.
  151. 51. An accreditation lasts at most five years, renewable on continuing compliance.
  152. 52. A Controller or Processor must comply with an Article 52(1) requirement, except for privileged or conflicting non-disclosure material; failing to is a breach.
  153. 57. No person may, without reasonable excuse, intentionally obstruct an auditor appointed under Article 57(1).
  154. 59. A direction must state the contravention and that the Controller or Processor may seek judicial review of the decision and its terms.
  155. 59. A Controller or Processor that fails to comply with a direction contravenes the Law and may be fined or liable for damages.
  156. 59. An affected party may ask the Commissioner to review a direction within fourteen days of receiving it.
  157. 62. An Article 62(2) administrative fine may not exceed the Schedule 2 amount for each contravention.
  158. 62. A fine not paid within the notice period, or ten days after an objection is determined, with no objection in progress, may be recovered by application to the Court.
  159. 62. The Commissioner may ask the Court for damages for a Data Subject only where he suffered material damage and is disadvantaged in claiming himself.
  160. 63. A Controller, Processor or Data Subject may appeal a finding of the Commissioner to the Court within thirty days.
  161. 65. Articles 26, 29, 30, 32-35, 37-39 and 42 do not apply to a DIFC Body as Controller to the extent compliance would materially prejudice its financial-protection or law-enforcement functions.
  162. 65. A DIFC Body must record each reliance on the Article 65(2) exemption with the Article and the reasons.
  163. SCHEDULE 2. An administrative fine for a contravention of Article 9 may not exceed USD 50,000.
  164. SCHEDULE 2. An administrative fine for a contravention of Article 10 may not exceed USD 50,000.
  165. SCHEDULE 2. An administrative fine for a contravention of Article 11 may not exceed USD 50,000.
  166. SCHEDULE 2. An administrative fine for a contravention of Article 12 may not exceed USD 50,000.
  167. SCHEDULE 2. An administrative fine for a contravention of Article 14(1) may not exceed USD 25,000.
  168. SCHEDULE 2. An administrative fine for a contravention of Article 14(2) may not exceed USD 50,000.
  169. SCHEDULE 2. An administrative fine for a contravention of Article 14(3) may not exceed USD 25,000.
  170. SCHEDULE 2. An administrative fine for a contravention of Article 14(4) may not exceed USD 25,000.
  171. SCHEDULE 2. An administrative fine for a contravention of Article 14(5) may not exceed USD 25,000.
  172. SCHEDULE 2. An administrative fine for a contravention of Article 14(7) may not exceed USD 25,000.
  173. SCHEDULE 2. An administrative fine for a contravention of Article 15 may not exceed USD 25,000.
  174. SCHEDULE 2. An administrative fine for a contravention of Article 16 may not exceed USD 50,000.
  175. SCHEDULE 2. An administrative fine for a contravention of Article 19 may not exceed USD 25,000.
  176. SCHEDULE 2. An administrative fine for a contravention of Article 20 may not exceed USD 50,000.
  177. SCHEDULE 2. An administrative fine for a contravention of Article 22 may not exceed USD 25,000.
  178. SCHEDULE 2. An administrative fine for a contravention of Article 23 may not exceed USD 25,000.
  179. SCHEDULE 2. An administrative fine for a contravention of Article 24 may not exceed USD 25,000.
  180. SCHEDULE 2. An administrative fine for a contravention of Article 25 may not exceed USD 25,000.
  181. SCHEDULE 2. An administrative fine for a contravention of Article 26 may not exceed USD 25,000.
  182. SCHEDULE 2. An administrative fine for a contravention of Article 27 may not exceed USD 50,000.
  183. SCHEDULE 2. An administrative fine for a contravention of Article 28 may not exceed USD 50,000.
  184. SCHEDULE 2. An administrative fine for a contravention of Article 29 may not exceed USD 75,000.
  185. SCHEDULE 2. An administrative fine for a contravention of Article 30 may not exceed USD 75,000.
  186. SCHEDULE 2. An administrative fine for a contravention of Article 31 may not exceed USD 75,000.
  187. SCHEDULE 2. An administrative fine for a contravention of Article 32(3) may not exceed USD 75,000.
  188. SCHEDULE 2. An administrative fine for a contravention of Article 33 may not exceed USD 100,000.
  189. SCHEDULE 2. An administrative fine for a contravention of Article 34 may not exceed USD 100,000.
  190. SCHEDULE 2. An administrative fine for a contravention of Article 35 may not exceed USD 100,000.
  191. SCHEDULE 2. An administrative fine for a contravention of Article 36 may not exceed USD 100,000.
  192. SCHEDULE 2. An administrative fine for a contravention of Article 37 may not exceed USD 100,000.
  193. SCHEDULE 2. An administrative fine for a contravention of Article 38 may not exceed USD 100,000.
  194. SCHEDULE 2. An administrative fine for a contravention of Article 39 may not exceed USD 50,000.
  195. SCHEDULE 2. An administrative fine for a contravention of Article 40 may not exceed USD 25,000.
  196. SCHEDULE 2. An administrative fine for a contravention of Article 41 may not exceed USD 50,000.
  197. SCHEDULE 2. An administrative fine for a contravention of Article 42 may not exceed USD 50,000.
  198. SCHEDULE 2. An administrative fine for a contravention of Article 59 may not exceed USD 75,000.
  199. SCHEDULE 2. An administrative fine for a contravention of Article 65 may not exceed USD 75,000.

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/difc-data-protection-law-difc-law-no-5-of-2020/query. SDK, MCP and REST.