What this page covers
Article 12 is not only about collecting more logs. The useful question is whether an auditor can reconstruct the relevant event chain without trusting an editable production database.
Legal timing
The AI Act entered into force on 1 August 2024. The Commission describes 2 August 2026 as the general application date, while the AI Omnibus political agreement moves many high-risk areas to 2 December 2027 and product-integrated systems to 2 August 2028. The preparation work still has to start now because evidence cannot be rebuilt reliably after deployment.
This page is implementation guidance for evidence planning, not legal advice.
Evidence Attesto AI can preserve
canonical event hash
model or service version
dataset version
human approval or override
Merkle inclusion proof
Example evidence records
Example proof receipt
Example Attesto receipt
event_type
ARTICLE12LOGGING
timestamp
2026-06-04T10:21:00Z
leaf_hash
sha256:8f41...b19e
merkle_root
sha256:52ac...91d4
verification_status
valid demo receipt, raw data not exposed
Where Attesto fits
Attesto adds proof material around AI events: hashes, signatures, Merkle proofs and verifier receipts that survive system changes.
FAQ
How is this different from a normal log?
A normal log asks an auditor to trust the system that produced it. Attesto records hashes, signatures, Merkle proofs and verifier receipts so selected evidence can be checked independently.
Does Attesto need to expose raw sensitive data?
No. Raw records can remain encrypted or customer-controlled while proof material is shared for verification.
Where does AI Act Article 12 logging fit in the compliance stack?
Attesto adds proof material around AI events: hashes, signatures, Merkle proofs and verifier receipts that survive system changes.