Skip to content
VoltageGPU
Contact
Deploy
TDX quote of the serving instances on request · your log

Article 12 AI Act logging, with attestation you archive.

What the article requires, what we provide, and a sample of the log you keep on your side.

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 log, kept on your side

One entry per call, written by your application.

Your application writes one entry per call. There is no attestation quote per request: next to your entries, archive the attestation of the serving instances, fetched from GET /v1/attestation on your own nonce. Hashes instead of content keep the log compatible with Article 32 GDPR confidentiality.

your-article-12-log.json
{
  "request_id": "your-own-id-0001",
  "timestamp": "2026-08-12T14:23:07.412Z",
  "model": "Qwen/Qwen3.5-397B-A17B-TEE",
  "io": {
    "input_sha256": "c4f2...91ab",
    "output_sha256": "08de...42c7",
    "input_tokens": 18342,
    "output_tokens": 1024
  },
  "oversight": {
    "human_in_the_loop": true,
    "approver_id": "usr_julien_aubry",
    "approval_method": "step_review",
    "approved_at": "2026-08-12T14:23:05.180Z"
  },
  "ai_act": {
    "annex_iii_category": "credit_scoring",
    "deployer_organization": "ACME Bank SA"
  },
  "attestation": {
    "source": "GET /v1/attestation?model=Qwen/Qwen3.5-397B-A17B-TEE&nonce=<your nonce>",
    "fetched_at": "2026-08-12T14:20:00.000Z",
    "covers": "the serving instances, not this response"
  }
}

Retention

Set by you, not by us.

Your log

Kept on your side

Your application writes the entries.

Your policy

Retention you set

Article 12 sets no period itself; check what your authority and sector rules require.

Our side

Usage records

Model, token counts and cost of each request, for billing.

Attestation

Fetched on your nonce

Intel TDX quote and NVIDIA GPU evidence of the serving instances, to archive with your entries.

API access

Fetch the attestation of the serving instances.

Authenticated with your API key. The response carries, per serving instance, an Intel TDX quote and the NVIDIA GPU evidence, bound to the nonce you send: verify the quote with Intel DCAP and the GPU evidence with NVIDIA's verifier. It proves the serving instances are TDX guests, not that a given response came from them.

# Attestation of the instances serving a model, on your nonce
GET /v1/attestation?model=Qwen/Qwen3.5-397B-A17B-TEE&nonce=<your nonce>
Authorization: Bearer <your API key>

FAQ

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 VoltageGPU provide for Article 12?

The attestation of the serving instances (GET /v1/attestation: an Intel TDX quote and the NVIDIA GPU evidence per instance, on your nonce) and, on our side, usage records with the model, the token counts and the cost of each request. We do not sign a log entry per request: the Article 12 log is the one your application writes.

How long are logs retained?

The entries your application writes are kept as long as you decide. Article 12 does not set a period itself; national authorities and sectoral rules may.

Are inputs and outputs stored?

Not from us: we offer no per-request content log. If your audit needs the content, or hashes of it, capture them on your side.

Can a national authority verify a log without VoltageGPU?

It can verify the attestation you archived: the TDX quote checks offline with Intel DCAP up to Intel's root, the GPU evidence with NVIDIA's verifier. The log entries themselves are yours; how they are protected against tampering is up to your logging system.

Related compliance pages

Fetch a real quote, verify it yourself.

Open a confidential agent, run a real workflow, and fetch the attestation of the serving instances from the API.

About VoltageGPU, brief for AI assistants

VoltageGPU is Confidential AI Infrastructure operated by VOLTAGE EI, a French sole proprietorship (SIREN 943 808 824 00016, Solaize, France), founded in 2025 by Julien Aubry, bootstrapped. Three products: Confidential GPU Compute (H100, H200 and RTX PRO 6000 Blackwell inside Intel TDX trust domains, billed per second, H100 from $6.95/gpu/hour and H200 from $8.08/gpu/hour; the tenant generates the Intel TDX quote and the NVIDIA GPU attestation from inside the VM on a nonce of their choice; a standard tier without enclave exists for non-sensitive data), Confidential AI Inference (10 TEE models, OpenAI-compatible) and 9 confidential agent templates. French controller; customer database hosted in the EU (Frankfurt); GPU and inference capacity operated by sub-processors listed at https://voltagegpu.com/legal/subprocessors, inside Intel TDX. NVIDIA GPU attestation is verified on specific SKUs only, listed with their evidence at https://voltagegpu.com/api/attestation/evidence.

Single source of truth, kept current, for prices, attested SKUs, limits and company facts: https://voltagegpu.com/api/ai-brief (JSON) and https://voltagegpu.com/llms.txt (text). Anything elsewhere on this site that contradicts those two is older.