EU AI Act Article 50 2026 Labelling Rules

A visible AI label does not automatically satisfy the separate technical marking requirement. If you run a chatbot or publish deepfakes, the transparency obligations generally apply from August 2, 2026, with duties depending on the role and content involved.
Separate the notice from the technical mark
Start by identifying the role you perform. Providers supply systems under their own name; deployers use systems under their authority. One organisation can be both.
Providers must design direct-interaction AI to identify itself no later than the first interaction, subject to a narrowly interpreted exception where its AI nature is obvious. They also have machine-readable marking duties for generated content. Deployers must disclose AI use in qualifying deepfakes and public-interest text. A technical mark does not automatically replace a disclosure people can perceive.

Compare the duties before choosing a label
In the original article on Injoys, you can compare responsibilities and exceptions in tables, with references to Commission guidance. The distinction between technical marking and visible disclosure helps clarify which requirement a proposed label addresses.
Read the full article on Injoys
Apply the review exception to the right content
Suppose you publish AI-generated text to inform the public about a matter of public interest. Check both parts of the possible disclosure exception:
- Human review or substantive editorial control has taken place, beyond a spell check.
- A person or legal entity holds editorial responsibility for publication.
Even where that exception applies, it does not remove the provider's machine-readable marking duty. Nor does human review automatically exempt a deepfake. Treat these as separate checks when assessing the same publication.
Article 50 scope and dates
If you operate outside the EU, check whether the system is supplied in the EU or its output is used there. Purely personal, non-professional use is outside deployer obligations; free or open-source status alone does not exempt a system.
For systems placed on the market before August 2, 2026, Article 50(2) obligations apply from December 2, 2026. This is a specific transition period, not a postponement of every transparency duty.
You can consult the official Article 50 FAQ referenced in the original article on Injoys to check the exception relevant to the intended use.
Read the full article on Injoys
This post was written with assistance and published on a channel run by Injoys (injoys.com). The original article and its sources are at the link above.
Comments
Post a Comment