Industry InsightsAI Credibility

AI Washing Is Now a Legal Problem, Not Just a Marketing One

The SEC has already charged firms for overstating their AI. A German academic audit found 100 startups making claims they couldn't back up. The era of vague AI claims is ending.

Sitio Labs Team6 min read4 topics

This stopped being a reputational risk and became a legal one

"AI washing", exaggerating or fabricating claims about a product's AI capabilities, has moved from an awkward marketing habit to active enforcement territory. Legal trade coverage describes AI washing now triggering SEC actions and investor lawsuits, with more scrutiny and litigation expected through 2026. The SEC's first enforcement action for AI washing dates back to 2024, when it charged two investment firms with misleading clients by claiming their strategies were driven by a proprietary deep-learning model that didn't actually do what was claimed. That precedent is now being applied more broadly as AI claims have become standard in nearly every pitch deck.

The cases are concrete, and the gap between claim and reality is often large

Regulatory actions give a sense of how specific this scrutiny has gotten. One drive-thru ordering company claimed its product removed the need for human order-taking, but regulators found the vast majority of orders actually required intervention from human contractors working abroad. Separately, the FTC fined DoNotPay $193,000 for deceptive advertising after finding its AI couldn't actually provide legal services without human intervention, despite marketing claims to the contrary. Neither case involved a company lying about having AI at all, both had some real AI component. The violation was the gap between what was claimed and what the system actually did unassisted.

The research backs up what regulators are finding

An October 2026 academic audit from the University of Hamburg studied 100 German startups and identified three recurring forms of exaggeration: claims made without any inspectable evidence, performance numbers presented without methodology, and capability claims made without acknowledging real limits. The authors' conclusion is blunt: founders exaggerate capability specifically to attract investors who reward AI branding they have no way to independently verify. One investor-side commentary adds useful context on the incentive, 37% of a recent fundraising quarter was AI-related companies, which means the pressure to sound more AI-native than you actually are is structural, not incidental.

What actually protects you, and it's simpler than legal review

The honest fix isn't a legal disclaimer, it's claims you can actually show. A product that's live, with real users, where the AI component does what you say it does without a hidden human workaround, doesn't need careful legal language to avoid this problem, it needs to be true. That's the entire reason we publish case studies with real scope, real stack, and real results instead of a slide full of adjectives, and why a studio that's shipped its own AI-native products has a different kind of credibility than one that's only ever pitched them. In a market where regulators and investors are both actively checking, the safest AI claim is the one you can open a browser and demonstrate.

Frequently Asked Questions

What counts as AI washing, exactly?

The pattern that keeps showing up in enforcement cases is claiming a capability your AI doesn't actually deliver unassisted, usually that something is "AI-powered" or "automated" when a human is quietly doing the real work behind the scenes. It doesn't require outright lying about having AI, just overstating what it does.

Can AI washing actually get a startup in legal trouble, not just bad press?

Yes. The SEC has already brought enforcement actions over AI claims, and the FTC fined DoNotPay $193,000 specifically for AI marketing claims that didn't match the product's actual capability. This is active enforcement territory now, not a hypothetical risk.

How do we make sure our own AI claims hold up?

The simplest test: could a technical reviewer or journalist verify the claim by actually using the product? If a claim depends on a demo environment, a cherry-picked example, or unstated human intervention, it's exposed. Claims backed by real production usage and documented methodology are the ones that survive scrutiny.

More from Industry Insights