Figma's AI Lawsuit Isn't About Figma. It's About Your Contract
A designer opens Figma, drags a frame onto the canvas, and starts building a screen they assume belongs to them and their client. Somewhere in a training pipeline, a version of that same file may already be teaching a model what a well-designed weather app looks like. Neither the designer nor the client signed anything that used those words. They signed a Terms of Service.
That gap — between what people believed they agreed to and what the contract actually says — is the real story behind Figma's current mess, and it's bigger than Figma. Figma is now facing a class-action lawsuit in California federal court alleging the company used customer design files to train its AI models without consent, with claims that include both copyright infringement and trade secret misappropriation. Around the same time, Figma had to disable its "Make Design" AI feature after it generated an interface that was nearly identical to Apple's Weather app — a hard demonstration that models trained on design work will, sometimes, just reproduce it. Google Stitch launched into that exact opening as a free AI design tool, and reports tied a significant drop in Figma's stock price to the controversy. Put together, this isn't a story about one company behaving badly. It's the first visible instance of a liability model that's sitting, mostly unread, in the contracts of every design and creative SaaS tool that has trained a model on user content.
The Weather app incident matters more than the lawsuit
Lawsuits are common. Class actions over data practices get filed against SaaS companies regularly, and plenty settle quietly or get dismissed without changing anything about how the underlying product works. What actually moved this story from "legal filing" to "industry reckoning" was the Make Design incident, because it turned an abstract training-data argument into something anyone could look at and recognize immediately: an AI tool output a screen that looked like it had been traced from Apple's Weather app.
That's the moment the argument stopped being theoretical. A lawsuit alleges a company did something with your data. A visibly copied interface shows you the mechanism. If a model can reproduce something that close to a specific, recognizable, real product, the question every designer should ask isn't "did this happen to Apple." It's "what's stopping this from happening to the client work sitting in my own files." Figma pulled the feature, which is the correct response and also, notably, an admission that the risk was real enough to require pulling a shipped product rather than patching it.
It's also worth noticing why the lawsuit names both copyright and trade secret claims, because those are different arguments doing different jobs. Copyright is about whether output too closely resembles a specific protected work — the kind of claim the Weather app incident makes vivid. Trade secret misappropriation is a different animal entirely: it's about confidential, competitively valuable material — an unreleased product's interior design, an unlaunched feature's interaction flow — being used in ways the owner never authorized, whether or not the AI output ever resembles it visibly. A designer's unshipped mockup doesn't need to show up looking like anything in particular for that second claim to matter. It just needs to have been fed into a system its owner didn't knowingly consent to.
"Improve our services" is not a small phrase
Read enough SaaS terms of service and you'll find some version of the same sentence: the company "may use your content to improve our services." It shows up in design tools, writing tools, video tools, note-taking apps, project management software — anywhere a company collects user-generated content at scale. Almost nobody stops to ask what that sentence licenses the company to do, because it reads like boilerplate. It isn't. That single clause is frequently the entire legal basis for training a model on your files, your client's confidential product mockups, or your unreleased brand work.
The uncomfortable truth is that this clause has probably been sitting in most creative tool contracts for years, long before anyone built a model capable of learning from it usefully. Nobody wrote it anticipating AI training specifically — it was originally boilerplate to cover things like caching, backups, and product analytics. Then the technology caught up to the language, and the language turned out to already grant far more than anyone negotiating it in 2019 intended. That's not a hypothetical about Figma. It's a description of how contract law works: broad language survives until someone builds a use case broad enough to fill it.
Designers read Terms of Service summaries. They don't read contracts
Most people, designers included, engage with a Terms of Service the way they engage with a cookie banner: scroll, find the "accept" button, move on. When a summary exists — a plain-language recap, a blog post breaking down "what changed" — that's what actually gets read, if anything gets read at all. The problem is that summaries compress exactly the clauses that matter most into a single reassuring sentence, because "we may use anonymized data to improve services" sounds fine in a recap and does an enormous amount of legal work in the actual document.
This is the same failure mode I wrote about with AI wireframe tools skipping the parts of design that don't demo well — the visible layer looks complete, and the part that actually determines what happens later is the part nobody looked at closely. A wireframe that looks finished can hide the fact that error states were never specified. A ToS summary that looks reassuring can hide the fact that a training-data license was already granted. Both fail the same way: the surface reads as done, and the substance was never checked.
This will not stay a Figma problem
Design tools are not unusual in collecting large volumes of proprietary user content. Every competitor with a comparable AI feature roadmap has the same incentive Figma had: a training corpus of real, professionally-made design work is valuable, and a ToS clause is a cheap way to get access to it. Google Stitch entering the market as a free alternative during Figma's controversy is a reminder that the competitive pressure to ship AI design features isn't going away — if anything, a rival launching for free raises the incentive for every vendor to move faster, not more carefully, on exactly the practices now under legal scrutiny.
None of this requires believing any particular company is acting in bad faith. It requires recognizing that the incentive structure — broad content licenses, competitive pressure to train on real work, and contracts nobody reads past the summary — is present across the entire category, not unique to one vendor that happened to get caught first. Figma is the visible instance. It is very unlikely to be the last one.
There's also a market signal worth sitting with: a reported significant drop in Figma's stock tied to this news cycle isn't just punishment for one company's bad week. It's a market pricing in the possibility that this liability model applies more broadly than one vendor, and that investors in every AI-forward SaaS company with a similar content library are now asking their own version of the question a designer should be asking about their tools.
What actually changes if you take this seriously
The practical response isn't switching design tools, boycotting AI features, or waiting for regulation to catch up — regulation on training data consent is still unsettled and will not resolve this in the timeframe that matters. The practical response is reading the actual contract, not the marketing page or the plain-language summary, for the specific clause that governs what a vendor can do with your content after you upload it. Look for the words "train," "improve," "develop," or "machine learning" anywhere near a data-use clause. If a client's confidential product work lives in a tool with that language unaddressed, that's a conversation to have with the client before it becomes a conversation with a lawyer.
Every tool with a "your content, our improvement" clause is one visible incident away from becoming the next headline. Figma just happened to go first.