The EU AI Act’s big enforcement moment was August 2, 2026. Most developers who saw the headlines concluded: deadline came, nothing happened, moving on. That read is wrong. High-risk AI compliance — the part with the heavy documentation burden — was postponed. But Article 50 transparency obligations went live, and they apply right now to every chatbot, AI agent, and AI content pipeline that reaches EU users.
What Actually Went Live on August 2 #
The EU AI Act has been rolling out in phases. The phase that landed August 2 covers two things: Article 50 transparency requirements and the European Commission’s enforcement powers over general-purpose AI models. That’s it. The high-risk AI framework under Annex III — the part covering hiring tools, credit scoring, healthcare systems — was pushed to December 2027 under the Digital Omnibus agreement.
Article 50 is narrower, but it’s not trivial. It covers four categories of AI use: interactive systems (chatbots, agents), synthetic content generation, emotion recognition and biometric categorization, and AI-generated content published on matters of public interest. If your product touches any of those, you have compliance work to do — not in six months, right now. The European Commission confirmed enforcement began August 2 with no grace period for Article 50.
The Chatbot Rule Is a UX Requirement, Not a Legal One #
Under Article 50(1), any AI system designed to interact directly with users must inform them they’re talking to AI. The disclosure must happen at the first point of contact — not buried in a terms-of-service page, not as a one-time modal the user can dismiss and forget. A persistent banner at the start of the session, or a clear first message, is what compliance looks like.
There is a carve-out for interactions where AI involvement is “already obvious.” Don’t count on it. The standard for obvious is a “reasonably well-informed, observant and circumspect person.” A chat window labeled “Chat with us” doesn’t qualify. Neither does a support widget with a friendly avatar. The bar is much closer to “the interface explicitly says ‘You are talking to an AI.'”
If your customer support chatbot, onboarding assistant, or AI agent doesn’t surface a clear AI disclosure before the first exchange, that’s a bug in your product — and now it’s also an enforcement risk.
AI-Generated Content: Two Deadlines to Track #
Article 50(2) covers generative AI outputs: images, video, audio, and text produced or substantially modified by AI. Here the rules split across two timelines.
Human-readable disclosure— Required now for all new AI-generated content. A visible label identifying the content as AI-generated. What fails: metadata only, small-print attribution, labels that disappear when content is shared. What works: visible indicators baked into images, audible disclosures at the start of audio, persistent labels in video.Machine-readable markers— Embedded watermarking and provenance data. Grace period until** December 2, 2026**for systems already on the market before August 2. New systems have no grace period. Standards are still being finalized through the EU AI Office’s Code of Practice.
The distinction matters operationally: you can defer watermarking tooling to Q4, but visible labeling for new content is live today.
Your Location Doesn’t Matter #
Article 50 applies based on where your users are, not where you are. A developer in San Francisco shipping a chatbot used by people in Germany falls within scope. A team in Singapore running an AI content pipeline with EU readers is covered. Penalties reach up to €15 million or 3% of your global annual turnover — whichever is higher.
The provider/deployer distinction also matters here. If you build the AI system, you’re the provider — responsible for building disclosure into the system by design. If you’re a business deploying a third-party AI tool, you’re the deployer — responsible for ensuring user-facing notifications are in place. Both roles carry obligations.
What’s Still Coming #
If you build AI tools for hiring, healthcare, credit assessment, or critical infrastructure, the heavy compliance burden isn’t here yet. The Digital Omnibus agreement pushed high-risk AI obligations under Annex III to December 2, 2027 for standalone systems, and August 2, 2028 for AI embedded in regulated products. The substantive requirements haven’t changed — risk management systems, technical documentation, logging, human oversight — only the deadlines moved. The December 2, 2026 machine-readable marking deadline is the next near-term milestone for most developer teams. Start scoping watermarking and provenance tooling now — the Code of Practice standards will finalize with less runway than the August date provided.
The Practical Step Right Now #
Audit every AI touchpoint in your product that a user interacts with or encounters. For each one, ask: does it disclose that it’s AI, at the moment of interaction, clearly enough that a non-technical person would notice? If the answer is no — or “I think so, but I’m not sure” — that’s where to start. The legal analysis can follow. The UI fix can’t wait.
A full implementation breakdown is available in the Article 50 developer implementation guide from CoderCops, which covers chatbot, content, and biometric system checklists in practical detail.