Ninth Circuit on Trade Secret Identification – Podcast

Trade secret litigation has a funny habit of asking parties to do two contradictory things at once: be specific, but not too specific; explain the secret, but please do not actually spill it on the courtroom floor. That tension sits at the center of Greenberg Traurig’s podcast episode on the Ninth Circuit’s latest guidance about trade secret identification, and it is exactly why this topic matters far beyond one biotech fight in California.

The podcast focuses on a 2025 Ninth Circuit decision that reshaped how lawyers should think about identifying trade secrets in cases brought under the federal Defend Trade Secrets Act, or DTSA. The ruling does not give plaintiffs a free pass to stay vague. It does, however, make clear that federal courts cannot automatically import California’s early disclosure rule and use it like a meat tenderizer on a DTSA claim before discovery has really begun.

In plain English, the episode is about timing, fairness, litigation strategy, and the eternal headache of telling a court what your trade secret is without handing your competitor a cheat sheet. For in-house counsel, founders, litigators, and even product teams that guard sensitive know-how, the discussion is more practical than it first appears. This is not just a podcast for people who collect appellate opinions for fun, though that niche audience is undoubtedly thriving.

What the Podcast Is Really About

The podcast episode examines the Ninth Circuit’s decision in Quintara Biosciences, Inc. v. Ruifeng Biztech, Inc., a case centered on how and when a plaintiff must identify alleged trade secrets under the DTSA. The hosts frame trade secret identification as one of the most heavily contested issues in trade secret litigation, and that description feels earned. Courts want enough detail to separate a genuine trade secret from a cloud of buzzwords. Defendants want enough notice to defend themselves. Plaintiffs want to avoid turning protected information into public roadkill. Everyone wants precision, but nobody wants overexposure.

That balancing act is what older Ninth Circuit case law once described as a “delicate problem,” and the phrase still fits. It is the legal equivalent of transporting a birthday cake across town without ruining the frosting: move too fast and everything collapses; move too slow and people start asking why nothing has arrived.

The Case Behind the Podcast: Quintara v. Ruifeng

A California dispute with federal consequences

Quintara arose from a dispute between two California companies involved in DNA sequencing and analysis. According to the allegations summarized in the opinion and discussed in the podcast, the business relationship deteriorated, and Quintara claimed Ruifeng misappropriated a range of trade secrets, including customer-related information, marketing materials, proprietary reagents, and DNA donor technology.

Here is the important procedural twist: Quintara sued under the federal DTSA, not under California’s Uniform Trade Secrets Act, or CUTSA. That detail turned out to matter a lot. In California state-law trade secret actions, Code of Civil Procedure section 2019.210 requires a plaintiff to identify the alleged trade secret with “reasonable particularity” before discovery relating to the trade secret begins. That rule exists for understandable reasons. It prevents fishing expeditions, forces a plaintiff to commit to what it claims is secret, and helps the court manage discovery without letting the case become an industrial espionage buffet.

But the district court borrowed that California rule and applied it to Quintara’s federal DTSA claim at the outset of discovery. It required a detailed disclosure and, after finding most of the disclosure insufficient, struck nine of Quintara’s eleven alleged trade secrets. The case proceeded on only two. After further litigation, Quintara lost the last surviving claim at trial and appealed.

What the Ninth Circuit Actually Held

The DTSA does not copy California’s early disclosure rule

The Ninth Circuit reversed the striking of those trade secrets and made a point that will echo through future federal cases: unlike CUTSA, the DTSA does not require a plaintiff to identify its alleged trade secrets with particularity from the start of the case. Instead, under the federal statute, whether the plaintiff has identified a trade secret with sufficient particularity is generally a factual issue to be resolved after some discovery, often at summary judgment or trial.

That distinction is the heart of the podcast discussion. The court did not say, “Bring us your vaguest allegations and your most mysterious nouns.” It said something more disciplined. A DTSA plaintiff still must ultimately define the trade secret with enough specificity to distinguish it from general industry knowledge or broad categories of information. But federal law does not impose California’s specific timing rule at the very beginning of discovery in a pure DTSA case.

Rule 12(f) was the wrong procedural hammer

