If your product talks to people with AI, or generates content with it, you will soon have to say so out loud. Disclosure is shifting from a nice-to-have to a default, pushed by regulation and, more quietly, by trust. For product, design, and growth teams in every industry, the question is no longer whether to tell users they are dealing with AI. It is how to do it in a way that builds confidence instead of draining it.
The clearest forcing function is European. Under the EU AI Act, providers must ensure that AI systems intended to interact directly with people are designed so those people are informed that they are interacting with an AI system, unless it is obvious. The same article requires that AI-generated audio, image, video, and text be marked as artificially generated, and that deepfakes be disclosed. These are not abstract principles. The European Commission's timeline puts the Article 50 transparency rules into application on 2 August 2026. The reach is broad: it applies to providers and deployers placing these systems on the EU market, wherever the company is based, which means a US or UK product with EU users is in scope too.
Treating disclosure as a legal checkbox misses the bigger reason to do it well. Public trust in AI is not a given. In its 2025 AI Index, Stanford's Institute for Human-Centered AI reports that only 39 percent of people in the United States see AI products and services as more beneficial than harmful, with optimism higher in some countries and lower in others. When trust is that fragile, being caught hiding the AI is expensive. A user who discovers after the fact that the helpful agent was a bot, or that the article was machine-generated, does not just feel misled about one interaction. They reassess everything else you told them. Disclosure done well is the opposite move: it signals respect, sets accurate expectations, and gives the user a reason to keep going rather than a reason to doubt.
Picture a bank with a support chat that opens with a friendly first name and no indication it is automated. A customer spends ten minutes explaining a fraud worry to what they assume is a person. Only when the answers start looping do they realize it was a bot all along. Now they are not only unhelped, they feel deceived on the exact topic where trust matters most. The same script plays out in a health portal triaging symptoms, a retailer handling a refund, and a media site publishing AI-drafted summaries with no label. Nothing illegal may have happened yet, but the relationship took the damage.
Designed for transparency, the same flow reassures instead. The chat opens with a plain line that the customer is talking to an AI assistant, names what it can and cannot do, and keeps a visible path to a human one tap away. AI-generated content carries a quiet, consistent label. The disclosure is not buried in a privacy policy nobody reads. It is part of the interface, delivered, in the words of the regulation, in a clear and distinguishable manner at the first interaction. The AI did not become less useful. The user simply knew what they were dealing with, and trusted it more for the honesty.
Most teams will treat disclosure as a banner added the week before an audit. That is the version users tune out and regulators are unimpressed by. The better approach designs it into the experience: where the AI label sits, how a person reaches a human, how AI-generated content is marked consistently across the product. This is the same discipline as designing for AI failure states, where the moment the AI falls short is exactly when honesty and a human handoff protect the relationship. It is also the trust layer we describe in designing for the answer-engine era: your credibility now depends on saying the same clear, honest thing everywhere, to people and to the machines reading on their behalf.
Before your next AI feature ships, run your team through these five questions. We use them as a practical lens at Aero, not an industry standard, and they surface the gaps fast.
If any answer is uncomfortable, the gap is in how you designed transparency, not in whether you are allowed to use AI.
Among other things, it requires that people be informed when they are interacting with an AI system unless that is obvious, that AI-generated audio, image, video, and text be marked as artificially generated, and that deepfakes be disclosed. These Article 50 transparency rules start to apply on 2 August 2026.
It can. The obligations attach to AI systems placed on the EU market and to interactions with people in the EU, so a company based elsewhere with EU users is generally in scope. Beyond the law, disclosure is a trust practice worth adopting regardless of where you operate.
Done as an afterthought, poor disclosure can feel like a warning label. Done as a designed part of the experience, it sets accurate expectations and tends to build trust, especially given how many people are still skeptical of AI. Being discovered hiding it is the far costlier outcome.
Start by listing every place your product uses AI to talk to people or generate content, then ask whether a user would know it in each one. Aero Interactive helps product teams design AI transparency that satisfies the rules and earns trust at the same time. Reach out to start the conversation.
The pressure to replace support staff with AI is nearly universal, and so is the boomerang. Why swapping people for a bot without redesigning the service is a false economy, plus a five-question human-AI service model check.
Every AI feature ships with a failure rate, and your users will meet it. The teams that win design the moment the AI is wrong, not just the moment it is right. Here is how, plus a five-question failure-readiness check.
