Start hereSelect the applicable regime
~84 days leftOpen step
Guide library
Regulation Middle East

UAE PDPL

Federal Decree by Law No. 45 of 2021 on the Protection of Personal Data

Identify the applicable UAE privacy regime and document processing and transfer decisions.

Who it applies to

Controllers and processors within the federal law’s scope, subject to its territorial rules and exclusions.

What you’ll produce

Documented privacy governance, individual rights and safeguards for covered UAE processing.

Check free-zone and sector-specific regimes, including DIFC and ADGM, before assuming the federal framework applies.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

UAE PDPL kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Select the applicable regime · Privacy counsel + operations [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
The whole journeyabout 84 days across 4 steps
  1. 01Select the applicable regimePrivacy counsel + operations · ~14 days
  2. 02Document bases, notices and rightsPrivacy lead + product · ~28 days
  3. 03Manage high-risk processing and transfersRisk lead + legal · ~28 days
  4. 04Prepare incident escalationSecurity + privacy lead · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 12 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Select the applicable regimePrivacy counsel + operationsAt initiationSet a start dateJurisdiction matrix; Data flows; Role registerOpen
Document bases, notices and rightsPrivacy lead + productBefore processing and on requestSet a start datePrivacy notices; Rights procedure; Appointment decisionOpen
Manage high-risk processing and transfersRisk lead + legalBefore covered activitiesSet a start dateImpact assessments; Transfer register; ContractsOpen
Prepare incident escalationSecurity + privacy leadOn discovery and during exercisesSet a start dateIncident playbook; Notice templates; Exercise reportOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Select the applicable regime

    Who Privacy counsel + operations When At initiation

    Map entities, locations, data types and free-zone or sector exclusions. Identify controllers and processors and assign responsibilities.

    What to produce

    Jurisdiction matrixSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

    Data flowsDiagram worksheet

    Gather first

    • System and vendor inventory
    • Examples of live transactions or data events
    • Approved boundaries and information categories

    How to prepare it

    1. Sketch an entry point, storage location, processing system and recipient for each flow. Label arrows with what moves and in which direction.
    2. Show trust boundaries, geographic locations, contracts or interconnections that matter. Include administrative access, backups and deletion paths where relevant.
    3. Walk through a real end-to-end transaction with engineering and operations. Save an accessible diagram and keep the reviewed flow register beside it.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Source
    Web checkout
    Destination
    Billing API in EU region
    Data and purpose
    Order reference and billing email to send the receipt
    Protocol and boundary
    HTTPS, crosses from public network into hosted production
    Owner and validation
    Billing owner, validated against request logs on 2026-11-12

    Check before handing it over

    An engineer can trace collection to deletion, and a reviewer can see every crossing or third-party handoff.

    Use the worksheet to design the diagram. Share the diagram with the people confirming scope, transfers or controls.

    Role registerMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    Every decision has one accountable person, a backup and a practical route to reach them.

    Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.

  2. 02

    Document bases, notices and rights

    Who Privacy lead + product When Before processing and on request

    Determine consent or another statutory basis. Create notices, establish request channels and verify appointment criteria for a data protection officer.

    What to produce

    Privacy noticesMemo

    Gather first

    • Approved data map and purposes
    • Applicable disclosures and languages
    • Actual rights, consent and contact channels

    How to prepare it

    1. Write the information a person needs at the point of collection or disclosure. Use the applicable legal checklist to cover who, why, what, recipients, retention and choices.
    2. Match every promise to the real product and supplier configuration. Draft any short collection notice alongside the longer policy and use language appropriate to the audience.
    3. Have privacy and product owners check the draft against the live journey. Publish the approved version, record where it appears and test all contact and choice links.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Audience and moment
    Customer account contact, on the invoice email form
    Plain wording
    We use your billing email to send receipts and help with billing questions.
    Choices and contact
    Link to the applicable privacy request channel.
    Supporting record
    Processing activity P-014 and retention schedule FS-04
    Publish and verify
    Legal approval, web form URL, version and date

    Check before handing it over

    A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.

    Send approved text to the publishing owner and give support teams the version and effective date.

    Rights procedureMemo

    Gather first

    • Covered rights and scope exceptions
    • Intake channels and identity verification rules
    • Systems, vendors and escalation contacts

    How to prepare it

    1. Start from each intake channel. Write who logs the request, verifies the requester and calculates the due date under the applicable rule.
    2. Map tasks to system owners. Include gathering records, searching vendors, deciding exemptions, securing replies and obtaining approval for extensions or denials.
    3. Run a test request end to end. Track timestamps, handoffs and output. Fix gaps and repeat the test before putting the procedure into use.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Trigger
    A verified customer requests access through the support form.
    Triage
    Open a case and record receipt time, jurisdiction and deadline.
    Handoffs
    Billing and customer operations return records using restricted links.
    Quality check
    Reviewer checks redactions, exemptions and controller instructions where applicable.
    Close
    Send the response securely and save delivery evidence and date.

    Check before handing it over

    A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.

    Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.

    Appointment decisionMemo

    Gather first

    • Applicable form or requirements
    • Approved scope and supporting records
    • Named signatory and approval route

    How to prepare it

    1. Identify which person can sign and what they must confirm. Gather supporting evidence, dates, responsibility and any required issuer wording.
    2. Draft a signed-document checklist or brief in your organization’s approved format. Reconcile every factual claim against the source evidence and route the draft for review.
    3. Use the applicable official wording or format for the real signed document. File the executed copy with its date, applicable scope and supporting evidence.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document owner
    Accountable executive or authorized signatory
    Scope and date
    Agreed service scope, as of 2026-10-31
    Supporting documents
    Scope v3, final control testing and open issue review
    Review and approval
    Legal and responsibility owner review before signature
    Filed record
    Signed copy plus evidence references

    Check before handing it over

    The signer can explain the basis for each statement and the record reflects the required scope and period.

    Give the executed document to the relevant recipient under the engagement or regulation. Use the worksheet to organize review.

  3. 03

    Manage high-risk processing and transfers

    Who Risk lead + legal When Before covered activities

    Screen processing for impact assessments, set security controls and evaluate international transfer conditions and processor terms.

    What to produce

    Impact assessmentsSpreadsheet

    Gather first

    • Processing or service design and affected people
    • Threats, consequences and assessment triggers
    • Risk methodology and current safeguards

    How to prepare it

    1. Screen the activity against the applicable assessment trigger. Describe the real scenario and who or what could be harmed. Record likelihood and consequence using your criteria.
    2. Describe existing safeguards. Decide what reduces the risk and what risk remains after those measures. For a required impact assessment, document necessity, alternatives and consultation where applicable.
    3. Send the result to the person who can approve, change or stop the activity. Set a review trigger and keep evidence of the decision.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and risk
    Account recovery could expose invoices to an impersonator.
    Affected people or assets
    Customer account contacts and invoices
    Current controls
    Recovery uses verified channel. Sampled evidence linked.
    Proposed treatment
    Require a second check for requests to change the billing address.
    Remaining risk and decision
    Moderate under company method. Approval required before launch.
    Owner and review trigger
    Product risk owner, repeat when recovery flow changes

    Check before handing it over

    The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.

    Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.

    Transfer registerSpreadsheet

    Gather first

    • Verified transfer map and remote access paths
    • Recipient contracts and safeguards
    • Current transfer rules, mechanisms and local restrictions

    How to prepare it

    1. Record exporters, importers, roles, countries, data and purposes. Include onward transfers or remote access if relevant to the governing law.
    2. Identify the permitted basis, mechanism or exemption and why it fits. Document safeguards, any required risk assessment and supporting clauses or approvals.
    3. Secure legal review and set triggers for reassessment, such as a new country, recipient or subcontractor. Tie the decision to procurement or product release.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Transfer ID
    XFER-018
    Parties and data
    EU controller to external support provider, ticket metadata
    Country and access
    Remote access from recipient country, limited support staff
    Mechanism and review
    Use applicable transfer mechanism. Legal assessment L-019 pending.
    Controls and approval
    Role restrictions and access logs. No production access until approved.

    Check before handing it over

    The register shows actual access paths, the basis for each transfer and a clear release decision.

    Share the decision with supplier and access owners so they can implement the conditions before data is available.

    ContractsMemo

    Gather first

    • Current agreement and service description
    • Applicable flow-down terms or engagement requirements
    • Contract owner and legal review

    How to prepare it

    1. Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
    2. Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
    3. Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Party and service
    Northstar hosting provider, production backup
    Clause or requirement
    Incident notification and contacts
    Current position
    General notice terms. No operational escalation contacts listed.
    Change to review
    Add named response channel and request confirmation of the timing.
    Owner, status and record
    Vendor lead, legal review pending, contract register V-018

    Check before handing it over

    The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.

    Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.

  4. 04

    Prepare incident escalation

    Who Security + privacy lead When On discovery and during exercises

    Classify incidents, preserve evidence and resolve who notifies the authority and individuals under the applicable federal, free-zone or sector rule.

    What to produce

    Incident playbookMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    Every decision has one accountable person, a backup and a practical route to reach them.

    Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.

    Notice templatesMemo

    Gather first

    • Incident case facts and awareness timestamps
    • Current authority forms and applicable notification criteria
    • Approved recipients and counsel or incident lead

    How to prepare it

    1. Identify the recipient and required fields. Prepare a concise account of what happened, data and people affected, likely consequences, protective steps and an official contact.
    2. Mark unknown facts and state how they will be updated. Confirm recipients and secure delivery or required portal before sending.
    3. Obtain the prescribed approval. Keep the sent version, delivery receipt and any follow-up or supplement with the case.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Recipient and reference
    Approved authority or affected person, incident INC-041
    What happened
    An account viewed a link beyond its permissions. Investigation continues.
    Likely effect and protection
    Access was revoked. Review your recent account activity and contact support for help.
    Contact and update
    Approved incident contact, updated facts after log review
    Approval and record
    Privacy lead approved, receipt recorded in case file

    Check before handing it over

    Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.

    Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.

    Exercise reportMemo

    Gather first

    • Approved scenario and participant roles
    • Goals and scoring criteria
    • Event timeline and expected records

    How to prepare it

    1. Prepare a scenario and timed new information that tests decisions, handoffs and evidence. Assign a facilitator and separate observer.
    2. During the exercise, note what participants actually did, the timestamps and where expected responses failed. Distinguish simulated actions from real ones.
    3. Write a short after-action summary with owners, deadlines and a retest plan. Attach the scenario, attendance and evidence references.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Scenario
    Simulated export leak found at 09:20 UTC
    Objective
    Reach operational and legal leads and classify the incident within the exercise target.
    Observed behavior
    Engineering preserved logs. Initial escalation went to an inactive mailbox.
    Action and owner
    Privacy operations updates the routing list before 2026-12-01.
    Retest
    Repeat the handoff in the next on-call drill.

    Check before handing it over

    An absent participant can see what was tested, what happened and why an action was assigned.

    Send approved findings to action owners and file the record for governance or assessment.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes