You named it "AI Assistant." That's not the same thing as disclosing it.
A conversation I've had more than once: a team tells me their chatbot is already compliant with Article 50's disclosure duty because they named it something like “AI Assistant” or gave it a bio that says “I'm an AI.” It feels like disclosure. Somewhere, in some way, it says AI. The problem is that “somewhere, in some way” isn't the standard the Act is actually applying.
The standard is whether a reasonable user actually understood they were talking to an AI system, not whether a label existed somewhere on the page. A name is weak evidence of that, and weak evidence is exactly the kind of thing that doesn't hold up when someone actually checks.
It's worth being specific about why a name falls short, because the reasons map directly onto what Article 50 is actually asking for. Compliant disclosure needs to be shown before or at the first interaction, not something a user has to already know to look for in a header or a bio. It needs to be clear and distinguishable, not a word chosen as much for branding as for accuracy, sitting next to a friendly avatar and a human-sounding greeting designed to put the user at ease. And it needs to be accessible, which a name in a header frequently isn't if it's never actually read out or surfaced to the interaction itself. A name can be technically true and still fail every one of those, because a user can read “AI Assistant” at the top of a page and still not register, three messages into a conversation that feels natural, that they're talking to a model.
The reverse mistake is assuming the fix is to say it louder or more often, which is its own failure mode, covered in more depth in a separate post on disclosure frequency: repeat a disclosure on every single message and people tune it out within the first few exchanges, which defeats the point just as thoroughly as never saying it at all. What actually works is one of two patterns: a clear, non-dismissable notice at the start of the session followed by a small persistent badge for the rest of it, or the disclosure written directly into the AI's first reply. Both say it once, clearly, at the moment it matters, then get out of the way.
This is also why Disclarion's SDK doesn't just return a boolean saying disclosure is “handled.” It tells your frontend exactly when a disclosure is owed, on a session's first message, and ships a copy-paste modal + persistent badge component built around the pattern above, so the UI decision isn't left to whoever happened to pick the bot's name. A name was never going to be a reliable place to put a legal obligation. A one-time, session-aware notice is.
If your own chatbot's case for compliance currently rests on what it's called, that's worth revisiting before an auditor — or a user who never actually realized they were talking to a model — does it for you. For the fuller breakdown of what counts as compliant disclosure and the two patterns that hold up, see our chatbot disclosure guide.
More from the blog
Your internal AI tools owe the same disclosure duty the customer-facing one does
An HR bot or IT helpdesk assistant used only by your own staff still interacts with natural persons. Article 50 doesn't carve out an exception for "internal-only."
Does the EU AI Act apply if you're not based in the EU?
"We're a US company, we don't have an EU entity" isn't the exemption it sounds like. The actual test is about who's on the other end of the conversation, not your mailing address.
Why I built Disclarion as an SDK, not a dashboard
The easier product to build is a dashboard you configure after the fact. I built Disclarion to sit inside the AI call itself instead, and it's worth explaining why.
Deepfakes get a stricter rule than an AI-written blog post
Article 50(4)'s deepfake duty isn't the same obligation as ordinary AI content labeling — it applies to image, audio, and video specifically, and the built-in exemptions work differently too.
Your chatbot isn't the only thing that owes a disclosure under Article 50.
Article 50's disclosure duty doesn't stop at chatbots — emotion recognition and biometric categorization systems carry the same obligation, and they're the two system types teams miss most often.
Your editor touched it. Article 50's label exemption still might not apply.
Article 50(4) waives the visible AI-content label when a human takes substantive editorial responsibility for a piece — but a quick skim doesn't qualify, and the exemption doesn't touch the audit-trail duty underneath it.
You labeled the article. That's not the same thing as marking it.
Article 50(2)'s machine-readable marking and Article 50(4)'s visible label are two different duties. Images already meet the first one by accident. Article text usually doesn't meet it at all.
Your AI answers the phone now. There's no modal for that.
Article 50's disclosure duty doesn't go away because there's no screen. What actually discloses an AI voice agent on a phone call, when a modal isn't an option.
An AI audit trail doesn't need to know what your users actually said.
Teams hear "audit trail" and picture a database of every conversation. Article 50's version is narrower: it has to prove disclosure and labeling happened, not repeat what was said.
Article 50 skips disclosure when it's "obvious from context." That word is doing more work than it looks like.
Disclosure isn't required when AI use is obvious from context, but Article 50 never defines obvious, and most of the cases teams assume qualify, don't.
Your chatbot needs to disclose it's an AI. Once, not every message.
Disclosing a chatbot is AI sounds simple until you build it: repeat it every message and people tune it out, show it once and later visitors never see it.
You have logs. That's not the same thing as an audit trail.
Under Article 50, an audit trail has to be insert-only, complete, and producible on demand, not a data-engineering project when a regulator actually asks.
Your AI-generated content needs a label. Here's what that actually means.
A disclaimer someone remembers to add isn't a labeling system. Under Article 50, AI-generated content needs to be identifiable as such, reliably, not as a manual step someone can forget.
EU AI Act Article 50, explained: who it affects and what it requires
Article 50 of the EU AI Act has been enforceable since August 2, 2026: who it applies to, its three obligations, and the penalties for getting it wrong.