← Go back

Guide · CompanionGuard · Published 14 November 2026 · Reviewed 14 November 2026 · By the Ingenious AI team

EU AI Act Article 50: Transparency Duties for Companion Chatbots

The short answer

Per CompanionGuard's own summary: EU AI Act Article 50 transparency duties have applied since 2 August 2026, and the legacy grace period ends 2 December 2026. For a companion chatbot the practical core is the same act the US packs require — tell users they are interacting with an AI. CompanionGuard's disclosure snippet, hosted protocol page and runtime disclosure state are the mechanisms a builder points to. This page is the toolkit's summary, not legal advice on EU law.

What is Article 50 transparency for a chatbot?

In the product's framing, Article 50 is the EU AI Act's transparency layer for AI interaction: people must be able to tell they are dealing with an AI system. For companion bots — products designed to feel personal — that duty cuts against the design grain, which is precisely why it exists and why a bolt-on banner written to satisfy it must survive contact with the persona, in conversation and on request.

Create the free safety kit Next guide All guides

CompanionGuard is built by Ingenious AI. A compliance toolkit — not legal advice and not a clinical service. If you are in crisis right now: US — call or text 988; UK & Ireland — Samaritans 116 123.

The dates, as the product states them

CompanionGuard's llms summary puts the European timeline in one sentence: 'EU AI Act Article 50 transparency duties have applied since 2 August 2026 (the legacy grace period ends 2 December 2026)'. Two facts in that sentence do operational work. The duties are not upcoming — they have applied since August 2026, so a European-facing companion without disclosure is not early, it is late. And the grace period for legacy systems ends 2 December 2026, weeks after this guide's publication — the last of the three regimes' deadlines to fall, and the one most likely to catch builders who treated Europe as a future problem.

Set beside the US packs — California operative since 1 January 2026, Colorado joining 1 January 2027 — the pattern is a pincer: by the start of 2027, disclosure duties are live on both sides of the Atlantic, in the three regimes this product tracks. The 2027 roadmap guide lays the three timelines on one calendar.

What a transparency duty means for a companion specifically

Companions are the hard case for transparency because the product fantasy is a relationship. A user who believes — even playfully, even half-knowingly — that the bot is a someone will disclose more, trust more and be harmed more when the fiction cracks. Article 50's logic, like SB 243's, is that the user is entitled to the fact of the matter at the point of interaction, not in a policy PDF.

For builders, the engineering reading is the same trio this product implements everywhere: a banner at first interaction (the disclosure snippet), disclosure that survives in conversation (tested by the scenario set's identity probes and secrecy scenarios), and a public page stating what the bot is (the hosted protocol page). The EU framing adds emphasis, not new machinery — which is the good news hidden in the deadline: a kit built for the strictest US pack is most of the way to the European duty as the product summarises it.

Grace periods end; evidence remains

The 2 December 2026 grace expiry changes the question a reviewer asks. During a grace period, 'we are implementing' is an answer; after it, the question is 'show me disclosure operating'. CompanionGuard's runtime disclosure state — disclosure_required returned until disclosure is shown, the satisfaction sealed in the evidence chain with a timestamp — converts implementation claims into per-session facts, which is the dialect postures change to once grace ends.

Builders still inside their implementation window should sequence by evidence value: banner first (visible, immediate), protocol page second (public, linkable), runtime state third (per-session proof), all before December so the chain accumulates history across the deadline rather than starting after it. A chain that begins 1 December tells a story about November that no one wants told about them.

What this page cannot tell you

Three honest limits. This is a toolkit vendor's summary, written to explain which product mechanisms map to the duty — it is not EU legal advice, and Article 50's full scope (which systems, which exemptions, which member-state enforcement practice) is a counsel question. The product says the same about itself everywhere: a compliance toolkit, not legal advice. Second, transparency is one duty among the Act's many; nothing here speaks to risk classification, data governance or other obligations your system may carry. Third, summaries age: verify the current state of the Act's application timeline before relying on any date in this guide.

What survives those limits is the direction of travel, identical in Sacramento, Denver and Brussels: users are told, at the interaction, that the companion is an AI. Builders who implement that once, well, and with evidence, are building for all three regimes at the same time.

Five actions before the grace period ends

  1. Confirm your European-facing bot shows the disclosure banner at first interaction today — the duty has applied since 2 August 2026, per the product's summary.
  2. Test in-conversation identity handling with the scenario set's probes: asked directly, the bot must disclose, not perform.
  3. Publish your hosted protocol page and link it from your European entry points, so the transparency statement is public and stable.
  4. On Pro or Team, ensure disclosure state is tracked per session so post-December reviewers get per-session facts, not intentions.
  5. Have counsel verify your Article 50 position against the current Act text; use this guide and the product's summary as engineering input, never as the legal conclusion.

Worked example: a December deadline met in October

A fictional companion studio, Hausfreund, sells a friendship bot with a meaningful German user base. Reading the product's timeline in October 2026, they treat 2 December as their internal launch date for 'transparency, evidenced'. Week one: the snippet goes live for all locales (the banner's resource line stays locale-matched; the disclosure itself translates with their existing localisation). Week two: the protocol page is linked from their EU storefront pages.

Week three, on Pro: the runtime starts tracking disclosure state, and the first export shows disclosure satisfied in 12,408 of 12,408 sessions — including 214 sessions restored after app crashes, where the state machine correctly re-required disclosure instead of assuming it. When December arrives, their evidence chain already spans six weeks of European sessions. The story is invented; the dates and mechanisms are the product's own summary.

Frequently asked questions

When did EU AI Act Article 50 duties start applying?

Per CompanionGuard's summary: Article 50 transparency duties have applied since 2 August 2026, and the legacy grace period ends 2 December 2026.

What does Article 50 require of a companion chatbot, in this product's framing?

Transparency about AI interaction: users must be able to tell they are dealing with an AI. CompanionGuard's corresponding mechanisms are the disclosure snippet at first interaction, in-conversation disclosure behaviour tested by scenarios, a public protocol page, and per-session disclosure state in the runtime.

Is this guide legal advice on the EU AI Act?

No. It is a toolkit vendor's summary explaining product mechanisms, and CompanionGuard states it is a compliance toolkit, not legal advice. Article 50's full scope and your obligations under the Act are questions for counsel, verified against the current text.

How does Europe interact with the California and Colorado duties?

The three regimes converge on the same core act — disclose AI nature at the interaction — on different dates: California operative 1 January 2026, EU duties applied 2 August 2026 with grace ending 2 December 2026, Colorado joining 1 January 2027. Building disclosure once, with evidence, serves all three.

What changes when the grace period ends?

The review question shifts from implementation intent to operating evidence. Runtime disclosure state — disclosure_required until shown, satisfaction sealed per session — is the kind of artefact that answers the post-grace question.

Keep going