Is Your Chatbot "Limited Risk"? New Transparency Rules for 2026
Is Your Chatbot “Limited Risk”? New Transparency Rules for 2026

Is Your Chatbot “Limited Risk”? New Transparency Rules for 2026

Transparency & Chatbots · 9 min read · Updated March 2026

Most organisations assume their chatbot is “just a chatbot” — a helpful widget that doesn’t attract serious regulatory attention. The EU AI Act disagrees. From 2 August 2026, Article 50 imposes mandatory transparency and labeling obligations on a broad range of conversational AI systems, AI-generated content tools, and emotion-recognition applications — regardless of whether they are classified as high-risk. This guide explains exactly which chatbots and AI systems fall under Article 50, what you must disclose, and how to comply.

Key Takeaways
  • “Limited Risk” is not the same as “no risk” — it means specific transparency obligations apply, enforced with the same penalty regime as high-risk violations.
  • Article 50 transparency duties apply to chatbots, deepfake generators, AI-generated text publishers, and emotion-recognition systems — even if none of these are classified as high-risk.
  • The deadline is 2 August 2026. With the Transparency Code of Practice Draft 2 now published (March 2026), the technical specifications for compliance are clear.
  • Many businesses are unknowingly operating chatbots that will require retroactive UI changes, updated terms of service, and new disclosure workflows before August 2026.

1. The EU AI Act’s Four Risk Tiers: Where “Limited Risk” Sits

The EU AI Act classifies AI systems into four tiers based on potential harm. “Limited Risk” is the third tier — below Unacceptable Risk (prohibited) and High Risk (full conformity obligations), but above Minimal Risk (no mandatory requirements).

Unacceptable Risk — Prohibited outright (Art. 5)
~1% of AI systems
High Risk — Conformity assessment, documentation, registration (Annex III)
~8–10%
Limited Risk — Transparency obligations only (Art. 50) ← YOU ARE HERE
~15–20%
Minimal Risk — No mandatory obligations
~70%

The “Limited Risk” label is slightly misleading — it refers to the level of mandatory compliance obligations, not the level of potential harm. The AI systems in this tier (chatbots, deepfake generators, AI content publishers) can cause significant social harm through manipulation and disinformation. The legislature’s response was not to impose technical conformity obligations, but to require transparent disclosure — ensuring users always know when they are interacting with AI.

⚠️
Penalty exposure is real: Article 50 violations are enforceable with fines of up to €15,000,000 or 3% of global annual turnover — the same penalty band as most high-risk AI violations. “Limited Risk” does not mean limited consequences.

2. Article 50: The Four Transparency Obligations in Full

Article 50 of the EU AI Act contains four distinct transparency obligations, each targeting a different type of AI system or content. They operate independently — your system may trigger one, two, three, or all four simultaneously depending on what it does.

Art. 50 ClauseAI System TypeObligationWho Must Act
50(1)Chatbots & conversational AIInform users they are interacting with AI — in the first interactionProviders & Deployers
50(2)Deepfakes & synthetic mediaMachine-readable label declaring content is AI-generatedOperators distributing content
50(3)AI-generated text on public-interest topicsHuman-readable disclosure of AI authorship to audiencePublishers & platforms distributing AI text
50(4)Emotion recognition AINotify individuals that emotion inference is operatingDeployers

3. Chatbots and Conversational AI: What Must Be Disclosed

Article 50(1) requires that providers and deployers of AI systems designed to interact with natural persons must ensure those persons are informed they are interacting with an AI system — unless this is obvious from the context or circumstances of use.

What counts as a “conversational AI system” for Article 50(1)?

✅ In scope
  • Customer service chatbots on websites or apps
  • AI assistants embedded in SaaS platforms
  • Voice assistants with conversational capability
  • AI-powered live chat tools
  • AI customer agents in messaging apps (WhatsApp, Messenger bots)
  • AI email response systems that interact personally
✓ Likely out of scope
  • Simple menu-driven IVR systems (not AI-driven)
  • Search engines returning AI-sorted results (no dialogue)
  • Internal enterprise AI tools not interacting with the public
  • AI tools in creative applications where AI nature is obvious from product positioning

What must the disclosure look like?

