Regulation · United Arab Emirates
UAE PDPL
At a glance
- Jurisdiction
- United Arab Emirates (outside free zones with their own laws)
- Supervisory authority
- UAE Data Office
- In force
- In force since 2 January 2022 · Executive Regulations not yet published
- Official name
- Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data
What the UAE PDPL asks of you, article by article
How GovernID fits: The UAE PDPL asks you to process with consent or a listed exception, keep a record of processing, protect data and report breaches. GovernID builds that proof into collection. Your RoPA records each activity, privacy notices are generated from it in Arabic and English, and each record collected through GovernID carries the notice, consent and retention period that applied on the day it arrived.
Good to know: Several details, such as breach timing, are left to the Executive Regulations. Companies in free zones with their own data protection laws, such as the DIFC and ADGM, follow those laws instead.
| Requirement | Article | What GovernID does | What stays with you |
|---|---|---|---|
| Scope. The law applies to processing in the UAE and to controllers abroad that process data of people in the UAE. It does not cover government data, health and banking data that have their own laws, or companies in free zones with their own data protection laws. | Art. 2 | GovernID hosts each company’s data in the country where it is registered, and each company in a group works in its own portal. | Deciding whether the law or a free zone law applies to you. |
| Processing controls. Process fairly, transparently and lawfully, for specific purposes, with only the data needed, kept accurate, secure and no longer than necessary. | Art. 5 | Each processing activity in your RoPA records its purpose, data categories, legal basis and retention period. Every field is classified before the first record arrives, and each record keeps the terms it was collected under. | Deciding purposes and judging what is necessary. |
| Consent and its exceptions. Processing needs consent unless one of the listed cases applies, such as a contract, a legal obligation or protecting public interest. You must be able to prove consent, the request must be clear, and people can withdraw it. | Art. 4, 6 | The approved consent text is shown at collection, one purpose per box, never pre-ticked. GovernID keeps the version on the record with the dates consent was given and withdrawn. People withdraw in the Privacy Center. | Deciding which case applies, and approving the consent text. |
| Controller obligations. Put in place technical and organisational measures, by design and by default, and keep a record of processing with the details the law lists. | Art. 7 | Your RoPA records each activity with its purpose, data categories, recipients, transfers and safeguards. Process owners confirm their activities and every confirmation is logged. Compliance Reporting exports the record with its version history. | Keeping the record complete for processing outside GovernID. |
| Processors. Processors act on the controller’s instructions under a contract, and keep their own record of processing. | Art. 8 | Processors and other recipients are recorded in each activity and shown as processing flows. | Choosing processors and signing the contracts. |
| Breach notification. Notify the Data Office of a breach that affects people’s privacy, confidentiality or security, and inform the people affected where the breach affects them. Timing and content follow the Executive Regulations. | Art. 9 | Breach Impact Analysis shows which activities used the affected system, which data was kept there and which safeguards applied. | Assessing the breach and notifying. |
| Data protection officer. Appoint a DPO in the cases the law lists, such as high-risk processing or large-scale sensitive data, and give them what they need to work. | Art. 10–12 | Your DPO works from one RoPA, sees which activities are confirmed and which have changed, and can export reports for management. | Appointing and supporting the DPO. |
| Right to information. People can ask for the categories of data, purposes, recipients, retention period, transfers and their rights. Some items must be given before processing starts. | Art. 13 | Privacy notices are generated from the RoPA with these items and served as a link at the moment of collection. Each record keeps the notice version the person saw. | Approving the notice and keeping it accurate. |
| Data subject rights. Portability, correction and erasure, restriction, stopping processing, and objecting to decisions made only by automated processing. | Art. 14–18 | In the Privacy Center, people see the records that contain their verified contact details, withdraw consent, object to processing and get an instant preliminary report. DSAR Automation finds every record of a person across connected collection points. | Handling portability, correction, erasure and restriction requests, and requests made through other channels. |
| Channels for requests. Give people clear and appropriate ways to contact you about their data and their rights. | Art. 19 | Requests made in the Privacy Center reach your team at once, with their date, and consent withdrawals are tracked until handled. | Running your other contact channels. |
| Security of processing. Apply technical and organisational measures appropriate to the risk, such as encryption and pseudonymisation. | Art. 20 | Safeguards are recorded for each activity and storage location, and Corporate Privacy Memory keeps how each activity looked on any past date. | Implementing and testing the measures. |
| Impact assessment. Assess processing that is likely to be high risk, such as new technologies or large-scale sensitive data, before it starts. | Art. 21 | GovernID recommends a DPIA for activities with sensitive data or transfers abroad. The assessment opens with the facts from your RoPA, ends with a risk map and report, and can be exported as PDF and JSON. | The risk judgement. |
| Transfers abroad. Transfer to countries with adequate protection, or in the cases the law lists for other countries, such as contracts with equivalent protection or the person’s express consent. | Art. 22, 23 | Transfers are recorded in each activity, appear in the privacy notice built from it, and GovernID recommends a DPIA when data is sent abroad. | Choosing the transfer route and signing it. |
| Sensitive data. Data on health, biometrics, genetics, beliefs, criminal records and similar categories needs extra care, often a DPIA and a DPO. | Art. 1, 10, 21 | Sensitive fields are marked in the RoPA and at collection, and GovernID recommends a DPIA for activities that use them. | Choosing the safeguards. |
| Storage limitation. Keep data no longer than its purpose needs; after that, delete it or make it anonymous. | Art. 5 | Retention periods are set in the RoPA. Each record gets its own end date, records past it can be listed at any time, and GovernID’s own copy is marked for destruction when its period ends. | Deleting the data in your own systems. |
This page summarises the law to show where GovernID supports your work. It is not legal advice; your legal counsel decides how the law applies to your company.
Right of access: what a response must include
Under Article 13 of Federal Decree-Law No. 45 of 2021, the data subject may request the following information free of charge.
| The response must include | Article |
|---|---|
| Types of personal data processed | Art. 13(1)(a) |
| Purposes of processing | Art. 13(1)(b) |
| Decisions made on automated processing, including profiling | Art. 13(1)(c) |
| Sectors or establishments the data is shared with, inside and outside the State | Art. 13(1)(d) |
| Controls and criteria for the retention period | Art. 13(1)(e) |
| Procedures for rectification, erasure, restriction and objection | Art. 13(1)(f) |
| Protection measures for cross-border processing | Art. 13(1)(g) |
| Actions to be taken in case of a breach | Art. 13(1)(h) |
| How to file a complaint with the Data Office | Art. 13(1)(i) |
Deadline: not yet set; it awaits the Executive Regulations. Fee: free.
What GovernID does: Every record collected through GovernID is stored with its purpose, legal basis, the notice version shown, consent scope, retention end date and collection point. These are the answers an access response has to give. In the Privacy Center, the individual sees their records instantly as a preliminary report and can export it, and your team finds a person's records across every GovernID collection point with PII Search.
What stays with you: Data held in systems outside GovernID and a copy of it, the formal response letter, identity checks beyond the verified e-mail, redaction of third-party data, and tracking the deadline.
Rectification, erasure and objection are separate rights and are handled separately; this section covers access only.
Frequently asked questions
Does the PDPL apply in the DIFC and ADGM?
No. Free zones with their own data protection laws are outside its scope (Art. 2). Companies there follow their free zone law.
Is consent always required?
No. Art. 4 lists cases where processing is allowed without consent, such as performing a contract, a legal obligation or protecting public health.
In which languages can notices be produced?
GovernID generates privacy notices in 9 languages, including Arabic and English.
Where is our data hosted?
GovernID hosts each company’s data in the country where it is registered.
Is this page legal advice?
No. It summarises the law to show where GovernID supports your work. Your legal counsel decides how it applies to your company.
The law and its regulations: official sources
Links go to the issuing authority's own website. Some government sites restrict access from outside their country.