The Ninth Circuit also held that Federal Rule of Civil Procedure 12(f) was not the right tool for striking the trade secret disclosure. Rule 12(f) concerns material in pleadings that is insufficient, redundant, immaterial, impertinent, or scandalous. Quintara’s disclosure did not fit neatly into that box, and the panel concluded the rule did not authorize what the district court had done.

This is more than procedural housekeeping. In litigation, the choice of procedural tool often decides whether the fight is about merits, timing, or sanctions. The podcast rightly emphasizes that point. When courts use the wrong mechanism, they risk converting a case-management dispute into a merits defeat before the record is mature enough to support that result.

Discovery sanctions remain possible, but early dismissal should be rare

The Ninth Circuit did not strip trial courts of discretion. Far from it. Federal judges still retain broad authority to sequence discovery, protect confidential information, enter protective orders, and manage the exchange of sensitive material. What the panel rejected was the idea that a district court could effectively dismiss much of a DTSA claim early, before meaningful discovery, simply because the plaintiff had not yet met a California-style “reasonable particularity” requirement.

That means courts can still require discipline, but they should not confuse discovery management with an early death sentence. The opinion suggests that dismissal at that stage should be unusual because the sufficiency of trade secret identification often becomes clearer through the iterative process of discovery.

Why This Decision Matters

The practical impact of Quintara is obvious. Plaintiffs bringing federal-only trade secret claims in the Ninth Circuit may try to avoid state-law baggage by pleading under the DTSA alone. Defendants, meanwhile, will likely push harder for targeted protective orders, phased discovery, sealed submissions, and carefully structured disclosures rather than relying on a blanket demand for early patent-style identification.

The decision also sharpens a strategic divide between federal and state approaches. California’s rule is explicit and front-loaded. The federal DTSA, at least as interpreted in this case, is more flexible on timing. That does not mean federal court is now a vagueness spa. It means the pathway to specificity is more procedural and fact-driven rather than dictated by a state statute at the opening bell.

This matters because trade secret cases are often about fast-moving business relationships, employee departures, source code, pricing models, customer data, manufacturing steps, formulas, and internal methods that are valuable precisely because they are not public. Overly rigid early disclosure can damage the asset the plaintiff is trying to protect. Overly loose disclosure can unfairly burden defendants and courts. Quintara attempts to keep both concerns in view.

How the Podcast Connects Quintara to Bigger Trade Secret Trends

One of the smarter parts of the podcast is that it does not oversell the ruling as a revolution. The hosts treat it as a major decision, but not a magic wand. That is the right tone. The court did not eliminate the requirement of “sufficient particularity.” It merely clarified that, in a DTSA-only case, the question usually belongs later in the process, after some factual development.

That distinction lines up with the Ninth Circuit’s earlier decision in InteliClear, LLC v. ETC Global Holdings, Inc., where the court held there was at least a triable issue of fact as to whether the plaintiff had identified its trade secrets with sufficient particularity. InteliClear is important because it shows the Ninth Circuit has long treated trade secret identification as a concrete and evidence-driven question, not merely a pleading slogan. In other words, the plaintiff still has to show the court the secret is a real secret and not just “our special business stuff, please trust us.”

The broader national conversation also supports that view. Commentators have noted that different jurisdictions handle timing differently, and trade secret identification remains highly fact-dependent across the country. So while Quintara is a Ninth Circuit case, the podcast captures a national issue: courts are still wrestling with how to require enough disclosure to make litigation fair without requiring so much disclosure that the plaintiff’s confidential information ends up flapping in the procedural wind.

Examples of Trade Secret Identification Done Better

Consider the difference between two descriptions. A weak disclosure says the company’s “confidential customer information, proprietary methods, and business processes” were stolen. That sounds dramatic, but it tells the court almost nothing. A stronger disclosure might specify a customer segmentation framework tied to nonpublic fields, ranking logic, pricing triggers, and internal combinations not known in the industry, while also describing the security measures used to protect it. That still protects secrecy, but it draws a line between a genuine trade secret and a corporate shrug.

The same logic applies to source code cases. Saying “our software” is secret is useless. Describing a nonpublic architecture, a defined set of modules, interaction logic, unique data structures, and the way those pieces create competitive value is far more useful. The point is not to publish the code in the complaint like a tragic open-source accident. The point is to identify the subject matter with enough precision that the court and the defendant know what is allegedly at issue.

