The EU AI Act for Marketing Agencies: The 2026 Compliance Checklist
The EU AI Act (Regulation (EU) 2024/1689) primarily obligates marketing agencies as deployers (Art. 26), and as providers (Art. 25) when they adapt their own models or carry out white-label rebranding. Core duties are AI literacy (Art. 4, since 2 February 2025), labelling AI-generated content (Art. 50) and a documented AI inventory with risk classification.
Key Takeaways
- ✓Under the EU AI Act, agencies are almost always deployers (Art. 26) — but through fine-tuning, white-label rebranding or a change of purpose they can tip into the provider role (Art. 25), with full Annex IV documentation obligations.
- ✓Two obligations already apply now: AI literacy (Art. 4, since 2 February 2025) and the prohibition of certain practices (Art. 5, since 2 February 2025). Neither has been postponed by the Digital Omnibus.
- ✓From 2 August 2026, Art. 50 requires the labelling of AI-generated content; the technical watermarking/labelling solutions must be operational by 2 December 2026 (as of 2026, subject to change).
- ✓Fines range from EUR 7.5 million / 1.5% (including Art. 4 literacy) through EUR 15 million / 3% (Art. 26 deployer, Art. 50 transparency) up to EUR 35 million / 7% (Art. 5 prohibited practices).
- ✓A tick-box compliance checklist comprises six blocks: AI inventory, risk classification, AI literacy, Art. 50 labelling, contracts/sub-processors and documentation.
- ✓Persuasion-optimised marketing agents that exploit cognitive biases below the threshold of conscious awareness can fall under the prohibition in Art. 5(1)(a) — the most severe sanction tier.
The EU AI Act (Regulation (EU) 2024/1689) does not classify marketing agencies as a category of their own in law — it recognises neither the term "agency" nor "AI agent". What matters is your role: almost every DACH agency is a deployer under Art. 3(4), because it uses AI systems under its own responsibility. It becomes a provider under Art. 3(3) via Art. 25 only in narrowly defined cases. The obligations follow from this.
- Default role of deployer: obligations under Art. 26 (oversight, monitoring, logging) plus Art. 4 AI literacy and Art. 50 transparency.
- Already in force: AI literacy (Art. 4) and the prohibitions (Art. 5) have applied since 2 February 2025 — regardless of risk and not postponed.
- Labelling obligation: AI-generated content and deepfakes must be disclosed under Art. 50 from 2 August 2026 (technical solutions by 2 December 2026).
What role does a marketing agency have — deployer or provider?
The AI Act distinguishes the operator roles in Art. 3(3)–(8). Two are relevant for agencies:
A deployer (Art. 3(4)) is anyone who uses an AI system under their own authority. This is the default role for almost every agency that uses ChatGPT Enterprise, Claude for Work, Microsoft 365 Copilot, Gemini for Workspace or a managed RAG service for copywriting, campaigns, customer service or knowledge management. As long as you use the system for its documented purpose, do not fine-tune or substantially modify the underlying model, do not rebrand it and do not repurpose it towards a new high-risk use, you remain a pure deployer.
A provider (Art. 3(3)) is anyone who develops an AI system or places it on the market under their own name. Via Art. 25, a deployer can tip into this role — with considerable consequences. Three triggers:
- Rebranding (Art. 25(1)(a)): you offer a white-label chatbot system under your own brand. According to the Commission guidelines, a contractual allocation cannot override this. For agencies that resell white-label chatbots, the Art. 50(1) disclosure obligation then becomes your obligation.
- Substantial modification (Art. 3(23), Art. 25(1)(b)): for example, fine-tuning a third-party LLM on proprietary data in a way that affects compliance under Art. 8–15.
- Change of purpose to high-risk (Art. 25(1)(c)): for example, a model fine-tuned on CV data for candidate selection — this is Annex III(4) high-risk, and the agency becomes a provider.
Standard RAG over your own documents, prompt engineering and system-prompt adjustment typically do not trigger Art. 25. Likewise, light LoRA fine-tuning below roughly a third of the original training compute remains under the GPAI threshold set out in the Commission guidelines of 18 July 2025.
The compliance checklist for marketing agencies
The following tick-box checklist bundles the core deployer obligations. It is based on the blueprint "Mittelstand deployer of managed-API agents" from the underlying research.
# | Obligation block | Concrete measure | Legal anchor | Deadline / status |
|---|---|---|---|---|
1 | AI inventory | Use-case register: record every AI application with its purpose, owner and oversight role | Best practice for meeting Art. 26 (monitoring, oversight) | ongoing |
2 | Risk classification | Assess each use case against Art. 5 (prohibited), Annex III (high-risk), Art. 50 (transparency); document the reasoning under Art. 6(3)/(4) | Art. 6, Art. 6(3), Art. 6(4) | ongoing |
3 | AI literacy | Role-based, German-language training programme; document completions; refresh annually | Art. 4 | in force since 2 Feb. 2025 |
4 | Art. 50 labelling | Chatbot notice, AI-content labels, deepfake labelling; document exemption analysis | Art. 50(1)–(4) | substantive from 2 Aug. 2026; technical by 2 Dec. 2026 |
5 | Contracts / sub-processors | Vendor due diligence: provider compliance, GPAI Code of Practice signature, Annex XII documentation, Art. 25 allocation, Art. 73 escalation, GDPR data residency | Art. 13, Art. 25, Art. 73 | before deployment |
6 | Documentation | Logging with at least 6 months' retention; monitoring KPIs; escalation/suspension path; designate oversight roles | Art. 26(2), (5), (6) | substantive from 2 Aug. 2026 |
Two DACH-specific points to add: where an AI application affects employees (for example, a productivity-monitoring copilot), Art. 26(7) applies, with works council or staff representation consultation before commissioning — in Austria via §§ 91, 96 ArbVG. And against shadow AI (private ChatGPT use in the browser that bypasses the governance model), an acceptable-use policy helps, backed by network and identity controls.
The state of the deadlines in 2026 — and what already applies
The Digital Omnibus (political agreement of 7 May 2026) postpones the bulk of the high-risk obligations: Annex III high-risk now applies from 2 December 2027, and Annex I product safety from 2 August 2028 (as of 2026, subject to change). Importantly: this postponement has not yet been formally adopted. Until it is adopted — promised before 2 August 2026 — the original date of 2 August 2026 remains the legally binding default.
Not postponed are: Art. 4 (literacy) and Art. 5 (prohibitions) since 2 February 2025, the GPAI rules (Art. 51–55) since 2 August 2025, and the fine framework. Art. 50 transparency starts substantively on 2 August 2026; only the technical implementation grace period was shortened to three months and ends on 2 December 2026.
Prohibited practices in marketing (Art. 5)
Agencies should take Art. 5 seriously — this is where the highest sanction tier lies. The research cites three marketing-relevant prohibitions:
- Art. 5(1)(a): subliminal, manipulative or deceptive techniques causing significant harm — for example, persuasion-optimised marketing agents that exploit cognitive biases below the threshold of conscious awareness.
- Art. 5(1)(b): exploiting vulnerability on the basis of age, disability or socio-economic situation — e.g. agents that target older customers with predatory financial products.
- Art. 5(1)(g): biometric categorisation based on sensitive attributes — relevant for targeting and segmentation agents.
In addition, the Digital Omnibus added a ninth prohibition for AI-generated non-consensual intimate content, with a deadline to remove non-compliant systems by 2 December 2026 (as of 2026, subject to change).
Example scenario with figures: a 60-person agency in Vienna
An owner-managed performance marketing agency with 60 employees uses four AI applications: a copywriting agent (internal), a customer service chatbot on its own website, a code-generation assistant and, occasionally, AI-generated product videos for campaigns.
Classification according to the research:
- Copywriting agent: minimal + Art. 50(2) labelling of the outputs (synthetic content).
- Customer service chatbot: limited risk, Art. 50(1) — disclosure that "you are chatting with an AI assistant".
- Code generation: minimal (internal use).
- Product videos: limited risk + Art. 50(4) deepfake disclosure in full; the artistic-satirical exemption is interpreted narrowly.
Effort (scaled to research figures): the blueprint cites 4–6 months of project duration and a budget of EUR 80,000–250,000 for a 500-person mid-sized company. For the 60-person agency, the realistic effort lies at the lower end or below — the focus shifts to the AI literacy programme (3–5 modules are typically sufficient for an operation of this size), the use-case register, the design of the Art. 50 disclosures and the vendor due diligence.
Risk of doing nothing: if, for example, the deepfake labelling were omitted, this would fall into the second fine tier under Art. 99 — up to EUR 15 million or 3% of worldwide annual turnover. As this is an SME, Art. 99(6) applies: the lower of the two amounts governs. With an annual turnover of EUR 6 million, 3% equals EUR 180,000 — so the cap here would be EUR 180,000 rather than EUR 15 million. A lack of AI literacy (Art. 4, third tier) is measured at 1.5%, so here up to EUR 90,000. The investment in compliance is therefore smaller than the exposed fine risk.
For agencies and B2B decision-makers
Anyone using AI productively in marketing is already under obligation today: AI literacy and the prohibition of manipulative practices have applied since February 2025, and the labelling of AI-generated content follows in 2026. The fastest lever is a documented AI inventory with clean risk classification — from which follow your training needs, labelling obligations and the question of whether you slip into the provider role under Art. 25 anywhere. Blck Alpaca supports agencies and B2B teams across the DACH region in building this inventory, implementing the Art. 50 labelling and establishing an audit-proof AI literacy programme.
Legal notice: This article serves as professional orientation and does not constitute legal advice. For a binding assessment of your specific individual case, please seek specialised legal advice.
FAQ
Is a marketing agency a deployer or a provider under the EU AI Act?
Must an agency label AI-generated marketing content?
Since when does the AI literacy obligation apply to agencies?
What fines do agencies face under the EU AI Act?
Can a marketing agent fall under a prohibition in Art. 5?
Want to go deeper?
Get new analyses straight to your inbox – or see how we put this knowledge to work for companies.