Background
Wall Street Business Academy, Inc. sued SDSol Technologies, LLC for breach of contract, alleging SDSol failed to deliver a functional source code for a web and mobile application. Wall Street claimed it was forced to hire its own developers to create a working application, called iYurek, and sought damages for that expense. In response, SDSol counterclaimed for unpaid development work.
During discovery, SDSol requested a complete copy of the iYurek application’s source code to determine if its own work product had been used in the new application. Wall Street objected, asserting the code was a protected trade secret. The trial court engaged in a lengthy discovery process, involving multiple hearings and attempts to have experts or witnesses opine on the matter without full disclosure.
After Wall Street failed to produce key witnesses and objected to the cost-sharing appointment of a neutral expert reviewer, the trial court ordered Wall Street to produce the iYurek source code directly to SDSol. The order specified the code was only for evaluating its origin and prohibited disclosure to third parties, but allowed access by SDSol itself. Wall Street then filed a petition for a writ of certiorari, arguing this order would cause irreparable harm by disclosing its trade secrets.
The Court’s Holding
The Third District Court of Appeal granted the petition in part and denied it in part. The court agreed with the trial court’s finding that production of the source code was reasonably necessary for discovery. It noted that Wall Street’s own expert testified that reviewing the code was “pretty much the only way” to determine if SDSol’s original work was incorporated into the iYurek application. The court held that Wall Street could not use the trade secret privilege as a shield while simultaneously putting the code’s development at the center of its damages claim.
However, the appellate court found that the trial court’s protective order was not narrowly tailored enough to safeguard Wall Street’s trade secrets. Because SDSol is a direct competitor, allowing the company itself—rather than just its designated expert or attorney—to review the source code created a “palpable and irreparable risk of misappropriation.” The court concluded that if the iYurek code was developed independently, SDSol should not be privy to it.
Accordingly, the court quashed the confidentiality portion of the trial court’s order and remanded the case, instructing the lower court to implement a more restrictive protective order. The suggested safeguards included limiting disclosure solely to SDSol’s attorney and experts, who would be barred from sharing it with their client without a further court order.
Key Takeaways
- A party cannot claim trade secret privilege to block discovery of information that is central to its own claims and damages.
- When ordering the production of a trade secret, courts must follow a three-step analysis: (1) determine if a trade secret exists, (2) assess whether production is reasonably necessary, and (3) craft safeguards to protect the information.
- In litigation between direct competitors, a protective order for source code or other trade secrets must be narrowly tailored, often by limiting disclosure to attorneys and outside experts only, to prevent the opposing party from gaining an unfair competitive advantage.
Why It Matters
This opinion highlights the critical tension between the need for broad discovery in litigation and the imperative to protect valuable intellectual property. The ruling serves as a practical guide for courts and litigants in technology disputes, emphasizing that a claim of trade secret privilege is not absolute. When a company puts the originality and development of its software at issue, it must be prepared to allow the opposing side to verify those claims.
The decision reinforces that the solution is not to block discovery entirely, but to control it through carefully structured protective orders. By insisting on an “expert-only” review, the court provides a clear framework for preventing litigation from becoming a tool for corporate espionage. This is particularly relevant for software development firms and tech companies whose source code represents a core business asset.