Security & Compliance4 min read
PDPL compliance checklist for your website
A ten-item checklist for bringing a UAE website into line with Federal Decree-Law No. 45 of 2021: which regime actually applies to your entity, consent you can prove, cross-border transfers, and the three fixes worth doing this week.
Danial AhmedFounder & engineering manager
On this page
The UAE's Personal Data Protection Law — Federal Decree-Law No. 45 of 2021 — has been in force since January 2022, and its executive regulations have taken considerably longer to arrive than anyone planned. That is not a reason to wait. Almost everything the law asks of a public website is achievable in a fortnight of engineering work, and most of it overlaps with what a competent build does anyway. This checklist covers the website surface specifically; the wider programme belongs with counsel. It is the list we work through on a custom software build.
First, check whether the federal law is even the one that applies to you
The PDPL is federal law, but it is not the only data protection regime in the country, and getting this wrong invalidates the rest of the exercise.
- DIFC entities follow DIFC Data Protection Law No. 5 of 2020, with its own regulator and its own breach timelines.
- ADGM entities follow the ADGM Data Protection Regulations 2021.
- Health data generated in the UAE falls under Federal Law No. 2 of 2019 on the use of ICT in healthcare, which carries a storage-location requirement that the PDPL does not — health data generated in the country must generally stay in it, absent an authority exemption.
- Banking and credit data sit under Central Bank instruments rather than the PDPL.
A Dubai mainland trading company runs on the PDPL. A DIFC fund administrator does not. A clinic in Jumeirah has a residency constraint before it has a consent question.
The ten-item website checklist
Work through these in order. Items one to four are where nearly every UAE site fails an audit.
- Inventory every input. Contact forms, newsletter, careers uploads, chat widget, booking calendar, WhatsApp click-to-chat, and every analytics or advertising tag. Each is a processing activity, and you cannot document what you have not listed.
- Assign a lawful basis per activity. Consent is one basis among several — contractual necessity, legal obligation, and the controller's legitimate interest also appear in the law. Marketing email needs consent; sending a quotation someone requested does not.
- Make consent provable. Unticked by default, granular per purpose, separable from the terms checkbox, withdrawable by the same effort it took to give, and logged with a timestamp and the version of the notice that was shown. A consent you cannot evidence is a consent you do not have.
- Write a privacy notice that names things. The legal entity, the categories of data, purposes, legal basis, retention periods, recipients and sub-processors, cross-border destinations, the rights available, and a working contact route. A generic template naming a US state law is worse than no notice at all.
- Gate non-essential tags. The PDPL has no separate cookie article, but analytics and advertising identifiers routinely constitute personal data. Practically: no non-essential tag fires before a choice is made, "reject" is as easy as "accept", and the tag manager enforces it rather than the banner pretending to.
- Publish a retention schedule and implement it. Form submissions kept "forever" in a shared inbox is the single most common finding. Give each store a period and a deletion job.
- Build a real data-subject-request route. Access, rectification, erasure, restriction, portability and objection all need a path that a non-engineer can execute, with a target of one month.
- Have a breach procedure. Detection, an internal owner, a written assessment, notification to the UAE Data Office without undue delay, and notification to affected individuals where the risk warrants it. Rehearse it once; an unrehearsed plan is a document.
- Sign processor agreements. Your hosting provider, CRM, email sender, analytics vendor and CMS host are processors. Each needs a data processing agreement and a named location.
- Do the security basics and record them. TLS everywhere, encryption at rest, least-privilege access, audit logging, tested backups, and dependency patching on a schedule.
Cross-border transfer, in plain terms
Hosting outside the UAE is not prohibited. Transfers are permitted where the destination provides adequate protection as determined by the UAE Data Office, and otherwise under contractual safeguards, binding corporate rules, explicit consent, or necessity for a contract with the data subject.
What this means for a website: know where your data physically sits. A Dubai company running a European CMS host, a US email provider and a Singapore CDN has three transfers to document. Documenting them takes an afternoon. Discovering them during a procurement review takes a deal.
Penalties, and why we will not print a number
Administrative penalties under the PDPL are set out in executive regulations rather than in the decree-law itself, and figures circulating in marketing content are frequently quoted from unrelated instruments. Verify the current position with the UAE Data Office or counsel before you put a number in a board paper.
The commercially relevant exposure is usually elsewhere: enterprise and government-adjacent procurement in the UAE treats a data protection questionnaire as a gate. Failing it costs you the tender long before a regulator gets involved.
What to fix this week
Three items give most of the compliance improvement for a day of work: block non-essential tags until consent, add a per-purpose consent log to your forms, and rewrite the privacy notice so it names your actual sub-processors. Then schedule the retention deletions. Everything after that is programme work — and if you are also handling payments, the controls overlap heavily with what UAE payment gateways require of an integrator.