Personal Data Protection Law (PDPL)

The UAE's first federal personal data protection law. It sets lawful-basis, consent, purpose limitation, security, breach notification and data subject rights requirements for controllers and processors in the UAE and for those processing UAE residents' data from abroad, supervised by the UAE Data Office. Government data, the DIFC and ADGM, and health and banking data are excluded.

Official title
Federal Decree-Law No. 45 of 2021 Concerning the Protection of Personal Data
Instrument
Federal Decree-Law No. 45 of 2021
Issued by
President of the UAE
Jurisdiction
UAE Federal
Dates
issued 20 September 2021 · in force 2 January 2022
Status
in force
Topics
Data protection
Official source
uaelegislation.gov.ae · official text (PDF)
Verified
29 October 2026

Summary

Federal Decree-Law No. 45 of 2021 is the UAE's first federal personal data protection law. It came into force on 2 January 2022 (Article 31) and is in force, but its full operation depends on Executive Regulations that Article 28 required the Cabinet to issue within six months of promulgation and that have not yet been published on the legislation portal; Article 29 gives controllers and processors six months from the issue of those regulations to comply, extendable once. Article 26 leaves administrative penalties to a Cabinet decision, so the law currently sets duties without a published fine schedule.

Article 2 applies the law to the processing of personal data by automated or other means where the data subject resides or has a place of business in the UAE, where the controller or processor resides in the UAE, and to every controller or processor residing outside the State that processes data of people inside it. It excludes government data and government entities, data held by security and judicial authorities, purely personal use by an individual, health data and personal banking and credit data that have their own laws, and entities in free zones that have their own data protection legislation, which in practice means the DIFC and ADGM.

Article 4 prohibits processing without the data subject's consent except in listed cases such as performance of a contract, legal claims, data the person has made public and protection of the person's interests. Article 5 sets the principles: fair, transparent and lawful processing for a specific purpose, limited to what is necessary, accurate, secured and not kept longer than needed unless anonymised. Article 6 requires consent to be provable, clear and as easy to withdraw as to give.

Article 7 requires controllers to apply security and privacy measures and data-minimisation defaults, keep a record of processing and appoint only processors that give sufficient guarantees; Article 8 confines processors to the controller's instructions. Article 9 requires the controller to notify the UAE Data Bureau at the time it becomes aware of a breach that prejudices privacy or security, and to notify the affected data subjects. Article 10 requires a data protection officer for high-risk new technology, systematic assessment of sensitive data or large-scale sensitive data. Article 20 requires security measures such as encryption and pseudonymisation, and Article 21 an impact assessment before high-risk processing.

Articles 13 to 18 give data subjects rights of access, portability, correction and erasure, restriction, objection to direct marketing and objection to automated decisions, with human review on request. Articles 22 and 23 allow cross-border transfers to countries with adequate law approved by the Bureau, or otherwise under contractual safeguards, explicit consent, legal claims or contract performance. Articles 24 and 25 provide for complaints to the Bureau and a 30-day grievance to its General Director before any court challenge.

Who it applies to

Any controller or processor established in the UAE outside the DIFC and ADGM, and any controller or processor abroad processing personal data of people inside the UAE; data subjects resident or doing business in the UAE. Excluded: government entities and data, security and judicial data, purely personal use, health and personal banking data under their own laws, and free zones with their own data protection law.

Key provisions