What Businesses Should Take Away

For companies, the lesson is not just about lawsuits. It is about preparation long before a lawsuit. Businesses that actually know what their trade secrets are tend to litigate better than businesses that discover, mid-emergency, that “trade secret inventory” is not the name of a folder but a thing they should have built months ago.

Strong trade secret practice usually includes internal mapping of valuable information, access controls, confidentiality terms, segmented permissions, training, device return procedures, vendor protections, and documented business reasons why the information has independent economic value. Those habits do not merely impress lawyers. They make it easier to identify the trade secret in litigation without inventing the theory on the fly.

For defense teams, Quintara suggests a different playbook: focus on disciplined discovery sequencing, demand clarity through protective mechanisms, challenge vagueness with record-based motions later, and build arguments around whether the allegedly secret information is really secret, really protected, and really misappropriated. The battlefield shifts, but it does not disappear.

Experiences From the Trade Secret Battlefield

In real-world trade secret disputes, the most stressful moment often arrives before anyone has taken a deposition. A company thinks sensitive information walked out the door with a former employee, a failed partner, or a competitor that suddenly knows a little too much. Executives want immediate action. Engineers want to avoid disclosing the crown jewels. Sales teams want to know whether customer lists are now radioactive. Outside counsel, meanwhile, gently asks the question nobody loves: “Can you define exactly what was secret?” That is where the theory of trade secret identification becomes an operational test of whether the business truly treated the information like a protected asset.

Many companies discover that their best people know the secrets intuitively but have never documented them cleanly. Product teams can explain why a workflow matters. Scientists can explain why a process works. Developers can explain why a structure is elegant. But turning that lived knowledge into a disclosure that is specific enough for court and guarded enough to preserve secrecy is hard work. It requires translation, not just accusation. That is why the “delicate problem” language resonates so strongly. The pressure is real, the timing is terrible, and the risk of saying too much or too little is not theoretical.

For plaintiffs, the experience can feel like being asked to prove the value of a locked safe by opening it just enough for the judge to inspect the contents, while hoping the person across the table does not memorize everything. For defendants, the experience is different but no less frustrating. They may face a complaint that sounds ominous but blurry, forcing them to defend against categories rather than clearly identified secrets. That is why courts keep circling back to specificity. Due process matters. So does confidentiality. Trade secret litigation is one of the few areas where both concerns are intense from day one.

Lawyers who handle these disputes often describe an iterative pattern. The first disclosure is too broad. The meet-and-confer is tense. The protective order gets negotiated like an international treaty. The amended disclosure becomes narrower, sharper, and more useful. By the time the case reaches summary judgment, the actual dispute is often much more concrete than it looked in month one. That practical reality helps explain why the Ninth Circuit was skeptical of early dismissal in Quintara. Trade secret cases frequently need that back-and-forth process to separate truly secret material from general know-how, public information, and workplace memory.

There is also a business-side experience that rarely gets enough attention: morale and trust. When a company sues over trade secrets, employees start wondering what information they are allowed to use, what belongs to the company, and where ordinary skill ends and proprietary knowledge begins. Managers become more careful. Departing employees become more nervous. Compliance teams become suddenly popular. In that environment, a clear internal understanding of what counts as a trade secret is not just litigation hygiene. It is a management tool. Companies that can identify their sensitive information internally tend to communicate better externally, whether to courts, counterparties, or employees walking toward the exit with a laptop bag and suspiciously perfect timing.

Conclusion

The podcast on the Ninth Circuit’s trade secret identification ruling is worth attention because it captures a rule change with real strategic consequences. Quintara does not erase the need for specificity, and it does not make trade secret claims easier in every respect. What it does is reject the automatic grafting of California’s early disclosure rule onto a DTSA-only claim and remind federal courts that trade secret identification is usually a fact-heavy issue that matures through discovery.

That is a meaningful shift. It gives plaintiffs in federal court more room to develop their claims without immediate procedural amputation, while still preserving the defendant’s right to demand clarity and challenge weak trade secret theories on a proper record. The podcast’s lasting value is that it turns a technical appellate issue into a practical lesson: in trade secret law, timing is substance wearing procedural clothing.

SEO Tags