Risk · R-157 · Transparency & Explainability
Training data transparency gap
The organisation cannot say what data a model was trained on, to the level regulators, customers or rights holders require.
- Severity
- Medium
- Audience
- Heads-of · Practitioner
- Frameworks
- Article 10 · Article 53 · Annex A.7 · AML.M0025
- Responsible AI domain
- Lifecycle stage
- Reviewed
- 2026-11-11
What it is
What a model was trained on determines much of what matters about it: whose data is inside it, what it may reproduce, what biases it carries, what rights were needed. More and more parties ask. Regulators ask about lawfulness and bias. Customers ask in due diligence. Rights holders ask whether their works were used. The EU AI Act requires providers of general-purpose models to publish a summary of the content used for training. The risk is that the organisation has no answer, because it kept no record of its own training data or because its supplier discloses nothing.
How it happens
- Datasets were assembled over time with no record of their sources.
- A pre-trained model was adopted whose provider describes its data in general terms only.
- Fine-tuning data was drawn from many internal systems with no inventory.
- Records exist and are held by people who have left.
Why it matters
An organisation that cannot describe its training data cannot show a lawful basis, answer a rights request, respond to a copyright claim or complete a customer's questionnaire. Silence is read as having something to hide.
Warning signs
- No dataset documentation exists for models in production.
- Supplier responses on training data are vague.
- Due diligence questions about training data take weeks to answer.
- The organisation has no position on what it would disclose publicly.
Mitigating controls
Primary controls
- Dataset documentation Directive
- Records what each dataset contains and where it came from. Each dataset used for AI has a maintained record of its source, collection method, contents, rights, lawful basis, known limitations and permitted uses.
Supporting controls
- Public AI transparency record Directive
- Publishes what can be made public. The organisation publishes and maintains a record of its significant AI uses, describing what each is for, what data it uses and what safeguards apply.
- Third-party model and vendor due diligence Directive
- Obtains the equivalent information from providers. Before an AI supplier, model or dataset is adopted, it is assessed against AI-specific criteria to a depth set by how material the use is, with evidence for the answers.
- Training data provenance checks Preventive
- Establishes the origin being disclosed. The source, collection method, rights and integrity of every dataset are verified and recorded before it is used for training, fine-tuning or retrieval.
Framework and clause references
| Framework | Clause | Title |
|---|---|---|
| EU AI Act | Article 10 | Data and data governance Knowledge of data origin. |
| EU AI Act | Article 53 | Obligations for providers of general-purpose AI models The public summary of training content. |
| ISO/IEC 42001:2023 | Annex A.7 | Data for AI systems Data for AI systems. |
| MITRE ATLAS | AML.M0025 | Maintain AI Dataset Provenance Dataset provenance. |
Sources
- EU AI Act: Regulation (EU) 2024/1689 European Union (EUR-Lex) · official text
- ISO/IEC 42001:2023 – AI management systems ISO/IEC · framework
- MITRE ATLAS MITRE · framework
Related terms
How to cite
Axiom Verity (2026). Training data transparency gap. Reference Library, R-157. https://axiom-verity.com/risks/training-data-transparency-gap. Reviewed 2026-11-11.
Found an error or a better source? Report a correction.