Almost every Gulf business that also deals with Europe eventually asks the same thing: "We've done GDPR. Are we covered for the UAE?"

The short answer is: mostly, but not quite, and the gaps are in places people don't tend to look. This PDPL vs GDPR guide is written for the person who has to deal with both, and it focuses on what you'd really need to change.

Do both apply to you?

Quite possibly. Picture a Dubai e-commerce company shipping to customers in Germany and the UAE. Its German customers fall under the GDPR, because the business targets people in the EU. Its UAE customers and staff fall under the PDPL. Same website, same CRM, two laws.

Add a DIFC holding company, and you have a third law. Companies registered in DIFC or ADGM follow their own data protection regimes instead of the PDPL. I've covered those in why DIFC companies need DIFC compliance and why ADGM companies need ADGM compliance.

UAE PDPL vs GDPR at a glance

Area EU GDPR UAE PDPL
Where it applies EU establishments, and organisations elsewhere that target or monitor people in the EU Personal data of people in the UAE, and controllers and processors in the UAE, excluding DIFC and ADGM
Regulator National data protection authorities UAE Data Office, being consolidated into the new Federal Authority for AI and Data
Legal basis Six, including legitimate interests Consent by default, with listed exceptions
Breach reporting To the regulator within 72 hours where there is risk to individuals To the regulator as soon as you become aware
Data Protection Officer Public bodies, large-scale monitoring, large-scale special category data Comparable high-risk situations
Maximum penalties Up to €20 million or 4% of worldwide turnover To be set by Cabinet decision
Detailed rules Regulation plus extensive guidance and case law Executive Regulations still unpublished in November 2026

The four differences that really change your work

Stack of compliance folders, representing PDPL and GDPR records

1. You can't lean on legitimate interests

This is the one that catches GDPR teams out. Under the GDPR, a lot of everyday processing, such as fraud checks or some marketing, may rest on legitimate interests. The PDPL has no general equivalent. Consent is the default, with specific exceptions, such as performing a contract or meeting a legal duty.

So take your GDPR record of processing and look at every line that says "legitimate interests". For each one, ask what your UAE basis would be. This one exercise tends to uncover most of the work.

2. Your breach clock is different

GDPR teams build their process around 72 hours. The PDPL asks you to notify the regulator as soon as you become aware of a breach affecting personal data, and to tell affected individuals where their rights are at risk. If your playbook assumes you have three days, change it. I'd build to the tighter expectation for both.

3. The enforcement picture is still forming

The GDPR has years of fines and court decisions behind it. The PDPL's Executive Regulations and administrative penalties hadn't been published as of November 2026. That can tempt people to relax. I'd read it another way: when the rules arrive, you'll have six months, and your GDPR work gives you a head start that others won't have.

4. Local rules sit around the PDPL

Some data is covered by its own UAE legislation, such as certain health and banking data. Health data, for example, generally has to stay in the UAE. A GDPR programme won't flag that. If your data moves between the Gulf and Europe, our article on cross-border data transfers in MENA goes deeper.

What carries over from GDPR?

Plenty, and that's the good news. If your GDPR programme is real, you can reuse most of it:

  • Your record of processing and data maps.

  • Privacy notices, with UAE-specific adjustments.

  • Your process for data subject requests.

  • Data protection impact assessments.

  • Security controls and vendor contracts.

  • Your incident response structure, with the timing changed.

How to close the gap

  1. Confirm which law applies to which entity. Include any DIFC or ADGM companies.

  2. Go through your legal bases, starting with legitimate interests.

  3. Update consent wording for UAE customers, and make it as easy to withdraw as to give.

  4. Change the breach playbook to reflect the PDPL's timing and regulator.

  5. Review transfers from the UAE to Europe and elsewhere, as well as the other way round.

  6. Watch for the Executive Regulations, and revisit your gap list when they're published.

Design for the stricter rule in each area, and run one programme. Two parallel projects usually mean two sets of documents nobody keeps up to date.

We help companies with GDPR compliance and UAE PDPL compliance, including data protection compliance in Dubai. This article is general guidance, not legal advice, so involve your legal adviser for specific decisions.

Comparing providers? See the Top 10 Data Protection (PDPL) Consultants in the UAE.

Talk to our data protection team or contact us.

Frequently asked questions

What is the main difference between the UAE PDPL and GDPR?

The biggest practical difference is the legal basis. The GDPR offers six lawful bases, including legitimate interests, while the UAE PDPL relies mainly on consent, with listed exceptions.

If we comply with GDPR, are we compliant with the UAE PDPL?

Not automatically. You can reuse much of the work, but you need to check legal bases, consent, breach timing, regulators and UAE-specific rules such as those for health data.

How quickly must a breach be reported under each law?

The GDPR requires notification to the regulator within 72 hours where there is a risk to individuals. The PDPL asks you to notify the regulator as soon as you become aware of a breach affecting personal data.

What are the penalties under the PDPL compared with GDPR?

GDPR fines can reach €20 million or 4% of worldwide annual turnover. PDPL administrative penalties are left to a Cabinet decision, which hadn't been published as of November 2026.

Does the PDPL apply in DIFC and ADGM?

No. Companies registered in DIFC and ADGM follow their own data protection regimes. Groups with entities onshore and in those free zones may have to meet more than one law.