← Insights

Drafting Effective Data Protection Clauses in UAE Commercial Contracts

A template-driven method ensures PDPL-compliant privacy, data-transfer and breach-notification provisions in UAE commercial contracts.

This article outlines the essential components of a PDPL-compliant data-protection clause, covering controller-processor roles, security measures, sub-processor controls, data-return obligations and cross-border transfer rules under Articles 22-23. It explains how to embed breach-notification requirements that meet the 72-hour notice standard and provides a practical template approach for service and supply agreements in Dubai and the wider UAE.

Reviewed by Mohamed Noureldin, Founder, Managing Partner & Senior Legal Consultant

Standfirst: Practical guidance on embedding PDPL-compliant privacy, data-transfer and breach-notification provisions into service and supply agreements under UAE law.

Summary: This article explains how to draft data-protection clauses that satisfy the UAE Personal Data Protection Law (PDPL), align with cross-border transfer rules and meet breach-notification obligations, using a template-driven approach suitable for commercial contracts in Dubai and the wider UAE.

Related Services: Explore our Data Protection Officer Service and Data Regulation & Compliance services for practical legal support in this area.

WHAT ARE THE ESSENTIAL ELEMENTS OF A PDPL-COMPLIANT DATA-PROTECTION CLAUSE IN A UAE COMMERCIAL CONTRACT?

A PDPL-compliant data-protection clause must identify the parties as controller and processor, limit processing to documented instructions, require appropriate security measures, mandate sub-processor approval, impose prompt breach notification to the controller, oblige assistance with data-subject requests, provide for deletion or return of data upon termination, and restrict cross-border transfers to the exceptions set out in PDPL Articles 22-23. These requirements stem directly from Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (PDPL) and apply to any contract where personal data is processed in the UAE mainland, unless the parties are governed by DIFC or ADGM data-protection regimes.

The clause should begin with a clear definition of "personal data" and "processing" as defined in Article 1 of the PDPL, then state that the processor shall act only on the controller's documented instructions (Article 7). It must oblige the processor to implement technical and organisational measures equivalent to ISO 27001 or SOC 2 standards, to conduct regular security testing, and to notify the controller of any actual or suspected breach without undue delay and, in any event, within seventy-two hours of becoming aware (Article 9). The processor must obtain the controller's prior written consent before engaging any sub-processor and must flow-down the same obligations to such sub-processors (Article 8). Upon termination, the processor must delete or return all personal data and certify such deletion (Article 7). Finally, the clause must incorporate the cross-border transfer gate-keeping of Articles 22-23: transfers are permissible only to countries on the Data Office adequacy list, with the data subject's explicit consent, where necessary for contract performance, or under the other statutory exceptions, and health-data transfers are prohibited unless authorised under Federal Law No. 2 of 2019 on ICT in Health.

HOW SHOULD A CONTRACT ADDRESS CROSS-BORDER DATA TRANSFERS UNDER THE PDPL?

Cross-border transfers of personal data from the UAE mainland are governed by PDPL Articles 22-23, which set out a limited set of lawful mechanisms. A contract must first determine whether the recipient country appears on the Data Office's adequacy list; as of the date of drafting, no adequacy decisions have been published, so reliance on adequacy alone is not currently available. If adequacy cannot be relied upon, the contract must secure one of the other lawful bases: the data subject's explicit, informed consent (Article 23(1)); the transfer being necessary for the performance of a contract to which the data subject is a party (Article 23(2)); the transfer being necessary for the establishment, exercise or defence of legal claims (Article 23(3)); or the transfer being required to protect vital interests of the data subject or another person (Article 23(4)). The contract should record the chosen basis, retain evidence of consent or contractual necessity, and, where health data is involved, expressly prohibit transfer unless authorised under Federal Law No. 2 of 2019, which mandates localisation of health-sector data within the UAE.

For DIFC- or ADGM-based entities, the transfer rules of the DIFC Data Protection Law 5/2020 or the ADGM Data Protection Regulations 2021 apply instead, and the contract must reference the appropriate regime. The clause should also oblige the processor to maintain a record of all transfers undertaken, to make such records available to the controller upon request, and to cooperate with any investigation by the UAE Data Office or the relevant free-zone regulator.

WHAT BREACH-NOTIFICATION OBLIGATIONS MUST BE INCLUDED IN A UAE COMMERCIAL CONTRACT?

Under PDPL Article 9, a processor that becomes aware of a personal-data breach must notify the controller without undue delay and, where feasible, not later than seventy-two hours after becoming aware of the breach. The notification must describe the nature of the breach, the categories and approximate number of data subjects affected, the categories and approximate number of personal-data records concerned, the likely consequences of the breach, and the measures taken or proposed to address the breach, including any mitigation steps. The contract should therefore require the processor to: (1) implement an internal breach-detection procedure; (2) notify the controller in writing (or via a secure electronic channel) within the seventy-two-hour window; (3) provide a preliminary breach report containing the details listed above; (4) cooperate with the controller in fulfilling any notification obligations the controller may have to the UAE Data Office or to affected data subjects; and (5) maintain a breach-log for at least five years, making it available to the controller and, if required, to the regulator.

If the controller requires notification to the Data Office under Article 9(2), the contract obliges the processor to provide support in preparing the regulator's notification, including providing logs, forensic reports, and remedial action plans. The parties may also agree on liquidated damages or specific performance remedies for failure to meet the notification timeline, provided such remedies are not punitive and are proportionate to the anticipated loss.

