EU AI Act Compliance: Article 26 Deployer Obligations and 6-Month Log Retention

Article 26 deployer duties including the 6-month log retention floor, plus shipped Assess mappings for Articles 12, 13, 14, and 26. Regulation (EU) 2026/1744 defers stand-alone Annex III high-risk obligations to 2 December 2027.

Read: 9 min
Updated: Aug 24, 2026
Level: deep

Ready to protect your own setup?

Install Pipelock Inspect the proof

Article 26(6) deployer log retention answer

Deployers of high-risk AI systems must retain the logs the system automatically generates for at least six months, to the extent the deployer controls those logs, and longer where Union or national law requires it. Article 12 is the design-time obligation on the provider to make the system technically capable of automatic logging. Article 26(6) is the runtime obligation on the deployer to keep the logs that result.

The minimum is the floor, not a ceiling. Sector law often sets longer retention windows, and Union data protection law can override the six-month floor in specific cases. Financial institutions subject to internal-governance rules under Union financial services law keep these logs as part of the documentation maintained under that law.

Article 12 vs Article 26(6)

Article 12 is the provider-side record-keeping design duty: a high-risk AI system must be technically capable of automatic event logging. Article 26(6) is the deployer-side retention duty: the deployer keeps the logs under its control for at least six months, unless another applicable law requires a longer or different period.

Pipelock generates runtime evidence for those duties. The deployer still owns retention policy, review workflow, incident sign-off, and legal sufficiency.

Below are the shipped Assess mappings for Articles 12, 13, 14, and 26, followed by deployer obligations and the current high-risk timeline. Regulation (EU) 2026/1744, the Digital Omnibus on AI, amends Regulation (EU) 2024/1689. It was published in the Official Journal on 24 July 2026 and entered into force on 27 July 2026. It defers stand-alone Annex III high-risk obligations to 2 December 2027 and Annex I embedded-in-product safety-component obligations to 2 August 2028.

Background

Regulation (EU) 2026/1744, the Digital Omnibus on AI, is the first major amendment to the AI Act, Regulation (EU) 2024/1689. The European Parliament endorsed it on 16 June 2026 and the Council gave final approval on 29 June 2026. It was published in the Official Journal on 24 July 2026 and entered into force on 27 July 2026. The amendment defers stand-alone Annex III high-risk obligations to 2 December 2027 and Annex I embedded-in-product safety-component obligations to 2 August 2028. Article 26 sets twelve paragraphs of deployer duty. This page summarizes the runtime-facing ones (paragraphs 1, 2, 4, 5, 6). The shipped catalog maps Article 26 as a whole.

Pipelock sits between your AI agent and the network. MCP proxy mode scans tool arguments and responses bidirectionally. Fetch proxy mode scans fetched response content and URL parameters. Forward proxy mode (CONNECT) filters by hostname, with optional TLS interception for full body inspection. The shipped Assess mappings below identify the controls and evidence it contributes.

What Gets Enforced (current text)

Article	Requirement	Penalty
Art. 9	Risk management system (continuous, iterative)	Up to EUR 15M or 3% turnover
Art. 12	Automatic event logging for traceability	Up to EUR 15M or 3% turnover
Art. 14	Human oversight with override and stop capability	Up to EUR 15M or 3% turnover
Art. 15	Cybersecurity, resilience, fail-safe mechanisms	Up to EUR 15M or 3% turnover
Art. 26	Deployer monitoring and 6-month log retention	Up to EUR 15M or 3% turnover

Industry estimates put conformity assessment at 8-14 months. If you haven’t started planning, now is the time.

Shipped Assess article mappings

Assess v3.7.1 includes the four entries below. Covered is the catalog status for a product contribution; it does not establish legal compliance. Articles 9 and 15 are not catalog entries.

ID	Article	Status	Pipelock mapping	Limit
A12	Article 12 - Record-Keeping	Covered	Replayable records and signed manifests support record-keeping.
A13	Article 13 - Transparency and Instructions	Partial	Reports and badges surface operational posture, but user instructions are deployment-specific.	Provider-facing documentation is only partly represented in the binary.
A14	Article 14 - Human Oversight	Covered	Human-in-the-loop approvals and dry-run testing support oversight.
A26	Article 26 - Deployer Monitoring	Covered	Assess outputs and recorded telemetry support deployer monitoring obligations.

Article 26: Deployer Obligations and 6-Month Log Retention