Article 50(1) does not prescribe the exact format — but the Transparency Code of Practice Draft 2 (March 2026) provides guidance. The disclosure must:

Appear in the first interaction — before the user has engaged meaningfully with the AI. Not buried in terms of service, not disclosed only after the user asks, not relegated to a “Help” section.
Be clear and unambiguous — acceptable language: “You are chatting with an AI assistant”, “This is an automated AI system”, “Hi, I’m [Name], an AI”. Unacceptable: vague indicators like a small robot emoji with no accompanying text, or AI disclosure only in the UI footer.
Be persistent or re-stated — for long-running sessions (over 30 minutes, or with significant time gaps), the disclosure should be re-surfaced. A user returning to a chat after two days should be reminded they are interacting with AI.
Be accessible — the disclosure must be understandable to the average user of your service. For consumer-facing chatbots, plain language is required. Technical descriptions of the underlying LLM are insufficient as the sole disclosure.
The “obvious from context” exception is narrow
Article 50(1) has one exception: the disclosure is not required where it is “obvious from the circumstances and context of use” that the user is interacting with AI. Regulators will interpret this narrowly. The exception covers situations like: a product branded explicitly as an AI assistant (e.g. “ChatGPT by OpenAI”), developer tools where users obviously know they are interacting with an API, or B2B platforms where all users are professionals trained to understand they are using AI tools. It does not cover a generic customer service widget just because some users might assume AI is involved.

4. Deepfakes and Synthetic Media: The Labeling Requirements

Article 50(2) requires that AI-generated images, video, audio, and other content that resembles existing persons, objects, places, or other entities must carry a machine-readable disclosure that the content is AI-generated. This applies to both the AI tool provider and the operator distributing the content.

The C2PA Content Credentials standard has been adopted as the technical implementation pathway in the Transparency Code of Practice Draft 2 — giving operators a concrete technical specification to implement. Machine-readable labels must travel with the file and be preserved through sharing and downloading.

Content TypeMachine-Readable LabelHuman-Visible LabelAdditional Requirement
AI-generated images of real peopleC2PA credentials in EXIF/XMPEU AI Icon in cornerNamed person disclaimer if identifiable
AI-generated video (deepfakes)C2PA in video containerEU AI Icon persistent throughoutNamed disclaimer for identifiable real persons in fictional scenarios
AI-generated audio / voice cloningC2PA in audio metadataEU AI Icon in platform listingSpoken disclosure at audio start for voice-cloning cases
AI-generated fictional imagery (no real persons)C2PA credentialsEU AI Icon recommendedNone additional

5. AI-Generated Text: The Public-Interest Content Rule

Article 50(3) addresses AI-generated text published for public consumption on topics of public interest — including news, politics, health, science, and elections. Publishers and platforms distributing such content must clearly disclose its AI-generated nature to their audience.

The Transparency Code of Practice Draft 2 defines the threshold as content that is more than 50% substantively AI-generated without human editorial revision. Minor AI-assisted editing of human-authored text does not trigger the obligation — it is intended to capture primarily or substantially AI-authored content.

What counts as “public interest topics”?
The Act does not exhaustively define public-interest topics, but the committee debates and the Transparency Code make clear this covers: news reporting, political and election-related content, public health information, scientific reporting, economic and financial news, legal and regulatory developments, and social commentary. It explicitly does not cover entertainment content, commercial product descriptions, fiction, or internal business communications.
Required disclosure format
The disclosure must include: a human-readable statement (e.g. “This article was generated by AI” or “AI-assisted content”) appearing at the top of the article or in a clearly visible byline area; the EU AI Icon adjacent to the content; and Schema.org markup in the page HTML identifying the content as AI-generated. For news publishers using CMS platforms, this requires CMS-level template changes and editorial workflow updates.

6. Emotion Recognition: The Notification Requirement

Article 50(4) requires that persons exposed to AI systems that infer emotional states from biometric data must be informed that emotion recognition is operating. This obligation falls on the deployer — the organisation operating the emotion recognition system.

Note the overlap with Article 5 prohibitions: emotion recognition AI in workplaces and educational institutions is prohibited outright under Article 5(1)(f) (with narrow exceptions for safety/medical purposes). Article 50(4) covers emotion recognition in other contexts — retail, healthcare (with consent), entertainment, and research — where the use is not prohibited but notification is required.

