---
title: "Dataset provenance and audit documentation | YPAI"
url: https://ypai.ai/compliance/provenance-audit/
description: "Data lineage with provenance records, consent documentation, and audit-ready exports, mapped to EU AI Act and GDPR requirements."
source: "src/copy/routes (route /compliance/provenance-audit/)"
---

# Dataset provenance and audit documentation

> Data lineage with provenance records, consent documentation, and audit-ready exports, mapped to EU AI Act and GDPR requirements.

## What is included in an evidence bundle?

The evidence bundle can include provenance records for each delivered asset, consent documentation with timestamps and version references, chain-of-custody records from collection to delivery, QA results, an exception log, and version history. The exact artefacts are fixed during scoping.

## How does this support EU AI Act Article 10?

EU AI Act Article 10 requires documented data governance for high-risk systems. YPAI delivers evidence for training data origin, consent status, and processing history, structured so your team can reference it during conformity assessment. YPAI does not perform conformity assessments or certify compliance.

## How are GDPR erasure requests evidenced?

Erasure workflows produce deletion evidence: which records were affected, when the deletion was executed, and the attestation delivered to the client. Procedures and timelines are defined in the DPA.

## When is the documentation delivered?

Provenance and audit documentation is delivered with the dataset it governs. Documentation scope, formats, and any interim reporting are agreed during scoping and defined in the engagement agreement.

## Can we review the documentation before committing?

Yes. Redacted sample provenance documentation and export examples are available during scoping, so legal and compliance stakeholders can review the evidence format before an engagement begins.