Article 2Applies to processing by automated or other means where the data subject or the controller or processor is in the UAE, and to controllers or processors outside the State processing data of people inside it; excludes government, security and judicial data, personal use, health and personal banking data with their own laws, and free zones with their own data law.
Article 4Processing without the data subject's consent is prohibited except in listed cases such as contract performance, legal claims, public-interest purposes, data the person has made public and protecting the person's interests.
Article 5Processing must be fair, transparent and lawful, for a specific purpose, limited to what is necessary, accurate and up to date, secured, and retained no longer than needed unless anonymised.
Article 6The controller must be able to prove consent; consent must be clear, simple and accessible, and as easy to withdraw as to give, without affecting earlier processing.
Articles 7–8Controllers must apply security and privacy measures, data-minimisation defaults, keep a processing record and appoint only processors with sufficient guarantees; processors act only on the controller's instructions under a written contract and delete data at the end.
Article 9The controller must notify the UAE Data Bureau at the time it becomes aware of a breach that prejudices privacy or security, and notify affected data subjects; processors must alert the controller as soon as they become aware.
Article 10A data protection officer, internal or external, is required where processing involves high-risk new technology or large volumes, systematic assessment of sensitive data including profiling, or large-scale sensitive data.
Articles 13–18Data subject rights: information and access, portability of consent- or contract-based automated data, correction and erasure, restriction, objection to direct marketing, and objection to automated decisions including profiling with human review on request.
Articles 20–21Technical and organisational security measures suited to the risk, including encryption, pseudonymisation, resilience and restoration, and a data protection impact assessment before high-risk processing.
Articles 22–23Cross-border transfers are allowed to jurisdictions with adequate law and an enforcing authority as approved by the Bureau, or otherwise under contractual safeguards, explicit consent, legal claims, contract performance or public interest.
Articles 24–26Complaints go to the Bureau, grievances against its decisions to the General Director within 30 days with a decision within 30 days, and administrative penalties are to be set by the Cabinet on the Bureau's proposal.
Articles 28–31Executive Regulations were due within six months of promulgation; controllers and processors have six months from their issue to comply, extendable once; the Decree-Law came into force on 2 January 2022.

Obligations and deadlines

  • Process personal data only with provable consent or on another Article 4 basis.
  • Keep a record of processing activities and apply privacy-by-default settings (Article 7).
  • Put a written contract in place with every processor and act only on instructions when acting as processor (Article 8).
  • Notify the UAE Data Bureau and affected data subjects of a breach that prejudices privacy or security (Article 9).
  • Appoint a data protection officer where Article 10 processing thresholds are met.
  • Run a data protection impact assessment before high-risk processing (Article 21).
  • Transfer data abroad only under Article 22 adequacy or an Article 23 safeguard.

Penalties

The Decree-Law contains no fine schedule. Article 26 provides that the Cabinet, on the Bureau's proposal, will define the violations and the administrative penalties for them; Article 24 lets the Bureau investigate complaints and impose those penalties once set. Criminal exposure for data misuse sits separately in Articles 6 and 13 of the Cybercrime Law.

In practice — how Polaris handles it

Every company we form holds personal data about shareholders, directors, employees and customers, and we hold KYC files on all of them ourselves, so this law governs both sides of the relationship. Our own privacy notice, retention schedule and processor contracts follow Articles 5 to 9, and because we process AML data under a legal obligation we document that basis rather than relying on consent. For clients we check whether their activity triggers a data protection officer or impact assessment under Articles 10 and 21, which is common for platforms, marketing businesses and anyone profiling users, and we build a breach-response step into their compliance calendar. Where a client sits in the DIFC or ADGM we apply those centres' own data protection laws instead, and where a group transfers data between a UAE entity and a foreign parent we document an Article 23 basis, usually contractual safeguards, pending the Bureau's adequacy list.

Related instruments

Related Polaris services

Source and verification. This page was written from the official text published at uaelegislation.gov.ae, read on 29 October 2026. Quoted from that text: “the Controller shall, at the time it becomes aware of the existence of any breach or violation”
This summary is published for general information by Polaris Corporate Services FZ-LLC, a licensed Trust and Corporate Service Provider. It is not legal advice and does not replace the official text, which prevails in case of difference. Arabic is the authoritative language of UAE federal and emirate legislation; English translations are provided by the issuing authorities. Instruments change: check the status and the official source before relying on this page.

Begin a Conversation

Whether you are establishing a new venture, restructuring an existing enterprise, or exploring residency pathways — we are here to advise.

Arrange a Consultation →