The European Commission’s June 10, 2026 Code of Practice gives AI companies a more concrete framework for labels, markings, and disclosures before the EU AI Act’s Article 50 transparency duties start applying on August 2, 2026. The code is voluntary, but the underlying obligations are not: providers and deployers will have to make certain AI interactions, synthetic media, deepfakes, and AI-generated public-interest text identifiable to users.
That turns AI transparency from a trust slogan into product work. A chatbot notice, machine-readable marker, deepfake disclosure, export watermark, or publication label has to be designed, placed, tested, localized, logged, and maintained. The hard question is no longer whether to disclose AI use in the abstract. It is when the label must appear, what it should say, who is responsible for it, and how it survives as content moves between services.
What Article 50 Covers
The AI Act entered into force in 2024, with obligations phased in over several years. Prohibited AI practices and AI literacy duties began applying in 2025. General-purpose AI model obligations followed in 2025. The transparency rules many users will actually see arrive on August 2, 2026.
Article 50 covers several situations. Users must be informed when they are interacting with an AI system unless that is obvious from the context. Providers of generative AI systems must make AI-generated or manipulated content detectable, including through machine-readable marking where technically feasible. Deployers must clearly label deepfakes and AI-generated or AI-manipulated text published to inform the public on matters of public interest, with exceptions such as human review and editorial responsibility.
The Commission’s code splits the work across the AI value chain. Providers are pushed toward technical marking and detection. Deployers are pushed toward user-facing labels for deepfakes and certain public-interest text. That split matters because the model provider, app developer, publisher, social platform, and end user may all be different actors.
The Code Is Voluntary, The Duties Are Not
The Code of Practice does not replace the AI Act or the Commission’s coming guidelines. It is meant to give providers and deployers a recognized practical framework for compliance. The Commission says organizations that sign the code may be able to rely on its measures to demonstrate compliance after a positive assessment, while those using other methods will need to show that their approach is adequate.
That distinction matters for product teams. A company can ignore the code and build its own compliance path, but it still has to solve the same operational problems: technical marking, label placement, detection reliability, accessibility, language coverage, records, and responsibility when content is generated in one product and distributed in another.
The code also points to a more standardized label environment. The EU has published icons deployers may use, and signatory task forces are expected to share implementation practices. The likely result is not one universal AI badge, but a move away from entirely ad hoc disclosure language.
Why Labels Are A Design Problem
A useful AI label answers a question at the moment of possible confusion: am I dealing with a person, an automated system, a synthetic image, a manipulated video, or public-interest text produced with AI? If the answer is buried in a policy page, footer, or generic terms-of-service link, it will not do the work regulators are asking it to do.
That means transparency belongs inside design systems. Chat products need a persistent way to identify automated responses and escalation to a human. Image and video tools need export behavior, metadata choices, visible labels, and removal rules. Publishing, newsletter, customer-service, and productivity tools need thresholds for when AI assistance becomes disclosure-worthy output.
The hardest cases are in the middle. A spelling fix, translation, crop, or formatting suggestion does not carry the same risk as a synthetic video of a public figure or an AI-generated article about an election. Labels that appear too rarely mislead users. Labels that appear on every minor assistive feature become background noise. The product work is drawing the line consistently and explaining it clearly.
Deepfakes Are The Clearest Test
Deepfakes are the easiest category for users to understand and one of the hardest for platforms to enforce. AI-generated or manipulated audio, images, and video can make people appear to say or do things they never did, with risks for elections, scams, harassment, reputational harm, and public trust.
A visible label alone is not enough. Platforms need detection systems, provenance metadata, reporting flows, moderation queues, takedown processes, appeal paths, and rules for what happens when metadata is stripped or content is reposted. The label is the visible output of a larger operational stack.
The same logic applies to synthetic abuse such as non-consensual intimate imagery. Regulators are treating generated media as a rights and safety issue, not a novelty. That raises the stakes for products that create, edit, host, recommend, or monetize media.
Chatbots Need Risk-Based Notices
Conversational AI creates a different transparency problem. A support assistant, workplace tool, tutor, shopping bot, or health-adjacent triage system can sound confident enough that users overestimate whether a person is involved or whether the system can act on their behalf.
A good disclosure should appear before or during the interaction, especially before the user shares sensitive information or relies on a recommendation. It should also make clear whether the system can take actions, whether a human may review the exchange, and whether the answer is based on live account data, a static knowledge base, or a broader model.
This becomes more important as chatbots become agents. A model that summarizes an order is different from one that cancels it. A system that drafts a message is different from one that sends it. The label should follow the user’s risk, not merely the presence of AI somewhere in the stack.
The Compliance Work Starts With An Inventory
Companies should begin by mapping where AI appears in the user experience. That includes generated text, edited media, synthetic images, automated recommendations, chatbot responses, exported files, customer-support flows, public-interest publications, and downstream sharing. A disclosure that disappears on export may not satisfy the practical purpose of the rule.
The inventory needs legal review, but it also needs product ownership. Labels require wording, placement, timing, persistence, localization, accessibility, telemetry, exceptions, and records. Teams may need to show when a label appeared, which system generated or altered the content, whether the user could remove the label, and what happened when the content was shared.
High-risk AI systems have their own more complex timeline for areas such as employment, education, critical infrastructure, migration, law enforcement, and regulated products. Article 50 is the nearer product deadline for many companies because it touches ordinary user interfaces people see every day.
What Users Should Expect
Users should expect more explicit cues: AI response labels in chat windows, notices on synthetic or manipulated media, metadata or watermarks on exported content, and clearer warnings when AI-generated text informs the public. The best versions will be specific and calm. The weakest versions will be vague badges that satisfy a checklist without telling users what changed.
The EU AI Act will not make every AI output trustworthy, and labels will not stop every misuse of synthetic media. They do create a baseline the market has often avoided: people should not have to guess whether the content or interaction in front of them is human, automated, generated, or materially altered. That is why the 2026 transparency rules matter. They force AI products to explain themselves at the point where confusion can cause harm.
