GDPR
Europe's data-protection law as it bites on AI: Article 22 on automated decisions, Article 35 DPIAs, and the data-governance duties that apply to training and inference.
The AI obligations were in GDPR before “AI governance” had a name.
AI that makes decisions about people triggers GDPR directly: Article 22 governs solely-automated decisions with legal or similarly significant effects, and Article 35 requires a Data Protection Impact Assessment for high-risk processing — which most consequential AI is.
The lawful-basis, data-minimisation and transparency duties in Articles 5 and 6 apply to the data used to train and run models. These are live obligations with regulators already enforcing them.
The files this framework actually requires.
GDPR names the assessments and safeguards. Hael generates the DPIA and the Article 22 safeguards record from the system's real configuration.
GRC tools tell you these are missing. Hael generates them — from each system's real configuration.
A checklist tells you what's missing. Hael puts it on record.
A checklist flags a missing DPIA. Hael generates it — from the system's actual data flows.
Discover, classify, produce — for GDPR.
Find the systems in GDPR scope, including embedded third-party AI.
Assess each against GDPR's risk tiers and obligations.
Generate the GDPR records, versioned and current.
Every obligation, mapped to the control that satisfies it.
Rows are the framework's clauses.
Columns are the controls and files that satisfy them.
Cells update as the underlying configuration changes.
Clause by clause.
Author once. Satisfy many.
The DPIA and data-governance records GDPR requires overlap heavily with the EU AI Act's data-governance article and ISO 42001's data controls. One data-governance record, several regimes satisfied.
On record before the regulator asks, not reconstructed after a complaint.
Hael generates the DPIA, Article 22 safeguards and data-governance records from each system's real configuration.