If you collect personal data through a website, mobile app, CRM, or any digital service in the UAE, you are governed by one of the most significant legal reforms in the country’s recent history: the UAE Personal Data Protection Law (PDPL), introduced as Federal Decree-Law No. 45 of 2021. Alongside it sits a network of related laws that together define how UAE businesses must collect, store, transfer, and protect personal information.
This guide explains how the PDPL works, what it requires from businesses, how it interacts with the DIFC, ADGM, and sector-specific regimes, and what you practically need to do to stay compliant. It is written for UAE business owners, managers, developers, and marketers who need a clear operational picture, not a legal treatise. For binding legal advice, consult a qualified UAE lawyer.
The UAE does not have a single unified data protection regime. Different rules apply depending on where your business is registered and what type of data you process. Before you assess your obligations, identify which regime (or combination of regimes) governs your operations.
| Jurisdiction | Governing Law | Who It Applies To |
|---|---|---|
| Onshore UAE (Mainland and most free zones) | Federal Decree-Law No. 45 of 2021 (PDPL) | Mainland companies and most free zone companies outside DIFC and ADGM |
| DIFC | DIFC Law No. 5 of 2020 (DIFC Data Protection Law) | Entities registered in the Dubai International Financial Centre |
| ADGM | ADGM Data Protection Regulations 2021 | Entities registered in the Abu Dhabi Global Market |
| Dubai Healthcare City (DHCC) | DHCC Data Protection Regulations | Healthcare entities registered in DHCC |
| Sector-specific | Health, banking, credit, telecom laws | Businesses in regulated sectors (additional rules on top of general regime) |
The DIFC and ADGM have their own comprehensive data protection laws modelled closely on the EU GDPR, overseen by their own regulators. If your company is incorporated in those free zones, the onshore PDPL does not generally apply to you, but the principles are broadly similar. The rest of this guide focuses primarily on the onshore PDPL, with references to the other regimes where relevant.
Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data is the UAE’s first comprehensive federal data protection law. Key facts:
| Item | Detail |
|---|---|
| Full title | Federal Decree-Law No. 45 of 2021 Concerning the Protection of Personal Data |
| Issued | September 2021 |
| Effective date | 2 January 2022 |
| Regulator | UAE Data Office (established by Federal Decree-Law No. 44 of 2021) |
| Modelled on | International best practices, with many similarities to the EU GDPR |
| Territorial reach | Onshore UAE, extraterritorial application for processing of UAE residents’ data |
The PDPL is a framework law. Many of its provisions, including exact notification timelines, specific penalty amounts, and detailed procedural rules, are meant to be set out in Executive Regulations to be issued by the UAE Cabinet on the proposal of the UAE Data Office.
The PDPL provides that Executive Regulations should be issued within six months of the law’s publication. At the time of writing this guide, the Executive Regulations have not yet been published. Once they are issued, organisations have a further six months (extendable by the Cabinet) to bring their operations into full compliance.
The PDPL applies broadly, with an extraterritorial reach similar to the GDPR. It covers:
In practical terms: if your website collects names, emails, phone numbers, or payment details from users in the UAE, the PDPL likely applies to you, even if your servers or headquarters are abroad.
The PDPL does not apply to several important categories. Your organisation may fall partially or entirely outside its scope if you operate in one of these areas, though sector-specific rules will typically still govern you.
The PDPL uses terminology that will be familiar to anyone who has worked with GDPR, but the specific UAE definitions matter. These are the core building blocks.
Any data relating to an identified or identifiable natural person. That includes names, identification numbers, email addresses, phone numbers, voice recordings, photos, electronic identifiers, location data, and physical, physiological, cultural, or social characteristics. IP addresses and cookie identifiers also qualify when they can be linked to an individual.
A special category of personal data requiring heightened protection. This includes data relating to ethnic or racial origin, political or philosophical views, religious beliefs, criminal records, biometric data, genetic data, and health data. Processing sensitive personal data triggers additional safeguards and is a trigger for mandatory DPO appointment when done at scale.
The natural person whose personal data is being processed. Your customers, employees, website visitors, and newsletter subscribers are all data subjects.
The entity that determines the purposes and means of processing personal data. If you decide what data to collect from your customers and why, you are a controller. Most businesses are controllers with respect to their own customer and employee data.
An entity that processes personal data on behalf of a controller. Cloud hosting providers, payment processors, CRM platforms, and marketing automation tools typically act as processors when they handle your customer data on your instructions.
The PDPL requires a lawful basis for every processing activity. Consent is the most visible legal basis, but it is not the only one. The law recognises several grounds for processing personal data without consent.
When you rely on consent, the PDPL sets strict conditions. Consent must be specific, given through a clear affirmative action, and the data subject must be informed how to withdraw it. Implied consent through silence, pre-ticked boxes, or bundled acceptance of terms is not valid.
The PDPL gives data subjects a suite of rights that businesses must be prepared to handle. Your internal processes need mechanisms to receive, verify, and respond to these requests.
These rights are subject to certain exceptions under the PDPL, and the balance differs slightly from the GDPR. Practically, your privacy policy and support processes must describe how data subjects exercise these rights and what to expect in response.
The PDPL imposes several concrete obligations on controllers and processors. These form the operational backbone of any compliance programme.
Both controllers and processors must keep a written record of their processing activities. This record typically includes the purposes of processing, categories of data subjects and data, recipients of data, retention periods, and the technical and organisational security measures in place. A ROPA is the evidence you produce if the UAE Data Office asks how you comply with the law.
Under Article 10 of the PDPL, a DPO must be appointed in three circumstances:
The DPO can be an employee or an external service provider, and does not have to be located in the UAE. Their contact details must be shared with the UAE Data Office.
Under Article 21, controllers must perform a DPIA before starting any processing that is likely to result in a high risk to data subjects. Triggers commonly include systematic and extensive evaluation of individuals through automated processing or profiling, large-scale processing of sensitive data, and large-scale systematic monitoring.
Under Article 9, controllers must notify the UAE Data Office of any personal data breach that would prejudice the privacy, confidentiality, or security of a data subject’s data. Notifications must include a description of the nature, form, and causes of the breach, approximate numbers affected, DPO contact details, likely consequences, and measures taken to mitigate. The exact timeline for notifications will be set by the Executive Regulations. If the breach poses a high risk, the affected data subjects must also be notified directly. Processors must notify controllers without delay when they become aware of a breach.
Controllers and processors must implement measures appropriate to the risk, including encryption, access controls, authentication, backups, secure deletion, and staff training. The PDPL does not prescribe specific technologies, but it does require that the measures be appropriate to the sensitivity of the data and the nature of the processing.
When you use processors, the relationship must be governed by a written contract that binds the processor to comply with the PDPL, implement appropriate security measures, assist you with data subject requests, and return or delete data at the end of the engagement. Generic terms and conditions are usually not enough.
Few parts of the PDPL matter more in practice than the rules on transferring personal data outside the UAE. Articles 22 and 23 regulate international transfers, and they directly shape your hosting and cloud decisions.
Personal data may be freely transferred to a country that has adequate data protection legislation, similar to the EU “adequacy decision” model. The UAE Data Office is responsible for determining which countries qualify. The official list has not yet been published.
In the absence of adequacy, transfers are still permitted under specific conditions. These include:
In practice, this means that if you use cloud services or hosting providers outside the UAE, you are carrying out international data transfers that need a legal mechanism under Article 22 or 23. The paperwork and risk profile are meaningfully higher than keeping data in-country.
The PDPL itself does not set specific penalty amounts. Instead, administrative penalties will be issued by a Council of Ministers decision on the proposal of the UAE Data Office, with specifics defined in the Executive Regulations. Until those are published, enforcement operates through guidance, complaints handling, and the expectation that organisations will align with PDPL principles.
Data subjects have the right to file complaints directly with the UAE Data Office if they believe the PDPL has been violated. Once the enforcement framework is fully operational, administrative fines are expected to apply alongside obligations to suspend or restrict non-compliant processing.
Outside the PDPL, other laws can impose criminal and financial penalties for data-related misconduct. Notably, Federal Decree-Law No. 34 of 2021 on Combating Rumors and Cybercrimes criminalises unauthorised access to and disclosure of personal data, with fines that can reach hundreds of thousands of dirhams and custodial sentences for serious cases.
Established under Federal Decree-Law No. 44 of 2021, the UAE Data Office is the national regulator responsible for data protection. It sits within the Ministry of Cabinet Affairs and its functions include:
If your business is registered in one of the UAE’s major financial free zones, different rules apply. These regimes are mature, fully enforceable today, and overseen by their own specialist regulators.
Applies to entities registered in the Dubai International Financial Centre. Modelled closely on the GDPR, it is enforced by the DIFC Commissioner of Data Protection. DPOs are mandatory for DIFC Bodies and for controllers or processors carrying out high-risk processing on a systematic or regular basis.
Applies to entities registered in the Abu Dhabi Global Market. Also modelled on GDPR, with its own Commissioner of Data Protection. A DPO is required when processing is carried out by a public authority, when core activities require regular and systematic monitoring of data subjects on a large scale, or when core activities involve large-scale processing of sensitive data.
Applies to healthcare entities in Dubai Healthcare City, with a particular focus on patient data.
The PDPL does not exist in isolation. Several other UAE laws contain privacy-related provisions that may apply to your business depending on sector, activity, and data type.
Also effective from 2 January 2022, this law replaced the older Federal Law No. 5 of 2012 on Combating Cybercrimes. It criminalises a broad range of online offences, including unauthorised access to information systems, data theft, identity fraud, hacking, phishing, and unlawful disclosure of personal data. Penalties can reach hundreds of thousands of dirhams in fines and custodial sentences for serious violations.
Safeguards consumer rights, including the confidentiality of personal information. It prohibits businesses from using customer data for marketing or promotional purposes without proper consent.
Regulates the use of information and communication technology in healthcare, including how digital health records must be handled, stored, and protected. Health data is excluded from the PDPL and governed by this law instead, along with sector regulations issued by UAE health authorities.
Governs how credit information is collected, stored, and protected. Banking and credit data are excluded from the PDPL and fall under this law and UAE Central Bank regulations.
Effective from 2 January 2022, this law repealed the older Federal Law No. 1 of 2006 on Electronic Commerce. It regulates electronic documents, electronic signatures, electronic seals, and trust service providers. The accompanying Executive Regulations were issued through Cabinet Resolution No. 28 of 2023. This law matters if your business issues, receives, or relies on digital signatures and electronic contracts.
As amended, this law and its implementing regulations issued by TDRA set rules for telecommunications providers, including obligations relating to user data confidentiality and content regulation.
Regulates the dissemination and exchange of data within the Emirate of Dubai. Its primary focus is on government-related data and the distinction between “open data” and “shared data” in the context of Dubai’s smart city initiatives. It is not a personal data protection law in the PDPL sense, but it interacts with data held by businesses that supply services to Dubai government entities.
Guarantees the confidentiality of personal communications through post, telegraph, or other means of communication. This constitutional right underpins the specific data protection statutes and reinforces the general privacy framework.
PDPL compliance is not only a policy and paperwork exercise. The infrastructure that stores and processes your data is part of the compliance picture, and the choices you make here carry real legal weight.
Hosting customer data in UAE-based data centres means there is no international transfer to justify under Articles 22 or 23. This removes an entire category of compliance paperwork and risk, particularly valuable while adequacy decisions from the UAE Data Office remain pending.
If your hosting provider operates the servers on which your customer database lives, they are processing personal data on your behalf. Under the PDPL, this makes them a data processor. You need a written agreement covering confidentiality, security measures, sub-processors, incident notification, and data return or deletion at the end of the engagement. Reputable UAE providers are familiar with these requirements.
Encryption at rest and in transit, access controls, tested backups, logging, and segregation of environments are expected of any modern provider. Certifications such as ISO 27001 and PCI-DSS at the data centre and provider level are not required by the PDPL, but they help you demonstrate the “appropriate measures” the law requires.
UAE-registered businesses typically need VAT-compliant invoices. Local providers issue AED-denominated invoices with proper UAE VAT treatment, which simplifies both accounting and regulatory relationships. International providers often cannot.
When a security incident affects personal data, you need fast, coordinated response to meet your Article 9 notification obligations. A local provider operating in your time zone with Arabic and English support cuts response time significantly compared with overseas-only support.
UAE businesses that work with European customers often need to comply with both the GDPR and the PDPL. The two regimes are broadly aligned, but there are differences worth knowing.
| Area | UAE PDPL | EU GDPR |
|---|---|---|
| Lawful bases | Consent default, with statutory exceptions | Six bases, including legitimate interests as a general ground |
| Legitimate interests | Not a general standalone basis | Explicit ground (Article 6(1)(f)) |
| Data subject rights | Access, rectification, erasure, portability, objection, restrict processing | Broadly similar rights, with some nuances |
| DPO requirement | Mandatory for high-risk or large-scale sensitive data processing | Mandatory for public authorities, large-scale monitoring, and large-scale sensitive data |
| Breach notification | Required. Timeline set by Executive Regulations | 72 hours to supervisory authority |
| International transfers | Adequacy (list pending) or equivalent safeguards | Adequacy decisions, SCCs, BCRs, derogations |
| Penalties | Set in Executive Regulations (pending); Cybercrime Law imposes criminal penalties separately | Up to 4% of global annual turnover or EUR 20 million |
| Regulator | UAE Data Office | National Data Protection Authorities |
If you already run a GDPR-compliant programme, most of the work is reusable for the PDPL. You will mainly need to update territorial scope assessments, add UAE-specific notices, document your PDPL lawful bases separately, and review your international transfer arrangements for data moving in and out of the UAE.
This checklist translates the PDPL requirements into concrete actions. It does not replace legal advice, but it gives you a practical starting point.
If your business processes personal data of UAE residents (customer names, emails, phone numbers, payment details), the PDPL generally applies, regardless of company size. The Executive Regulations may introduce simplified requirements for SMEs, but the core obligations such as lawful basis, security measures, data subject rights, and breach handling apply broadly. Check whether you are instead subject to DIFC, ADGM, or DHCC rules based on where your entity is registered.
The PDPL has extraterritorial reach. If you process personal data of data subjects inside the UAE, you are covered even if your company and infrastructure are abroad. Foreign businesses serving UAE customers should treat the PDPL in the same way as the GDPR: review scope, update notices, document lawful bases, and put transfer safeguards in place.
Under Article 10 of the PDPL, a DPO is required when processing is high-risk due to new or data-size-based technologies, involves systematic and comprehensive assessment of sensitive personal data (including profiling and automated processing), or involves large-scale processing of sensitive personal data. Many SMEs will not hit these triggers, but if you handle health data, biometric data, or large volumes of consumer profiles, the answer is likely yes. The DPO can be an external service provider.
Yes, but with added compliance work. If those services store data in regions outside the UAE, you are carrying out international data transfers under Articles 22 or 23 and need a legal basis for each transfer (typically a data processing agreement with appropriate safeguards). Hosting customer data in UAE-based data centres, whether with those providers’ UAE regions or with a local provider, removes this complexity.
The PDPL itself does not set specific penalty amounts. These will be defined in the Executive Regulations, which have not yet been published at the time of writing. Separately, the Cybercrime Law (Federal Decree-Law No. 34 of 2021) already imposes meaningful penalties for misuse of personal data, including fines and custodial sentences. Reputational and commercial consequences of a breach are often greater than the statutory fines.
Marketing typically relies on consent as the lawful basis. Consent must be specific (for marketing, not buried in general terms), informed, unambiguous, and easy to withdraw. Pre-ticked boxes, bundled consents, and silence do not qualify. The Consumer Protection Law (Federal Law No. 15 of 2020) reinforces these rules for consumer-facing businesses.
Contain the incident immediately, assess the scope and affected data, and document everything. Under Article 9, you must notify the UAE Data Office if the breach would prejudice the privacy, confidentiality, or security of personal data. If the breach poses a high risk to data subjects, you must also notify them directly. The exact notification timeline is to be set by the Executive Regulations. Have a written incident response plan ready before you need it.
The UAE does not have a dedicated e-privacy or cookies law equivalent to the EU’s ePrivacy Directive. However, cookies that collect personal data fall within the PDPL, which means you need a lawful basis for their use and must provide transparency. In practice, UAE businesses targeting international audiences often apply GDPR-style cookie consent banners that satisfy both regimes.
The Federal Decree-Law No. 45 of 2021 is published on the UAE official legislation portal. The UAE Data Office and the UAE government portal (u.ae) publish guidance and updates. For binding interpretation, consult a UAE-qualified legal professional.