TwinEthos homeRequest access

Law

DIFC Data Protection Law Art. 38 (automated decisions)

DIFC (Ruler of Dubai); administered by the DIFC Commissioner of Data Protection (Art. 8) · AE-DU-DIFC · 1 provision encoded · verified against the official source as of 2026-10-03.

Informational data, not legal advice. Summaries and rules have not been reviewed by a lawyer: always verify official law text for decisions. A suggested guard is intended to address each rule; adding it is not a statement of compliance to that law.

AI-adjacent law General privacy or biometric law, included only where AI data flows trigger it; reported apart from AI-specific law.

Official text: assets.difc.com.

Trust and provenance 1 official source · last verified 3 Oct 2026 · not reviewed by a lawyer · 1 of 1 provision audit-grade · release 2026.10.03.3

Where this instrument's data comes from, how current it is, and what has and has not been checked. Each provision below has its own panel.

Official sources
Lanes
Binding law — in force 1
Verification
Sources last verified 3 Oct 2026; each provision states how.
Data release
Data release 2026.10.03.3, data as of 3 Oct 2026, schema 0.3.9.
Legal review
None of the 1 provision has been reviewed by a lawyer; no TwinEthos rule has been legally reviewed yet. Treat each as research to check against the official text; it is not legal advice. Open questions for counsel on them: 1.
Audit standard
1 of 1 provision audit-grade. The audit standard is TwinEthos's own quality bar for provenance, dates, applicability, detectors, fixtures, remediation and licences; it is not a legal review.
Detectors
1 detector, all experimental: written from the rule's text and not yet measured for precision on real code, so treat a hit as a lead to verify. Each provision lists its detectors' known limits.
Changes
  • 2026.10.03.3 (3 Oct 2026): 1 provision added

Each data release records which provisions changed; the full list is on Changes.

Binding law — in force AI-adjacent law

Data subjects may object to solely automated decisions with legal or seriously impactful effects and require manual review (DIFC Data Protection Law Art. 38)

Art. 38 (automated individual decision-making, including Profiling) · official text · In force: applies since 1 Jul 2020 · AE-DU-DIFC

Under the DIFC Data Protection Law, a data subject has the right to object to any decision based solely on automated processing, including profiling, that produces legal or other seriously impactful consequences for them and to require the decision to be reviewed manually (Art. 38(1)). The right does not apply to decisions necessary for a contract, authorised by applicable law with safeguards, or based on explicit consent (Art. 38(2)), but those exceptions never apply to minors (Art. 38(4)), and the contract and consent exceptions require suitable safeguards including at least the ability to have the processing reviewed manually (Art. 38(5)). Decisions based solely on automated processing of special categories need explicit consent or a substantial public interest under applicable law (Art. 38(6)). Detect a model output that becomes a decision about a person with no objection and manual-review route and no human decision.

Trust and provenance not reviewed by a lawyer · audit-grade · source verified 3 Oct 2026 · release 2026.10.03.3
Lane
Binding law — in force In force: applies since 1 Jul 2020
Official source
Art. 38 (automated individual decision-making, including Profiling) · captured 3 Oct 2026 · anchor hash (SHA-256) 5766047afe5a… · 3 more anchors in the data release
Verification
Quoted text found word for word in the captured official document (3 Oct 2026). Source last verified 3 Oct 2026: checked against the captured official document; not in the weekly watcher's list; checked against the captured document.
Data release
Data release 2026.10.03.3, data as of 3 Oct 2026, schema 0.3.9.
Legal review
Not reviewed by a lawyer. TwinEthos derived this rule from the official text it cites: treat it as research to check against that text; it is not legal advice. No TwinEthos rule has been legally reviewed yet. Open questions for counsel on this rule: 1.
Audit standard
Audit-grade: meets all 10 checks of the TwinEthos audit standard that apply to it. The audit standard is TwinEthos's own quality bar for provenance, dates, applicability, detectors, fixtures, remediation and licences; it is not a legal review.
Detectors

1 detector (data flow), experimental: written from the rule's text and not yet measured for precision on real code, so treat a hit as a lead to verify.

Known limits:

  • Special-category data use (Art. 38(6)) is not detected
  • Decisions with no legal or seriously impactful consequence are outside Art. 38; objection handling may live in another service.

Who it applies to

  • Duty falls on: controller
  • Systems covered: automated decision, consequential decision
  • Controllers within the DIFC Data Protection Law (incorporated in the DIFC, or processing in the DIFC as part of stable arrangements, Art. 6(3)) that take decisions based solely on automated processing with legal or seriously impactful consequences. The Law is in force from 2020-07-01 (Art. 4); the consolidated text does not show whether the 2022 or 2025 amendment laws changed Art. 38.
  • Not covered:
    • Processing by natural persons in a purely personal or household activity with no commercial connection (Art. 6(4))
  • Whether it applies depends on facts outside the code; a person has to decide.

The guard to add

Route significant automated decisions through meaningful human review, or wire in an automated-decision notice, reasons, human intervention, a way to give a view, and contest.

At the point where model output becomes a significant decision about a person (approve, deny, underwrite, set_status), either queue the case for a reviewer who weighs the evidence and can change the outcome before it takes effect (review_queue.enqueue, requires_human_review), or, where the decision stays solely automated, record the permitted basis for that decision type and wire the safeguards in. Those safeguards are a notice in the decision message that it was made by automated processing, reasons the person can read, and request_human_review or contest routes where the person can give their view and have a human reconsider. A reviewer who approves every case without examining it does not make the decision non-automated, so the review records reviewer identity, the evidence viewed, and the outcome.

Where it goes: 1 application source code, 9 AI output handling, 15 agent action surface, 14 user-facing text.

What this provision adds:

  • Offer an objection route for solely automated decisions with legal or seriously impactful consequences that leads to manual review by a person who can change the outcome.
  • Never rely on the contract, law or consent exceptions for minors, and keep manual review available when relying on contract or consent.

Example (Python + OpenAI SDK), before:

verdict = client.chat.completions.create(model=MODEL, messages=msgs).choices[0].message.content
if verdict.strip() == 'deny':
    deny(applicant)
    send_decision_email(applicant, 'Your application was not approved.')

After:

out = client.chat.completions.create(model=MODEL, messages=msgs,
                                     response_format={'type': 'json_object'})
result = json.loads(out.choices[0].message.content)
if result['decision'] == 'deny':
    if requires_human_review('credit'):                 # a person decides
        review_queue.enqueue(applicant.id, proposal=result)
    else:                                               # solely automated, recorded basis
        deny(applicant, basis=DECISION_BASIS['credit'], reasons=result['reasons'])
        send_decision_email(applicant, render('adm_denial.txt', notice=ADM_NOTICE,
            reasons=result['reasons'], contest_url=f'{BASE}/decisions/{applicant.id}/contest'))

Control: Solely-automated significant decision without human-intervention safeguards. The same guard addresses 15 items with binding law in 15 jurisdictions. Engineering guidance, not legal advice.

Related incidents

No guardrail sits on this exact control; these incidents are cited by guardrails on related controls.

Rule id difc-dp-law-art38.object-and-manual-review · review status: primary source derived

Informational data, not legal advice. Summaries are TwinEthos's own words and rules have not been reviewed by a lawyer: check the official text before relying on any of it. A guard addresses an item; adding it is not a statement that your code meets any law.