⚠️
Check Article 5 first: Before implementing Article 50(4) notification procedures for your emotion recognition system, confirm that your specific use case is not prohibited under Article 5(1)(f) (workplace and educational contexts). If it is prohibited, no amount of notification makes it compliant. Use our free risk assessment tool to check your classification.

7. Exceptions: When Article 50 Does Not Apply

Article 50 contains several exceptions. Most are narrow — regulators will interpret them conservatively.

ExceptionArticleApplies toPractical scope
“Obvious from context”50(1)Chatbot disclosurePurpose-built AI products; developer tools; B2B professional contexts. Very narrow — does not cover consumer-facing chatbots.
Authorised law enforcement50(2)Deepfake labelingLaw enforcement operations using synthetic media for investigative purposes with judicial authorisation
Artistic & satirical content with clear disclosure50(2)Deepfake labelingClearly labelled satire, parody, fiction. The artistic nature must be apparent — not a defence used to avoid labeling harmful deepfakes.
Minor AI assistance50(3)Text disclosureAI-assisted editing of primarily human-authored text. Under 50% AI-generated (per Draft 2 Code of Practice threshold).

8. Practical Compliance Steps for Each Obligation

For chatbot and conversational AI operators
  • Add a clearly worded AI disclosure in the first message or interface header of every AI chat interface before August 2026
  • Audit every chatbot widget across your website, app, and messaging integrations — document each one
  • Update terms of service to reference AI interaction, but do not rely on ToS as the sole disclosure mechanism
  • For session-resuming chats, implement a session-gap re-disclosure trigger (e.g. after 24 hours)
For synthetic media and image/video generation
  • Implement C2PA credential generation as a default output of your image and video generation pipeline — not opt-in
  • Obtain the official EU AI Icon vector from the EU AI Office and integrate it into your content rendering pipeline
  • Ensure your content distribution channels (website, social, email) do not strip C2PA metadata on upload/publish
  • Brief your content team on the 50% AI-authored threshold and when text disclosure is required
For publishers and platforms distributing AI-generated content
  • Update your CMS article templates to include AI authorship disclosure fields and the EU AI Icon display
  • Add Schema.org CreativeWork markup to article pages identifying AI-generated content
  • Create an editorial policy defining what level of AI assistance requires disclosure
  • Train editorial teams on the >50% substantive AI generation threshold
See Article 50 in your compliance programme
Article 50 transparency items are covered in Phase 3 of our compliance checklist — with implementation specs aligned to the Transparency Code of Practice Draft 2.
View Compliance Checklist →

9. Frequently Asked Questions

Does Article 50 apply if our chatbot only uses AI to classify the user’s intent but a human handles the response? +
If the AI system only classifies or routes the conversation and a human writes the response, Article 50(1) is less likely to apply — the interaction is fundamentally with a human, not an AI. However, if the classification is itself communicated to the user (e.g. “I’ve detected you have a billing query and have routed your message to the billing team”), this could be considered a form of AI interaction requiring disclosure. The safest approach is to disclose AI involvement wherever AI plays any communicative role with the end user.
Our chatbot is B2B only — do we still need to add an AI disclosure? +
Article 50(1) applies to AI systems that interact with “natural persons” — it does not distinguish between B2B and B2C contexts. If individual users of your B2B platform interact with a conversational AI, the disclosure obligation applies to those individuals. The “obvious from context” exception is more likely to apply in professional B2B settings where all users are trained experts who know they are using an AI tool — but this must be documented and cannot be assumed.
What are the penalties for failing to comply with Article 50? +
Article 50 violations are penalised under the EU AI Act’s second-tier penalty band — up to €15,000,000 or 3% of global annual turnover, whichever is higher. For context, this is the same penalty band as violating most high-risk AI obligations. It is more severe than GDPR’s standard penalty tier (€10M / 2% for most violations). National market surveillance authorities can also order the AI system or content to be withdrawn until compliant. See our full breakdown of EU AI Act penalties.
Leave a Reply

Your email address will not be published. Required fields are marked *

You May Also Like