Trade secret law has always had a slightly awkward social problem: everyone in the case wants to talk about the secret without actually revealing the secret. It is the legal equivalent of trying to explain your favorite recipe while refusing to admit what makes the sauce taste so good. That tension sits at the center of a major Ninth Circuit decision that now gives companies, lawyers, and judges much sharper guidance on how federal trade secret claims should move through California courts.
In Quintara Biosciences, Inc. v. Ruifeng Biztech, Inc., the Ninth Circuit drew a meaningful line between the federal Defend Trade Secrets Act, or DTSA, and California’s Uniform Trade Secrets Act, commonly called CUTSA. The ruling matters because trade secret cases often rise or fall on timing. When must a plaintiff define the alleged secret? How detailed must that definition be before discovery begins? And can a court toss out a claim early because the description is not precise enough on day one?
The Ninth Circuit’s answer was clear enough to make trade secret litigators sit up straighter in their ergonomic chairs: the DTSA does not import California’s pre-discovery “reasonable particularity” requirement. In other words, federal law is not just California law with a nicer suit and a federal courthouse badge. That distinction has real consequences for pleading strategy, discovery battles, motion practice, and forum selection.
This article breaks down what the Ninth Circuit decided, why the difference between DTSA and CUTSA matters, how the ruling fits with earlier and related Ninth Circuit trade secret decisions, and what businesses should do now if they want their trade secret claims to survive first contact with litigation.
What Happened in the Quintara Case?
The dispute in Quintara arose between two California DNA sequencing and analysis companies whose business relationship unraveled in dramatic fashion. According to the plaintiff, the relationship deteriorated, offices were locked, equipment changed hands, and employees were pulled away. Quintara sued under the federal DTSA, alleging that Ruifeng had misappropriated trade secrets involving customer and vendor information, marketing plans, software code, product designs, customized reagents and protocols, and related technical know-how.
That is already a familiar trade secret storyline: a business partnership goes sideways, access to information becomes the battlefield, and suddenly everyone is arguing about whether a spreadsheet is priceless intellectual property or just a glorified contact list with ambition.
But the key procedural twist was this: Quintara brought a DTSA claim and did not plead a CUTSA claim. Even so, the district court borrowed California’s procedural disclosure rule, which requires a plaintiff in a CUTSA action to identify the alleged trade secret with reasonable particularity before trade-secret discovery moves forward. The court ordered Quintara to provide a much more detailed disclosure, essentially asking for a level of precision that sounded a little like drafting patent claims. When Ruifeng argued that the revised disclosure still was not specific enough, the district court struck nine of the asserted trade secrets and effectively narrowed the case to almost nothing.
That move may have seemed practical from a case-management perspective. Judges do not enjoy letting trade secret cases turn into fishing expeditions. Defendants do not enjoy being told to produce sensitive information while the plaintiff still describes the secret in foggy, high-altitude language. But the Ninth Circuit concluded that the district court had crossed the line from managing discovery to importing a California rule into a federal claim where it did not belong.
What the Ninth Circuit Actually Held
The Ninth Circuit did not say that DTSA plaintiffs may wander into court waving their hands and shouting, “The secret is… secret-ish.” That would be chaos, and federal courts generally frown on chaos unless it is carefully briefed.
Instead, the court said something more precise and more important: under the DTSA, a plaintiff still must ultimately prove that the claimed trade secret is identified with sufficient particularity. But unlike CUTSA, the DTSA does not require that showing at the outset of discovery under California’s pre-discovery disclosure rule. The court treated the question of whether the plaintiff had identified a trade secret with sufficient particularity as a factual issue that is usually better resolved on summary judgment or at trial, not through an early discovery-stage strike order.
Just as important, the Ninth Circuit held that Rule 12(f) was not the proper tool for striking Quintara’s trade secret disclosures and that the district court had abused its discretion by effectively dismissing those claims so early. The panel emphasized that federal courts already have other tools to manage the “delicate problem” of trade secret discovery, including protective orders, staged discovery, and court supervision under the Federal Rules of Civil Procedure.
That is the center of gravity in the decision. The Ninth Circuit did not eliminate discipline. It relocated it. The message was: use federal procedural tools to manage confidentiality and sequence discovery, but do not use California’s special pre-discovery CUTSA rule to short-circuit a federal DTSA claim.
DTSA vs. CUTSA: Same Family, Different House Rules
The DTSA
The DTSA gives owners of trade secrets a federal civil cause of action when the misappropriated secret is connected to a product or service used in interstate or foreign commerce. It also expressly does not preempt state trade secret remedies. That means federal and state trade secret claims can coexist, and they often do. A plaintiff can plead DTSA and CUTSA together, or sometimes choose one over the other depending on the facts and the litigation strategy.
For years, that overlap encouraged a practical assumption in California: if state law requires early particularity, maybe federal courts handling California trade secret disputes should expect something similar. Earlier Ninth Circuit language in cases such as InteliClear fed that debate because it emphasized that a trade secret must be identified with sufficient particularity. What remained fuzzy was the timing of that showing in a DTSA-only case.
The CUTSA Rule
CUTSA comes with California Code of Civil Procedure section 2019.210, which requires the plaintiff to identify the trade secret with reasonable particularity before commencing discovery relating to the trade secret. That requirement serves several purposes. It helps define the case. It prevents vague accusations from unlocking broad discovery into a competitor’s business. And it forces the plaintiff to separate actual trade secrets from general knowledge, employee skill, or material already in the public domain.
California courts have long treated that rule as an important gatekeeping device. It is not just housekeeping. It is a front-door filter.
Why the Distinction Matters
Quintara makes clear that the federal DTSA and California’s CUTSA may be close cousins, but they do not share identical house rules. A plaintiff who brings only a DTSA claim in federal court does not automatically inherit California’s pre-discovery disclosure burden. That is a major procedural distinction, and it creates a very real difference in how a case can develop.
For plaintiffs, that means more room to refine the description of a trade secret during discovery rather than locking the entire theory into a hyper-detailed early disclosure. For defendants, it means the early knockout punch becomes harder to land in DTSA-only cases. For judges, it means discovery management has to happen through federal case-management tools instead of a borrowed state-law shortcut.
How Quintara Fits with InteliClear and Zunum
The Ninth Circuit did not write Quintara on a blank page. The decision fits into a broader line of trade secret rulings that increasingly treat specificity as a factual question rather than a magical incantation that must be fully perfected at the opening bell.
In InteliClear, LLC v. ETC Global Holdings, Inc., the Ninth Circuit held that there was a genuine issue of material fact as to whether the plaintiff had identified at least one trade secret with sufficient particularity. That case is often read for the idea that a trade secret must be described in a way that distinguishes it from ordinary industry knowledge, but it also supports a more nuanced point: whether the plaintiff has done enough is often a merits question, not a quick procedural execution.
Then came Zunum Aero, Inc. v. Boeing Co., where the Ninth Circuit reinstated a major jury verdict after the district court had concluded that Zunum failed to identify its trade secrets with sufficient particularity. The appellate court said that while a plaintiff must identify its trade secrets with enough specificity for the jury to evaluate them, it does not have to define every boundary with perfect precision. The panel restored a verdict tied to Boeing’s alleged misuse of startup technology and related confidential information, reinforcing the idea that trade secret identification is often something juries can meaningfully assess when the evidence is fully developed.
Taken together, InteliClear, Quintara, and Zunum push the Ninth Circuit toward a more practical, fact-driven framework. Specificity matters. But the court is increasingly skeptical of treating specificity as an early procedural trapdoor. That is not a small shift. It changes leverage.
Why This Decision Matters for Plaintiffs
If you represent a company that believes its trade secrets were stolen, Quintara is encouraging. It does not eliminate the need for careful drafting, and sloppy complaints remain a terrible idea. But it does make federal DTSA litigation in California a little less like trying to perform open-heart surgery while filling out paperwork with a broken pen.
Plaintiffs still need to do the hard work. They should identify categories of trade secrets clearly, explain why the information is not generally known, and show the reasonable measures used to maintain secrecy. But they now have stronger support for the argument that detailed refinement may occur through the iterative discovery process rather than through an all-or-nothing pre-discovery showdown.
That matters especially in cases involving layered trade secrets, such as source code architecture, manufacturing tolerances, technical workflows, pricing models, product roadmaps, or curated customer intelligence. In those cases, the secret often lies not in a single document but in a combination, structure, sequence, or integration of information. Describing that kind of asset at a very early stage can be difficult without seeing how the defendant actually used or copied it.
Why This Decision Matters for Defendants
Defendants should not read Quintara as a surrender flag. It is more like a warning label: choose your procedural tools carefully. If a plaintiff’s trade secret theory is vague, overbroad, or opportunistic, defendants still have serious defenses. They can challenge the existence of a trade secret, test whether the information was actually secret, argue that the alleged value came from public or industry-known sources, and push back on causation and damages.
What has changed is the timing and method of attack. Rather than relying on California’s pre-discovery disclosure rule in a DTSA-only case, defendants will need to focus more on targeted discovery, confidentiality protections, narrowed issue framing, expert analysis, and summary judgment. They may still win. They just may have to win the longer way around.
That is not necessarily unfair. Trade secret cases are often technical, fact-heavy, and context-dependent. The Ninth Circuit appears increasingly convinced that a fuller record, not a premature pruning shears routine, is the better way to evaluate them.
Practical Lessons for Businesses Trying to Protect Trade Secrets
Litigation strategy is only half the story. The other half starts long before anyone files a complaint. Cases like Quintara and Zunum highlight how much turns on internal discipline. Courts may be more flexible about timing, but they still expect companies to prove that the information at issue was actually secret and was actually protected.
1. Name your trade secrets before a lawsuit forces you to
Many companies know they have valuable know-how, but few maintain a clean internal inventory of what qualifies as a trade secret. That is a mistake. A company should be able to identify core confidential assets by category, business function, and value.
2. Match secrecy measures to the importance of the information
Access controls, confidentiality agreements, employee training, vendor restrictions, document classifications, and exit procedures all matter. Courts look for “reasonable measures,” not performative paranoia. Still, if everyone in the company can grab the file from a shared drive called “Definitely Secret Final FINAL v6,” the litigation story writes itself, and it is not flattering.
3. Preserve evidence of development and value
Trade secret cases often turn on proof that the information took time, money, expertise, and experimentation to develop. Keep records. Preserve design histories, research timelines, testing data, and business plans that show why the information mattered.
4. Control relationships with partners and departing employees
Some of the ugliest trade secret disputes do not begin with a masked hacker. They begin with a partner, consultant, contractor, investor, or senior employee who had legitimate access and then used it for the wrong purpose. That means agreements, scope limits, monitoring, and offboarding procedures are not optional extras. They are preventive medicine.
Experience from the Real World: What Trade Secret Fights Usually Feel Like
One of the most useful ways to understand the Quintara ruling is to look at how trade secret disputes actually feel inside a business. They rarely begin with a dramatic memo labeled “misappropriation.” They usually begin with a weird moment. A sales team suddenly loses accounts it had locked down for years. A former engineer launches a strikingly familiar product. A vendor relationship implodes, and the other side suddenly knows details it should not know. Someone notices that customer outreach has become suspiciously precise, as if an invisible hand is holding the company’s playbook.
Then the panic starts. Executives want answers immediately. Lawyers ask for a list of the trade secrets. Business people respond with something like, “Well… kind of everything important.” That answer may be emotionally satisfying, but it is terrible litigation fuel. The real experience of preparing a trade secret case is the slow, sometimes painful process of turning business intuition into legal definition.
In many companies, the first pass is too broad. The team points to the database, the pricing strategy, the customer pipeline, the product roadmap, the lab methods, the code base, the training materials, and the market expansion plan. Some of that may indeed be protected. Some of it may be merely useful. Some of it may be confidential but not actually a trade secret. And some of it may be a protectable secret only because of the way the information is organized rather than because of any single line item.
That is why the Ninth Circuit’s approach makes practical sense. In the real world, trade secret identification often sharpens through evidence. Discovery reveals who accessed what, when files moved, what devices were used, what competing product changes occurred, and how internal communications described the plaintiff’s information. A case that looks fuzzy at filing can become precise later, not because the plaintiff invented a new theory, but because the evidence clarifies where the economic value and secrecy actually lived.
Defendants have real experiences here too. From their side, vague trade secret accusations can feel like being told to open the vault because the plaintiff believes something shiny is missing. That is why courts still need boundaries, protective orders, and disciplined issue framing. Quintara does not deny that concern. It simply says federal courts should manage that concern with federal procedural tools instead of importing California’s special pre-discovery filter into every DTSA fight.
The lesson from actual disputes is simple: the strongest trade secret cases are built by businesses that already know what they protect, why it matters, who had access, and what rules governed its use. When that foundation exists, litigation is still hard, but at least it is a chess match. Without that foundation, it turns into a scavenger hunt in dress shoes.
Final Takeaway
The Ninth Circuit’s clarification of DTSA versus CUTSA is more than a technical procedural ruling. It reshapes how federal trade secret litigation is likely to unfold in California. The court preserved the core idea that trade secrets must be defined with enough specificity to separate them from general knowledge. But it rejected the notion that a DTSA plaintiff must satisfy California’s pre-discovery “reasonable particularity” rule before the case can truly begin.
That means timing matters. Forum choice matters. Claim selection matters. And case management tools matter. For plaintiffs, the ruling offers breathing room. For defendants, it shifts the fight from early gatekeeping to disciplined merits litigation. For businesses, it is a reminder that the best trade secret strategy is still boring in the most profitable way possible: identify the assets, protect them consistently, document the safeguards, and prepare for the day a court asks you to explain exactly what makes your secret worth stealing.