Article 26 sets out the deployer’s runtime duties for high-risk AI systems. This section focuses on the duties most relevant to AI agents in production. It is not a complete legal summary. Additional duties in Article 26 apply conditionally (workplace notice, public-authority registration, GDPR DPIA linkage, law-enforcement biometric ID rules, notice to natural persons, authority cooperation), and other articles cover provider-side and lifecycle obligations. Read the official OJ text and get qualified legal advice before treating any single page as a compliance checklist.

Runtime-facing deployer duties under Article 26:

Art. 26(1). Take appropriate technical and organisational measures to use the system in accordance with the provider’s instructions for use.
Art. 26(2). Assign human oversight to natural persons with the necessary competence, training, authority, and support.
Art. 26(4). Ensure input data is relevant and sufficiently representative of the intended purpose, to the extent the deployer controls the input.
Art. 26(5). Monitor the system’s operation based on the instructions for use. Inform the provider (and, for serious incidents or identified risks, the market surveillance authority) without undue delay. Financial institutions subject to internal-governance rules under Union financial services law can satisfy this monitoring duty by complying with those rules.
Art. 26(6). Keep the logs automatically generated by the system for at least 6 months, to the extent those logs are under the deployer’s control. Longer retention applies where other Union or national law requires it, in particular data protection law. Financial institutions maintain logs under their applicable financial services law documentation rules.

Provider-side design obligation (Article 12). Article 12 requires high-risk AI systems to be designed with the technical capability to automatically record events (logs) throughout their lifecycle. Article 12 is about the system being capable of logging; the deployer’s duty to actually keep those logs for 6 months is Article 26(6). Keeping the two articles straight matters because they sit on different parties (provider vs. deployer).

What runtime tooling often misses: Article 26(5) operation monitoring and Article 26(6) log retention. Many AI governance tools focus on training-time concerns (data governance, bias assessment, model documentation). They don’t see what the agent does at 2am when it calls an MCP tool or hits an API.

What Pipelock provides toward these duties:

Pipelock provides the evidence source, not the compliance program. It records runtime decisions, emits metrics, and can sign receipt chains when a signing key is configured. The deployer decides where logs live, how long they stay, who reviews them, and who signs off.

The shipped A26 mapping names Assess outputs, the flight recorder, and audit emission as support for deployer monitoring. It does not separately map Article 26’s individual paragraphs or enforce a retention period.

A minimal emit configuration:

emit:
  webhook:
    url: https://logs.example.invalid/ingest
    min_severity: info
  syslog:
    address: udp://syslog.example.invalid:514
    min_severity: info

Pair with S3 Object Lock, Loki retention policy, or SIEM lifecycle rules set to at least 6 months. The logs are a product output; the retention period is your deployment decision.

Download the 2-page Article 26 matrix (PDF): obligations, Pipelock evidence, deployer-owned gaps, and sample retention setup. The Digital Omnibus on AI, Regulation (EU) 2026/1744, defers stand-alone Annex III high-risk obligations to 2 December 2027 and embedded-in-product safety-component obligations to 2 August 2028.

What Pipelock Does NOT Cover

Pipelock is a runtime network security layer. It does not cover:

Training data governance (Art. 10): Pipelock operates at runtime, not training time
Conformity assessment (Art. 43): organizational process, not a tool feature
Bias and fairness evaluation (Art. 10(2)): Pipelock applies rules uniformly but doesn’t evaluate model fairness
Full system documentation (Art. 11): Pipelock documents itself; full system docs are the deployer’s responsibility
Fundamental rights impact assessment (Art. 27): requires organizational assessment

Pipelock is one component of a compliance stack. Use it alongside model governance tools (Credo AI, Holistic AI) and organizational processes.

Separate NIST AI RMF mapping

The shipped NIST AI RMF mapping is separate from the EU AI Act mapping. GOVERN and MAP are partial; MEASURE and MANAGE are covered. It does not define a function-to-article crosswalk. See NIST AI RMF coverage for the product evidence and limits.

Enforcement Timeline

Date	Milestone	Status
August 1, 2024	EU AI Act enters into force	In force
February 2, 2025	Prohibited AI practices (Art. 5) take effect	In force
August 2, 2025	General-purpose AI model obligations (Art. 51-55) take effect	In force
24 July 2026	Regulation (EU) 2026/1744, the Digital Omnibus on AI, published in the Official Journal	Published
27 July 2026	Regulation (EU) 2026/1744 enters into force	In force
2 December 2027	Stand-alone Annex III high-risk obligations	Current text
2 August 2028	Annex I embedded-in-product safety-component obligations	Current text

The European Parliament endorsed Regulation (EU) 2026/1744 on 16 June 2026, and the Council gave final approval on 29 June 2026. It is the first major amendment to Regulation (EU) 2024/1689.

