What happened
On Sunday, August 2, a section of the EU AI Act called Article 50 becomes enforceable. It is the law's transparency layer, and it lands on ordinary businesses — not just the AI labs.
In plain terms: if a customer can talk to your AI, or read, see, or hear something your AI produced, you now have to say so.
The rule applies to any company whose AI reaches a person in the EU — including US businesses serving European customers — and breaches carry fines of up to €15 million or 3% of worldwide annual revenue, whichever is larger.
The AI Act has been on the books since 2024; August 2 is simply the day this particular obligation switches on. It is not a proposal or a consultation. It is a live compliance date.
The detail almost everyone will miss
Earlier this year, Europe agreed an "Omnibus" package that pushed its most demanding obligations far into the future. The rules for "high-risk" systems — hiring, credit scoring, critical infrastructure — moved to December 2027; the versions baked into regulated products slipped to 2028.
The coverage that followed was blunt, and for most readers it was the whole story: Europe delayed the AI Act.
But the one obligation that reaches almost every business — the duty to disclose AI — was left on its original August 2, 2026 date.
That is the trap. The delayed rules govern a narrow set of high-stakes systems most companies will never build. Article 50 governs the everyday stuff nearly everyone already runs: a support chatbot, a synthetic voice line, AI-written marketing copy, a generated product image.
The expensive, headline-grabbing part of the law got two more years. The cheap, universal part is the one arriving now.
Inside the rulebook, the demanding rooms — high-risk hiring, credit, infrastructure — were locked for two more years. The corridor everyone actually walks, the duty to say "this is AI," stayed open on schedule.
Why this matters if you run a business
Article 50 covers four concrete situations, and most operators sit inside at least one. A chatbot or voice agent that speaks with people must tell them they're dealing with a machine, unless it's already obvious. AI-generated images, audio, video, and text must be marked so they're detectable as synthetic. Emotion-recognition and biometric tools must notify the people they're used on. And deepfakes — plus AI-written text on matters of public interest — must be labeled as artificial.
If a customer can interact with your AI or read what it wrote, you now carry a disclosure duty — and the burden of proving you disclosed sits with you, not the regulator.
There is one partial reprieve, and it's easy to misread. The technical watermarking of synthetic content already on the market before Sunday gets a four-month grace period, to December 2.
The duty to tell someone they're talking to a bot does not get that grace — that one is live immediately.
What to do about it
You don't need a compliance department to clear this bar. Most of the work is plain disclosure you can add in an afternoon:
- Find where AI meets an outsider. Walk your customer touchpoints: the website chatbot, the voice system, the email assistant that hits "send," any AI images or copy you publish.
- Add the sentence. A plain line — "You're chatting with an AI assistant" — satisfies the direct-interaction rule. It costs nothing, and it's the thing a customer or a regulator can check in a single click.
- Label what your AI makes. Mark AI-generated media and public-facing text as artificial, and keep it visible rather than buried in a policy page.
- Push it onto your vendors. If a third party supplies your chatbot or content tool, get the disclosure and watermarking commitments in writing — you're the "deployer," so the duty lands on you regardless of who built it.
The parts of the AI Act that need lawyers were delayed. The part that needs a sentence was not — and Sunday is the day "tell people it's AI" stops being a courtesy and becomes the law.