For a while, AI washing sounded like a cheap shot. A company slapped “AI-powered” on ordinary software. A vendor implied the model could do more than it really could. A marketing team reached for the label because the market wanted to hear it.
That still happens. What has changed is the legal posture around it.
AI washing is no longer just a hype problem. It is turning into a substantiation problem. When a company says a product is intelligent, autonomous, safe, accurate, compliant, unbiased, or ready for sensitive work, regulators, customers, investors, and plaintiffs can all ask the same question: what did that claim actually mean, and what evidence supported it?
That question does not require a new AI-specific statute. Existing deception, unfairness, privacy, procurement, securities, and misrepresentation theories are already enough to create pressure.
Why This Is Becoming A Real Legal Category
The reason is straightforward. AI claims now shape material decisions.
Consumers may rely on them when deciding whether a product is safe, trustworthy, educational, therapeutic, or appropriate for minors. Enterprise buyers may rely on them when deciding whether a system is ready for legal, HR, health, finance, or security workflows. Investors and board members may rely on them when evaluating growth, defensibility, product moat, or operational maturity.
Once AI language starts influencing those decisions, the claim stops being casual branding. It becomes something closer to a factual representation about capability, safety, governance, or reliability.
That is why AI washing is becoming a legal category even without a statute labeled “AI washing.” The law already knows how to handle claims that create a misleading net impression.
“AI” Is Not Just One Claim
One reason this gets messy fast is that companies often use AI language as if it were a single label.
It is not. Saying a product uses AI can imply very different things depending on the context. It may suggest the product actually uses machine learning rather than ordinary automation. It may suggest the system is more advanced than a rules engine, improves itself over time, requires less human labor, produces more accurate results, acts autonomously, or has stronger safety and governance controls than competing tools.
Those are not all the same claim. They create different expectations and different legal exposure.
A regulator or plaintiff usually does not need to prove that every part of the AI story was false. It is often enough to show that the overall impression was materially misleading for the audience that mattered.
The Problem Is Broader Than Capability Hype
The obvious form of AI washing is capability inflation. A company says the product can do things it cannot do.
The harder cases are broader than that. The claim may not be “our model is magic.” It may be “our system is safe,” “our outputs are objective,” “our workflow is compliant,” “our AI runs with human oversight,” or “our platform is enterprise ready.”
That is where the risk gets more serious, because those claims are often tied to internal process, governance, testing, escalation, data handling, and product design, not just model performance.
A company can also create AI-washing risk by hiding the amount of human labor behind the product, downplaying model limitations, overstating bias mitigation, overstating explainability, or suggesting a level of operational control that does not really exist.
In other words, the legal problem is often not “you said the word AI.” It is “you used AI language to imply a level of performance, safety, or governance that the record cannot support.”
The FTC Makes The Trend Easier To See
The FTC's proposed AI accuracy policy statement is not an anti-AI-washing rule by name, but it shows the direction clearly.
The Commission's point is that a company may create the impression that its AI system is trying to provide the best, most accurate, or most truthful answer for the user's objective. If the system is actually steered toward a different hidden objective, the FTC says that may be deceptive.
That is a model-design issue, but it is also a claims issue. A company may never use the phrase “objective and neutral” and still create that impression through product design, benchmarking language, sales materials, accuracy messaging, or positioning.
The same pattern showed up differently in the FTC's Active Listening matter. There, the problem was not just a buzzword. It was the gap between what the product was presented as doing and what the facts supported about the listening function and the related privacy implications.
Put those together and the pattern becomes clearer. AI-washing risk is not confined to inflated tech language. It can arise whenever the public story about the system outruns the product reality.
Where The Risk Usually Shows Up
The public homepage is only one part of the problem.
Marketing copy is the obvious starting point because words like autonomous, safe, trustworthy, accurate, unbiased, transparent, and enterprise ready can imply a lot more than the company intends. Those words are not off-limits. They just need support.
The bigger risk often sits in enterprise sales materials, procurement responses, security questionnaires, governance decks, and customer demos. That is where companies make concrete statements about explainability, retention, deletion, human review, model change management, data isolation, safety controls, and compliance readiness. If those statements outrun the actual workflow, the mismatch may surface later in a customer dispute, regulator inquiry, or internal escalation.
Investor and board communications create another layer. If a company ties AI to measurable gains in safety, efficiency, margins, market position, or defensibility, those statements may later be compared against testing records, incident logs, and internal discussions. Not every optimistic statement creates liability. But specific, repeated, safety-linked claims deserve careful treatment.
The product experience itself also matters. A system can create strong expectations without saying much at all. A chatbot that speaks with confidence, appears emotionally perceptive, presents itself as a trusted helper, or hides the extent of human involvement may create a stronger impression than any disclaimer in the footer.
The Internal Record Usually Decides How Bad It Gets
AI washing tends to look worst once someone asks for the internal record.
If the company publicly describes a system as safe, accurate, objective, well-governed, or ready for sensitive deployment, the next questions are predictable. What testing supported that statement? What limitations were already known? Were complaints or incidents pointing in the other direction? Did anyone inside the company describe the claim as too aggressive? Was the claim approved because it was supported, or because it sounded good?
That is the point where puffery arguments start to weaken. The problem stops looking like enthusiastic copy and starts looking like a documentation and governance failure.
What Companies Should Review Now
Companies using AI language in public or customer-facing materials should review a few things immediately.
- Whether the claim is really about the presence of AI, or about performance, safety, autonomy, neutrality, or compliance.
- Whether current product testing and governance records actually support the claim being made.
- Whether consumers, enterprise customers, investors, and regulators are hearing different versions of the same product story.
- Whether the product experience creates stronger expectations than the formal copy.
- Whether disclaimers change the net impression in a meaningful way, or just try to patch over an aggressive claim after the fact.
- Whether the rationale behind sensitive AI claims is being preserved in a way the company could defend later.
The practical question is not “can we argue about this phrase if challenged?” It is “what expectation does this create, and would we be comfortable defending that expectation with the actual record?”
Bottom Line
AI washing is becoming a real legal category because AI claims now influence decisions about safety, trust, spending, and risk.
The law does not need a special AI-washing label to get there. Existing doctrines already give regulators and plaintiffs room to test whether the public AI story matches the product, the workflow, and the record behind it.
If a company would be uneasy putting its public AI claims next to its testing history, governance records, customer complaints, and known limitations, those claims probably need work.