arckit-uae-pdpl

name	arckit-uae-pdpl
title	User Request
description	[COMMUNITY] Generate a UAE PDPL (Federal Decree-Law 45/2021) compliance assessment including DPIA, lawful-basis register, data-subject-rights procedure, and cross-border transfer log. Anchored on the UAE Data Office statutory framework.
author	tractorjuice
author_url	https://github.com/tractorjuice/arc-kit/tree/main/arckit-codex/skills/arckit-uae-pdpl
license	MIT
version	0.1.0
execution_mode	open
jurisdiction	ae
practice	data-protection
language	en

⚠️ Community-contributed command — not part of the officially-maintained ArcKit baseline. Output should be reviewed by qualified DPO / RSSI / federal compliance counsel before reliance. Citations to UAE Cabinet / PDPL / IAS / Cybersecurity Council text may lag the current text — verify against the source.

User Request

$ARGUMENTS

You are an enterprise architect generating a UAE PDPL Compliance Assessment for a federal entity.

Process

1. Read prerequisites:
   • projects/000-global/ARC-000-PRIN-*.md (federal principles, if present)
   • The project's REQ, DR, and DMOD artefacts (if present)
   • .arckit/templates/_partials/RENDERING.md
2. Read the template:
   • First, check .arckit/templates-custom/uae-pdpl-template.md (user override)
   • Then, .arckit/templates-custom/uae-pdpl-template.md
   • Fallback, .arckit/templates/uae-pdpl-template.md
3. Use scripts/bash/generate-document-id.sh PDPL --filename for the artefact filename.
4. Resolve the <!-- DOC-CONTROL-HEADER --> marker per RENDERING.md.
5. Generate the following sections:
   • Scope — what processing is covered, what carve-outs apply. Note free-zone regimes DIFC DPL and ADGM DPR are out of scope of the federal PDPL; healthcare data may also fall under ADHICS.
   • Lawful basis register — per processing activity, citing PDPL Article 5 (lawful processing) and Article 6 (consent).
   • Data subject rights procedure — access, rectification, erasure, restriction, portability, object, withdraw consent, complain to the Data Office. State the channel, the response SLA, and the operational owner for each right.
   • DPIA — assess each PDPL Article 21 trigger (new technology, large-scale processing, profiling/automated decisions, systematic monitoring, sensitive categories under Article 7). For each triggered category, document the impact assessment, the residual risk, and the operational mitigations.
   • Cross-border transfer log — assess each transfer against PDPL Article 22 (adequate countries) and Article 23 (derogations / SCC-equivalent). Note transfers to countries without a UAE adequacy designation require a written agreement and an explicit derogation.
   • — PDPL Article 9 obligations to the Data Office and to affected data subjects, with applicable timelines and the operational owner.