Article 12 AI Act logging — automatic event logs from TDX.
What the article requires. What we sign. How to access the logs. Sample JSON below.
What the article requires
Automatic recording of events over the lifetime of the system.
Article 12(1) of the EU AI Act requires high-risk AI systems to technically allow for the automatic recording of events ("logs") over the lifetime of the system. Article 12(2) sets the purpose: identifying situations that may result in risks at the national level or substantial modifications, and facilitating post-market monitoring under Article 72. Article 14(4)(d) ties this evidence to human oversight.
- Identification of situations that may result in risks
- Substantial modifications detection
- Post-market monitoring under Article 72
- Support for human oversight under Article 14
- Traceability across the full lifecycle
- Logs accessible to competent national authorities
Sample attestation log
One signed quote per request — JSON-LD, exportable.
Each inference call produces an ECDSA-signed log entry bound to the enclave measurement and model version. The signature is verifiable against the Intel SGX/TDX root of trust. No plaintext input or output is stored — only SHA-256 hashes — keeping Article 12 logging compatible with Article 32 GDPR confidentiality.
Retention
Configurable per workflow.
30 days
Low-risk workflows
Default for general-purpose copilots not in Annex III scope.
90 days
Standard default
Covers most regulated SaaS workloads under GDPR Art. 32 expectations.
365 days
High-risk regulated
Aligned with DORA, NIS2 and sectoral regulator expectations.
Extended
On request
For workflows under prudential or healthcare regulator long-term retention.
API access
Pull logs by request ID, time window or tenant.
Authenticated REST endpoints, scoped to your tenant. Pagination, filtering by Annex III category and approver identity. Bulk export as JSON-LD or CSV for audit submission. Verification endpoint at /trust/verify for independent signature checking.
# Fetch a single attestation log
GET /v1/attestation/logs/{request_id}
# Filter by time window and category
GET /v1/attestation/logs?from=2026-08-01&to=2026-08-12&category=credit_scoring
# Verify a signature independently
POST /trust/verify
Content-Type: application/jose+jsonFAQ
What does Article 12 of the EU AI Act require?
Article 12 requires high-risk AI systems to allow for the automatic recording of events ('logs') over their lifetime. Logs must enable identification of situations that may result in risks at the national level, substantial modifications, and facilitate post-market monitoring under Article 72. Article 14(4)(d) ties Article 12 to human oversight.
What does a VoltageGPU attestation log contain?
Each log entry is a signed ECDSA quote bound to: request ID, enclave measurement, model version with weight checksum, RFC3339 UTC timestamp, tenant ID, approver identity (when human-in-the-loop is configured), and SHA-256 hashes of input and output. The signature is verifiable against the Intel SGX/TDX root of trust.
How long are logs retained?
Default retention is 90 days. Configurable to 30 days for low-risk workflows or 365 days for high-risk regulated workflows. AI Act Article 12(2) does not set a minimum retention but national authorities and sectoral regulators (DORA, NIS2) commonly require 6 months to several years. Contact us for extended retention.
Are inputs and outputs stored?
No plaintext input or output is stored. Only SHA-256 hashes go into the log entry, keeping Article 12 logging compatible with Article 32 GDPR confidentiality. If your workflow needs the actual content for audit, you can capture it on your side and bind it to our request ID.
Can a national authority verify a log without VoltageGPU?
Yes. The signature is ECDSA-P384 over the canonical JSON-LD entry, verifiable against the Intel attestation root of trust. The /trust/verify endpoint is public and stateless — anyone with the log entry can confirm authenticity.
Related compliance pages
Article 12, 14, 15 and 32 obligations enforceable from 2 August 2026.
Article 28 native DPA, Article 32 confidentiality.
ICT third-party risk for banks, insurers and investment firms.
Supply chain security and incident reporting.
Vertical agents for legal, finance, regulated professionals.
Verify any request against the public attestation root.
Intel TDX, Protected PCIe, attested GPUs as raw compute.
Full agent line-up across legal, finance, healthcare and operations.
See a real signed quote — verify it yourself.
Open a confidential agent, run a real workflow, and pull the matching attestation log via the API.