{"id":128405,"date":"2020-12-20T12:15:18","date_gmt":"2020-12-20T17:15:18","guid":{"rendered":"https:\/\/ipwatchdog.com\/?p=128405"},"modified":"2020-12-22T14:04:02","modified_gmt":"2020-12-22T19:04:02","slug":"take-heed-lessons-top-trade-secret-cases-2020","status":"publish","type":"post","link":"https:\/\/ipwatchdog.com\/2020\/12\/20\/take-heed-lessons-top-trade-secret-cases-2020\/id=128405\/","title":{"rendered":"Take Heed: Lessons from the Top Trade Secret Cases of 2020"},"content":{"rendered":"

\u201cOn motions to seal, which can consume a great deal of the court\u2019s time and effort, get it right the first time. And by the way, be scrupulously aware of variations in rules among district courts.\u201d<\/p>\n<\/div>\n

\"https:\/\/depositphotos.com\/189494614\/stock-photo-word-lessons-learned-written-on.html\"<\/a>One of the uniquely fascinating aspects of trade secret disputes is that they are laced with unbridled emotions, accusations of treachery, and actors who angrily disagree over basic facts. In other words, they provide a perfect metaphor for the year 2020.<\/p>\n

Let\u2019s take a look back at the cases this year that are worthy of comment, either because they involved some unusual set of facts or because they provide useful guidance for behaving better in 2021.<\/p>\n

Damages<\/strong><\/h2>\n

First, this year brought two massive verdicts in trade secret cases. February\u2019s Chicago jury verdict in Motorola v. Hytera<\/em> came in at $764 million, of which $418 million was for punitive damages. Then, in October, a jury in the New York case by Cognizant against Syntel awarded $854 million, including $570 million in punitives. Even more remarkable, the same trial counsel represented the plaintiffs in each case. Congratulations, Kirkland & Ellis! See, some people had a very good year in 2020.<\/p>\n

A big award in another case got reduced, in Epic v. Tata<\/a><\/em>, 971 F.3d 662 (7th<\/sup> Cir. 2020). The jury had awarded $240 million in compensatory damages and $700 million in punitives. The trial court reduced the damages to $140 million and limited the punitive award to twice that amount under the Uniform Trade Secrets Act (UTSA). On appeal, the 7th<\/sup> Circuit held that constitutional due process required a further reduction in the punitive award to $140 million. Still, the case is another reminder that unethical behavior (here, accessing a competitor\u2019s data by misleading a customer) can lead to enormous awards.<\/p>\n

In Ajaxo v. E*Trade<\/a><\/em>, 48 Cal.App.5th<\/sup> 129 (2020), the court confirmed that it was acceptable to use the \u201cGeorgia-Pacific factors\u201d from patent law in order to inform the damage analysis in a trade secret case.<\/p>\n

DTSA Extraterritoriality<\/strong><\/h2>\n

One of the lingering questions since enactment of the Defend Trade Secrets Act (DTSA) in 2016 has been whether the pre-existing provisions of the Economic Espionage Act establishing jurisdiction over foreign misappropriation would apply to civil cases as well. The first decision analyzing this question came in January, in Motorola v. Hytera<\/em><\/a>, 436 F.Supp.3d 1150 (N.D. Ill. 2020), ruling that the statute did apply where at least one act in furtherance of the \u201coffense\u201d occurred in the U.S. That ruling enabled the large verdict referred to earlier; but its continuing impact is potentially much broader, given the international character of many business relationships. And just to sharpen the point, the court in vPersonalize v. Magnetize<\/a><\/em>, 437 F.Supp.3d 860 (W.D. Wash. 2020) ruled that the \u201cact in furtherance\u201d need not have been committed by the defendant.<\/p>\n

Loss of Secrecy<\/strong><\/h2>\n

To qualify information as a trade secret, the owner must show \u201creasonable efforts\u201d to keep it confidential. Increasingly, courts are unwilling to excuse what looks like sloppy behavior by the plaintiff. In Amgen v. California Correctional<\/a><\/em>, 47 Cal.App.5th<\/sup> 716 (2020), the court said that merely putting the word \u201cconfidential\u201d on an email blast to 170 people wasn\u2019t enough. And in a real sign of our times, the contents of a Zoom meeting among franchise owners lost confidentiality protection because the organizers did not require passwords or keep accurate track of who gained access to the call. Smash Franchise v. Kanda<\/a><\/em>, 2020 Del.Ch. LEXIS 263. On the other hand, in Ultimate Timing v. Simms<\/em>, 715 F.Supp.3d 1195 (W.D. Wash. 2020), the court found that an email request to treat information as confidential was sufficient.<\/p>\n

Ownership<\/strong><\/h2>\n

The DTSA defines an owner as one who has rightful possession of a secret, such as through a license. So mere possession is enough to establish standing to sue, even though the plaintiff had developed the information under a \u201cwork for hire\u201d contract that gave title to a third party. Advanced Fluid v. Huber<\/a><\/em>, 958 F.3d 168 (3d Cir. 2020). But merely claiming ownership of a patent improperly derived from a trade secret does not invoke a question of \u201cinventorship\u201d under the Patent Act, so removal on that basis to federal court is improper. Intellisoft v. Acer<\/a><\/em>, 955 F.3d 927 (Fed.Cir. 2020).<\/p>\n

Misappropriation<\/strong><\/h2>\n

Taking someone else\u2019s secret by \u201cimproper means\u201d is unlawful. Back in the 1970s, aerial surveillance of a construction site was condemned by a judge as a \u201cschoolboy\u2019s trick.\u201d The same expansive view of unethical business behavior animated the finding in Compulife v. Newman<\/a><\/em>, 959 F.3d 1288 (11th<\/sup> Cir. 2020) that using \u201cbots\u201d to \u201cscrape\u201d information from the plaintiff\u2019s publicly accessible website that was designed to provide data only to individual humans amounted to \u201cimproper means.\u201d That said, in the more common circumstance of departing employees, early intervention by lawyers can help their clients avoid liability. In Flatiron v. Carson<\/a><\/em>, 2020 U.S. Dist. LEXIS 48699 (SDNY), counsel advised, and the client adopted, a plan to reduce the risk of misuse of secrets by a former employee. As a result, the court rejected the plaintiff\u2019s claim of \u201cthreatened misappropriation.\u201d<\/p>\n

Noncompete Agreements<\/strong><\/h2>\n

Employee confidentiality agreements are typically viewed as fair and non-controversial. But if the employer gets aggressive and limits post-employment use of publicly available information, the nondisclosure agreement can be analyzed under the rules applicable to noncompete contracts, and declared unenforceable. TLS Mgmt. v. Rodriguez-Toledo<\/a><\/em>, 966 F.3d 46 (1st<\/sup> Cir. 2020). In California, employee noncompete agreements have long been outlawed. But oddly for the first time this year, a California court ruled what should have been obvious, that the prohibition does not apply during the term of employment, when duties of loyalty justify imposing that restriction. Techno Lite v. Emcod<\/a><\/em>, 44 Cal.App.4th<\/sup> 462 (2020). In another case dealing with California\u2019s ban on noncompetes, the court held that strict application of Business & Professions Code \u00a7 16600 is applied only to employee agreements, not to contracts between businesses, which are examined under a rule of reasonableness. Ixchel Pharma v. Biogen<\/a><\/em>, 9 Cal.5th<\/sup> 1130 (2020).<\/p>\n

Preservation of Evidence<\/strong><\/h2>\n

Because trade secret claims often come as a surprise to the defendant, and early procedural moves such as preliminary injunction applications can consume counsel\u2019s attention, it is possible to overlook some of the finer points about litigation holds and other aspects of evidence preservation. But turning off an autodelete function on the defendant company\u2019s email server is not viewed as one of the fine points. In Weride v. Kun Huang<\/a><\/em>, 2020 U.S. Dist. LEXIS 72738 (N.D. Cal.), the resulting destruction of evidence justified terminating sanctions and a fee award. So, pay attention; you have been warned.<\/p>\n

Identification of Secrets<\/strong><\/h2>\n

As we in the trade secret bar are fond of saying, ours is the only area of intellectual property where the subject matter is not laid out in a government document, and where a dispute may be the first time that anyone is required to articulate what the thing is. But even if a plaintiff as part of its sensible trade secret management program has made a list, you can be sure that it will be challenged in litigation as insufficient to inform the defense. Indeed, identification of trade secrets has become one of the most hotly contested aspects of any claim. There are legitimate competing interests at stake, and one of the positive developments in 2020 was the publication by the Sedona Conference of a Commentary<\/a> addressing this singularly challenging issue.<\/p>\n

While everyone is reading this helpful guide, the cases keep coming. In Jabil v. Essentium<\/a><\/em>, 2020 U.S. Dist. LEXIS 24371 (M.D. Fla.) the court held it sufficient to define secret software by providing file names and paths for 16,000 files. Sometimes litigants use experts to explain that because they can understand the description, the court should approve it. But the expert\u2019s elucidation itself has to be understandable. In Calendar Research v. StubHub<\/em>, 2020 U.S. Dist. LEXIS 112361 (C.D. Cal.), the court rejected what it characterized as \u201ca circuitous path of unexplained jargon.\u201d By comparison, the judge in Caudill Seed v. Jarrow<\/a><\/em>, 2020 U.S. Dist. LEXIS 94821 (W.D. Ken.) allowed the plaintiff to broadly claim a \u201cknowledge base\u201d derived from years of R&D.<\/p>\n

Finally on this subject, I refer to the recent opinion in Inteliclear v. ETC<\/a><\/em>, 978 F.3d 653 (9th<\/sup> Cir. 2020), not because it creates new law on identification, but only because some people think it does, and I respectfully disagree. The case is highly unusual because on the first day of discovery the defendant filed a motion for summary judgment directed at the insufficiency of the trade secret description. In opposition, the plaintiff provided additional information about its claim, but the trial court granted the motion anyway. On appeal, the Ninth Circuit held that the dimension of the plaintiff\u2019s trade secret was an issue of fact that couldn\u2019t be resolved summarily. The only real lesson of this case is never to challenge an initial trade secret description by an early motion for summary judgment; file a request for protective order instead. The case does not, as some have suggested it does, represent some new federal standard regarding identification of trade secrets.<\/p>\n

Requests to Seal Documents Filed in Court<\/strong><\/h2>\n

Protecting trade secrets in litigation is a concern in many kinds of cases where sensitive information has to be presented and the parties confront the tradition and constitutional requirements regarding public access to courts. Those requirements are not absolute, of course, but proper balancing of interests requires careful observance of court procedures for sealing. In Uniloc v. Apple<\/a><\/em>, 964 F.3d 1351 (Fed. Cir. 2020), the party filing its sealing motion was hardly discriminating; it asked the trial court to seal almost everything in the parties\u2019 briefs, \u201cincluding citations to case law and quotations from published opinions,\u201d along with a number of exhibits containing publicly available information. When that motion to seal was denied, the litigant came back with a more restrained request, but the court denied it, and the order was affirmed on appeal. The lesson: on motions to seal, which can consume a great deal of the court\u2019s time and effort, get it right the first time. And by the way, be scrupulously aware of variations in rules among district courts. In the Western District of Washington, for example, the sealing rules state that a request to withdraw material in case the motion is denied must be made at the time the motion is filed; asking for return of the material once you get a ruling is too late, and the information will be placed in the public record. Rydman v. Champion<\/a><\/em>, 2020 U.S. Dist. LEXIS 51101 (W.D. Wash.).<\/p>\n

My Personal Favorite<\/strong><\/h2>\n

It\u2019s been a long, and occasionally very frustrating, year. Having made it through 2020, we can all use a bit of comic relief. Sometimes it shows up in trade secret cases, usually unintentionally. In PB Legacy v. Am. Mariculture<\/a><\/em>, 2020 U.S. Dist. LEXIS 62947 (M.D. Fla.) we learn that trade secret protection extends to . . . shrimp. Who knew?<\/p>\n

 <\/p>\n

Image Source: Deposit Photos
\nAuthor: Milkos
\nImage ID: 189494614
\n<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

One of the uniquely fascinating aspects of trade secret disputes is that they are laced with unbridled emotions, accusations of treachery, and actors who angrily disagree over basic facts. In other words, they provide a perfect metaphor for the year 2020. Let\u2019s take a look back at the cases this year that are worthy of comment, either because they involved some unusual set of facts or because they provide useful guidance for behaving better in 2021.<\/p>\n","protected":false},"author":109117,"featured_media":119383,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","footnotes":"","_links_to":"","_links_to_target":""},"categories":[6998,266,228,3,38597,48],"tags":[72232,9383,49,454,72231,8728,72233],"yst_prominent_words":[53669,15339,15855,15854,15846,18133,17348,18134],"acf":[],"_links":{"self":[{"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/posts\/128405"}],"collection":[{"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/users\/109117"}],"replies":[{"embeddable":true,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/comments?post=128405"}],"version-history":[{"count":0,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/posts\/128405\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/media\/119383"}],"wp:attachment":[{"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/media?parent=128405"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/categories?post=128405"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/tags?post=128405"},{"taxonomy":"yst_prominent_words","embeddable":true,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/yst_prominent_words?post=128405"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}