HOW CAN A TEMPLATE-DRIVEN APPROACH SIMPLIFY THE INCLUSION OF PDPL CLAUSES IN SERVICE AND SUPPLY AGREEMENTS?

A template-driven approach requires a master data-protection clause that prescribes the mandatory PDPL obligations for controller-processor relationships, security standards, sub-processor controls, breach-notification timelines, data-subject-rights support, deletion or return of data, and cross-border transfer gate-keeping. This master clause is then inserted into the relevant schedule or annex of each service or supply agreement, with project-specific variables (such as the description of processing activities, the categories of personal data, the retention period, and the chosen transfer mechanism) completed via a short questionnaire or data-sheet.

The template should include placeholders for:

  • Controller and Processor details - legal names, trade licence numbers, and registered addresses.
  • Scope of Processing - a brief description of the services, the types of personal data (e.g., customer contact details, transaction records, health information), and the legal basis for processing.
  • Security Measures - reference to the applicable standard (ISO 27001, SOC 2, or equivalent) and any sector-specific requirements (e.g., Central Bank outsourcing rules for banks).
  • Sub-processor List - an attached schedule that is updated whenever a new sub-processor is engaged, with the controller's prior written consent.
  • Breach-Notification Procedure - the seventy-two-hour notice period, required contents of the notice, and cooperation obligations.
  • Data-Subject Rights Support - timelines for responding to access, rectification, erasure, portability, and restriction requests (Articles 13-18).
  • Transfer Mechanism - the selected basis under Articles 22-23, including adequacy-list reference, consent copy, or contract-necessity justification, and a statement that health-data transfers are prohibited unless authorised.
  • Deletion or Return - the format and timing for data return or certified deletion upon contract expiry or termination.

By completing the questionnaire for each new agreement, the contracting parties ensure that all PDPL-mandatory elements are present while allowing customization to the specific processing context. The template also facilitates internal audits: the legal or compliance team can verify that every active contract contains the master clause with accurately filled-in fields, reducing the risk of non-compliance and the associated penalties under PDPL Article 41 (administrative fines up to AED 5 million).

FREQUENTLY ASKED QUESTIONS

What is the legal basis for requiring a data-processing agreement under the PDPL?
Federal Decree-Law No. 45 of 2021 (PDPL) Article 7 obliges a processor to process personal data only on the documented instructions of the controller, and Article 8 requires that any engagement of a sub-processor be subject to the controller's prior written consent. These provisions require a written data-processing agreement that sets out the instructions, security obligations, sub-processor controls, breach-notification duties, and data-subject-rights support. The Arabic text of UAE legislation as published in the Official Gazette prevails over any translation.

How soon must a processor notify a controller of a data breach under UAE law?
PDPL Article 9 requires the processor to notify the controller "without undue delay" and, where feasible, not later than seventy-two hours after becoming aware of the breach. The notice must contain the details prescribed in the article, including the nature of the breach, categories of data subjects and records affected, likely consequences, and remedial measures taken.

Can personal data be transferred outside the UAE if the recipient country is not on the adequacy list?
Yes, provided one of the exceptions in PDPL Articles 22-23 applies: explicit consent of the data subject, necessity for the performance of a contract with the data subject, necessity for legal claims, or protection of vital interests. Health-data transfers are additionally restricted by Federal Law No. 2 of 2019 on ICT in Health, which generally prohibits such transfers unless authorised.

What security standards are acceptable for PDPL compliance in the UAE?
The PDPL does not prescribe a specific standard but requires "appropriate technical and organisational measures" (Article 9). In practice, controllers and processors commonly adopt internationally recognised frameworks such as ISO 27001, SOC 2, or NIST CSF, and the contract should reference the chosen standard and any sector-specific obligations (e.g., Central Bank outsourcing rules for banks, Dubai Data Law 26/2015 for government data).

What happens to personal data at the end of a service contract under the PDPL?
PDPL Article 7 obliges the processor to, upon termination of the contract, delete or return all personal data to the controller and to provide a certification of such deletion. The contract should specify the format for data return (e.g., machine-readable CSV or JSON), the timeline (typically within thirty days of termination), and the procedure for certification (e.g., an auditor's report or a sworn statement).

Are DIFC and ADGM entities subject to the UAE PDPL?
No. DIFC and ADGM are separate common-law jurisdictions with their own data-protection regimes: the DIFC Data Protection Law 5/2020 and the ADGM Data Protection Regulations 2021. Contracts involving entities incorporated in those free zones must comply with the applicable free-zone law rather than the federal PDPL, unless the parties expressly agree to apply the PDPL by choice of law, which is permissible only where the free-zone law does not conflict with mandatory provisions.

End of article

If your matter involves data protection clauses in the United Arab Emirates, you are welcome to request a consultation with Nour Attorneys. Our team can assess your position under the law currently in force and outline the options available to you. Request a consultation

This article is provided for general informational purposes only and does not constitute legal advice. Reading this article or contacting Nour Attorneys through this website does not create an attorney-client relationship; such a relationship arises only after a conflicts-of-interest check and a signed engagement agreement. Do not send confidential information through this website; information submitted before engagement is not protected by legal privilege. Past results do not guarantee future outcomes. The firm's lawyers practice in the jurisdictions stated in their individual profiles; this article addresses the law of the United Arab Emirates only.

DISCLAIMER

This article is for informational purposes only and does not constitute legal advice.

Additional Resources

Explore more of our insights on related topics:

Drafting Effective Data Protection Clauses in UAE Commercial Contracts
Call Us NowChat With Our Team On WhatsApp