Penalties: up to EUR 35M or 7% global turnover (prohibited practices), EUR 15M or 3% (high-risk violations), EUR 7.5M or 1% (misleading information). SME and startup fines are capped at the lower of percentage or absolute amount.

Get Started

# Install
# Requires Go 1.26+, Git, and Make. Start in a directory without a pipelock subdirectory. Community build only; use a release binary for paid features.
git clone --branch v3.7.1 --depth 1 https://github.com/pipelab-org/pipelock.git
make -C pipelock install
# Homebrew alternative on macOS/Linux: brew install luckyPipewrench/tap/pipelock

# Generate a config
pipelock generate config --preset balanced > pipelock.yaml

# Enable audit logging + run
pipelock run --config pipelock.yaml

Set HTTPS_PROXY=http://127.0.0.1:8888 on your agent. Every connection is now logged and filtered. Enable TLS interception for full HTTPS body scanning.

For the full compliance mapping with NIST crosswalk, see the source document on GitHub.

Generate signed compliance evidence for your deployment with pipelock assess.

Frequently asked questions

Does the EU AI Act apply to AI coding agents?

AI coding agents are not explicitly listed in Annex III of the EU AI Act. However, agents writing software for medical devices, critical infrastructure, or employment systems may be classified as safety components of high-risk systems. Organizations in regulated sectors often choose to comply with Articles 9, 12-15 as a risk management best practice, regardless of formal classification.

What EU AI Act articles does Pipelock help with?

Assess v3.7.1 maps four articles: Article 12 (record-keeping), Article 13 (transparency, partial), Article 14 (human oversight), and Article 26 (deployer monitoring). Articles 9 and 15 are not included in that shipped catalog.

When do EU AI Act high-risk obligations apply?

Regulation (EU) 2026/1744, the Digital Omnibus on AI, amends the AI Act, Regulation (EU) 2024/1689. It was published in the Official Journal on 24 July 2026 and entered into force on 27 July 2026. It defers stand-alone Annex III high-risk obligations to 2 December 2027 and Annex I embedded-in-product safety-component obligations to 2 August 2028. The European Parliament endorsed the amendment on 16 June 2026 and the Council gave final approval on 29 June 2026.

Is Pipelock a complete EU AI Act compliance solution?

No. Pipelock covers runtime network-level controls: egress filtering, content inspection, audit logging, and human oversight. It does not cover training data governance (Art. 10), conformity assessment (Art. 43), bias evaluation, or full-lifecycle AI management. It is one component of a defense-in-depth approach.

How does Pipelock generate Article 12 audit logs?

Pipelock automatically logs requests as structured JSON events. Blocked events include URL, method, scanner, reason, and client IP. Allowed events add status code, size, and duration. These logs support Article 12 evidence needs for automatic event recording and risk situation identification; the deployer’s program is what satisfies Article 12 itself. Logs can be forwarded to any SIEM via webhook or syslog sinks.

How long must EU AI Act deployers retain logs?

EU AI Act Article 26(6) requires deployers of high-risk AI systems to keep the logs automatically generated by the system, to the extent such logs are under the deployer’s control, for a period appropriate to the intended purpose and at least 6 months. Longer retention may apply where other Union or national law requires it, in particular Union data protection law. Financial institutions subject to internal-governance rules under Union financial services law maintain the logs as part of the documentation kept under that law. Article 12 is the design-time obligation on providers to make high-risk systems technically capable of automatic log generation; Article 26(6) is the runtime obligation on the deployer to keep those logs.

What are the EU AI Act deployer obligations?

Article 26 sets out twelve paragraphs of deployer duties for high-risk AI systems, not all of which apply in every deployment. The runtime-facing duties most relevant to AI agents are: paragraph 1 (technical and organisational measures to use the system per the instructions for use), paragraph 2 (human oversight by competent natural persons), paragraph 4 (input data relevance and representativeness, to the extent the deployer controls the input), paragraph 5 (monitoring operation and informing the provider and market surveillance authorities of risks and serious incidents), paragraph 6 (6-month log retention). Additional duties apply conditionally: paragraph 7 (workplace notice to workers’ representatives and affected workers), paragraph 8 (EU-database registration for public-authority deployers), paragraph 9 (using Article 13 information to carry out a GDPR Article 35 data protection impact assessment where applicable), paragraph 10 (authorisation rules for post-remote biometric identification by law enforcement), paragraph 11 (notice to natural persons affected by Annex III decisions), and paragraph 12 (cooperation with competent authorities). This page covers the runtime-facing duties; check the official OJ text for the complete set.