<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.lexblog.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
   <channel>
      <title>Unfair Competition &amp; Trade Secrets Counsel</title>
      <link>http://www.unfaircompetitiontradesecretscounsel.com/</link>
      <description>Employer Rights Attorneys &amp; Lawyers: Littler Mendelson Law Firm</description>
      <language>en</language>
      <copyright>Copyright 2012</copyright>
      <lastBuildDate>Tue, 15 May 2012 09:17:40 -0800</lastBuildDate>
      <pubDate>Tue, 15 May 2012 09:17:40 -0800</pubDate>
      <generator>http://www.sixapart.com/movabletype/?v=4.32-en</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

      
      <feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="unfaircompetitiontradesecretscounsel" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://www.unfaircompetitiontradesecretscounsel.com/index.xml" /><feedburner:emailServiceId xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">UnfairCompetitionTradeSecretsCounsel</feedburner:emailServiceId><feedburner:feedburnerHostname xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://feedburner.google.com</feedburner:feedburnerHostname><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.bloglines.com/sub/http://www.unfaircompetitiontradesecretscounsel.com/index.xml" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://fusion.google.com/add?feedurl=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.plusmo.com/add?url=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://plusmo.com/res/graphics/fbplusmo.gif">Subscribe with Plusmo</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.thefreedictionary.com/_/hp/AddRSS.aspx?http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://img.tfd.com/hp/addToTheFreeDictionary.gif">Subscribe with The Free Dictionary</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.bitty.com/manual/?contenttype=rssfeed&amp;contentvalue=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://www.bitty.com/img/bittychicklet_91x17.gif">Subscribe with Bitty Browser</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.live.com/?add=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://tkfiles.storage.msn.com/x1piYkpqHC_35nIp1gLE68-wvzLZO8iXl_JMledmJQXP-XTBOLfmQv4zhj4MhcWEJh_GtoBIiAl1Mjh-ndp9k47If7hTaFno0mxW9_i3p_5qQw">Subscribe with Live.com</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://mix.excite.eu/add?feedurl=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://image.excite.co.uk/mix/addtomix.gif">Subscribe with Excite MIX</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.webwag.com/wwgthis.php?url=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://www.webwag.com/images/wwgthis.gif">Subscribe with Webwag</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.podcastready.com/oneclick_bookmark.php?url=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://www.podcastready.com/images/podcastready_button.gif">Subscribe with Podcast Ready</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.wikio.com/subscribe?url=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://www.wikio.com/shared/img/add2wikio.gif">Subscribe with Wikio</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.dailyrotation.com/index.php?feed=http%3A%2F%2Fwww.unfaircompetitiontradesecretscounsel.com%2Findex.xml" src="http://www.dailyrotation.com/rss-dr2.gif">Subscribe with Daily Rotation</feedburner:feedFlare><item>
         <title>The Importance of Pleading Actual Harm in Trade Secret Misappropriation Cases</title>
         <description><![CDATA[<p><em><img class="mt-image-left" style="float: left; margin: 0 20px 20px 0;" src="http://www.unfaircompetitiontradesecretscounsel.com/botox.jpg" alt="botox.jpg" width="424" height="283" />By </em><a href="http://www.littler.com/people/harry-d-jones" target="_blank"><em>Harry D. Jones</em></a></p>
<p>In an April 25, 2012 <a href="http://www.unfaircompetitiontradesecretscounsel.com/River%27s%20edge%20case%5B1%5D.pdf">ruling</a> [pdf] a Middle District of North Carolina court clearly illustrated the importance of pleading actual harm in an unfair competition case. &nbsp;By dismissing parts of a dispute between River&rsquo;s Edge Pharmaceuticals, a discount pharmaceutical product distributor, and Gorbec Pharmaceutical Services, Inc., a pharmaceutical manufacturer, the court ruled that speculation about potential harm &nbsp;is not enough to sustain a litigant&rsquo;s burden.</p>
<p>In 2003, River&rsquo;s Edge first developed products through an FDA-sanctioned program.&nbsp; River&rsquo;s Edge sought help from Gorbec in 2007 to manufacture and test generic drugs under an Abbreviated New Drug Application (ANDA) process.&nbsp; The parties contemplated preparing a written contract to memorialize their agreement, but never completed one.&nbsp; River&rsquo;s Edge submitted purchase orders to Gorbec to manufacture drugs to River&rsquo;s Edge&rsquo;s specifications.&nbsp;</p>
<p>In 2010, the relationship soured.&nbsp; River&rsquo;s Edge claimed Gorbec executives boasted of having the &ldquo;know-how, intellectual property, and regulatory approvals,&rdquo; threatened to stop work, and made plans to compete.&nbsp; Gorbec claimed River&rsquo;s Edge failed to pay Gorbec in full, and hid a warning letter from the FDA asking River&rsquo;s Edge to cease sales.&nbsp; Both sued.&nbsp; River&rsquo;s Edge&rsquo;s complaint alleged breaches of contract and fiduciary duty, fraud, promissory estoppel, unjust enrichment, conversion, and misappropriation of trade secrets; and sought declaratory relief. &nbsp;Gorbec&rsquo;s counterclaim was almost a mirror image, alleging breach of contract, unjust enrichment, negligent misrepresentation, fraud, and deceptive trade practices.</p><p>Both parties moved to dismiss for failure to state a claim under the Federal Rules of Civil Procedure, as interpreted by the U.S. Supreme Court in <em>Ashcroft v. Iqbal</em>, 556 U.S. 662, 678 (2009); the only count not included in the Rule 12(b)(6) motions was River&rsquo;s Edge&rsquo;s declaratory judgment request.&nbsp; The court granted many parts of the dueling motions.&nbsp; What survived?&nbsp;</p>
<p><em>River&rsquo;s Edge&rsquo;s Claims Trimmed</em></p>
<p>River&rsquo;s Edge was left with a fiduciary breach claim based on Gorbec&rsquo;s alleged refusal to provide River&rsquo;s Edge with all FDA communications on pending ANDA work, conversion and trade secret misappropriation claims, and a contract claim for the alleged cessation of ANDA work.&nbsp; However, the court dismissed the contract claims based on Gorbec&rsquo;s alleged statements of ownership or intent to compete, fiduciary claims for any &ldquo;threatened or potential conduct,&rdquo; claims for constructive fraud and unjust enrichment, and made it clear that as to the misappropriation claims, River&rsquo;s Edge had to be able to prove Grobec had the opportunity to acquire, use and disclose trade secrets without consent.</p>
<p><em>Gorbec&rsquo;s Counterclaims Narrowed</em></p>
<p>The court dismissed Gorbec&rsquo;s counterclaim for negligent misrepresentation entirely, dismissed part of the fraud counterclaim to the extent it was based on the idea that River&rsquo;s Edge formed its own manufacturing company in order to get around its contract, and dismissed part of the contract counterclaim to the extent it was based on River&rsquo;s Edge&rsquo;s failure to enter into the <em>anticipated</em> written agreement.&nbsp; The court denied the motion to dismiss for unfair and deceptive trade practices and unjust enrichment, finding sufficient information to state a claim; and denied the motion as to the part of the contract claim based on the actual ANDA work Gorbec had done, and denied dismissal of the fraud counterclaim to the extent it was based on fraudulent concealment of the FDA warning letter.&nbsp;</p>
<p><em>Lessons Learned</em></p>
<p>As the court&rsquo;s ruling demonstrates, in the arena of unfair competition, it is paramount to avoid speculative language about potential harm.&nbsp; Instead, courts in trade secret misappropriation cases will look for plaintiffs to identify the specific injury the alleged theft has cost them.&nbsp;</p>]]></description>
         <link>http://www.unfaircompetitiontradesecretscounsel.com/trade-secrets-1/the-importance-of-pleading-actual-harm-in-trade-secret-misappropriation-cases/</link>
         <guid isPermaLink="false">http://www.unfaircompetitiontradesecretscounsel.com/trade-secrets-1/the-importance-of-pleading-actual-harm-in-trade-secret-misappropriation-cases/</guid>
         <category domain="http://www.unfaircompetitiontradesecretscounsel.com/">Trade Secrets</category>
         <pubDate>Tue, 15 May 2012 09:07:19 -0800</pubDate>
         <dc:creator>Unfair Competition &amp; Trade Secrets Counsel</dc:creator>










      </item>
      
      <item>
         <title>New York Court: Plaintiff Must Identify Trade Secrets</title>
         <description><![CDATA[<p><em>By <a href="http://www.littler.com/people/harry-d-jones" target="_blank">Harry D. Jones</a></em></p>
<p>A conundrum employers face when protecting trade secrets is the obligation to identify the very secrets to be protected in litigation.&nbsp; A critical issue in the context of discovery is the extent to which trade secrets must be disclosed and identified by the plaintiff.&nbsp; When the secret is something as technical and unique as a computer source code alleged to have been used to augment a competitor&rsquo;s source code library, the requirement to identify the misappropriated secret with &ldquo;reasonable particularity&rdquo; early in the case may become the &ldquo;case within the case.&rdquo;</p>
<p>A recent example of a fight not to be the first party to identify source code in discovery is the New York state court case of <a href="http://www.unfaircompetitiontradesecretscounsel.com/MSCI.pdf" target="_blank"><em>MSCI, Inc. v. Jacob and Axioma, Inc.</em></a> [pdf], where Supreme Court Judge Shirley Kornreich ruled the plaintiffs had to identify the components and sequencing of both the secret and the publicly known source code to the defendants, before discovery could proceed.</p>
<p>The plaintiffs claimed their former employee (who was not subject to a non-compete clause) had taken, used, and disclosed portions of source code to his new employer Axioma, who had embedded parts of that secret source code in its own financial market software.&nbsp; The plaintiffs first characterized the entire source code &ldquo;reference library&rdquo; as a trade secret, even though parts of that code are in the public domain or licensed.&nbsp; Their backup argument was that &ldquo;certain details of the specific implementation&rdquo; of even the publicly known code were trade secrets.&nbsp; The plaintiffs proposed to only identify which parts of its source code were not trade secrets, and maintained this was a more practical and cost-efficient, yet legally sufficient way to meet its burden of trade secret identification.&nbsp; An earlier preliminary ruling by the court affirmed that approach.</p><p>However, the issue came to a head when the plaintiffs sought full disclosure by the defendants of the Axioma source code library first.&nbsp; The defendants argued that before the plaintiffs could obtain or inspect Axioma&rsquo;s source code library, the plaintiffs should be made to reveal the precise parts of source code it claimed were trade secrets.&nbsp;</p>
<p>Judge Kornreich was &ldquo;persuaded that the law requires that a trade secret plaintiff identify trade secrets with reasonable particularity early in the case&rdquo; (citing <em>Xerox Corp. v. IBM Corp.</em>, 64 F.R.D. 367, 371 (S.D.N.Y. 1974) for the proposition that trade secret defendants should not be made to &ldquo;guess at what they are&rdquo; and that only after identification of a trade secret lost can a defendant &ldquo;undertake a meaningful discovery program...&rdquo;; and noting that California has codified this requirement at Cal. Code Civ. Proc. &sect;2019.210).&nbsp; Judge Kornreich reasoned that distinguishing between &ldquo;general knowledge in the field&rdquo; and trade secrets would allow the court to set the &ldquo;parameters of discovery&rdquo; and make the defendants &ldquo;able to prepare their defense.&rdquo;&nbsp; The judge even observed that the plaintiffs, once privy to Axioma&rsquo;s source code, &ldquo;could tailor their theory of misappropriation&rdquo; or even misappropriate Aximoa&rsquo;s trade secrets.&nbsp;</p>
<p>Before the plaintiffs can seek further discovery from the defendants, they must identify with reasonable particularity which of the &ldquo;component parts or sequencing of their source code&rdquo; are not publicly available, commonly used, or licensed from third parties.</p>
<p>This order has expensive and important ramifications in the case at issue, and generally, in source code misappropriation litigation.&nbsp; A vital consideration in launching trade secret cases is the cost (dollar and competitive) of disclosure and identification of the secrets lost.</p>]]></description>
         <link>http://www.unfaircompetitiontradesecretscounsel.com/trade-secrets-1/new-york-court-plaintiff-must-identify-trade-secrets/</link>
         <guid isPermaLink="false">http://www.unfaircompetitiontradesecretscounsel.com/trade-secrets-1/new-york-court-plaintiff-must-identify-trade-secrets/</guid>
         <category domain="http://www.unfaircompetitiontradesecretscounsel.com/">Trade Secrets</category>
         <pubDate>Wed, 09 May 2012 17:13:55 -0800</pubDate>
         <dc:creator>Unfair Competition &amp; Trade Secrets Counsel</dc:creator>




      </item>
      
      <item>
         <title>Can "Friends" Be Trade Secrets? </title>
         <description><![CDATA[<p><img class="mt-image-left" style="float: left; margin: 0 20px 20px 0;" src="http://www.unfaircompetitiontradesecretscounsel.com/SocialMediaII.jpg" alt="SocialMediaII.jpg" width="350" height="232" />By <a href="http://www.littler.com/people/corinne-k-hays">Corinne K. Hays</a> and <a href="http://www.littler.com/people/william-j-leahy">William J. Leahy</a></p>
<p>Unfair competition litigation frequently involves disputes over whether information actually constitutes a trade secret.&nbsp; Given the prevalent use of social media by both businesses and individuals, it is not surprising that courts have begun to address whether such information can be a trade secret.&nbsp; In November, a California federal court <a href="http://www.unfaircompetitiontradesecretscounsel.com/trade-secrets-1/claim-that-ex-employee-twittered-away-company-trade-secrets-allowed-to-proceed/">refused to dismiss</a> a claim that Twitter account information was protected as a trade secret. &nbsp;A recent decision from the District of Colorado opened the door to allowing businesses to protect their Facebook and MySpace &ldquo;friends&rdquo; list as a possible trade secret.</p>
<p>In <a href="http://www.unfaircompetitiontradesecretscounsel.com/Christou%20v%20Beatport%5B1%5D.pdf">Christou v. Beatport, LLC</a> [pdf], the plaintiffs, including several Denver area night clubs, brought numerous claims against a former employee and the companies that he founded.&nbsp; The claims included an allegation of misappropriation of trade secrets.&nbsp; Specifically, the plaintiffs alleged that the defendants misappropriated their login information to access profiles on MySpace and lists of MySpace &ldquo;friends.&rdquo;&nbsp; The defendants moved to dismiss this claim, arguing that the plaintiffs failed to allege sufficient facts to demonstrate that their MySpace profile and &ldquo;friends&rdquo; list qualify as trade secrets.&nbsp;</p>
<p>Colorado has adopted the Uniform Trade Secrets Act and defines a trade secret as the &ldquo;whole or any portion or phase of any scientific or technical information, design, process, procedure, formula, improvement, confidential business or financial information, list of names, addresses, or telephone numbers, or other information relating to any business or profession which is secret and of value.&rdquo;&nbsp; C.R.S. &sect; 7-74-102(4).&nbsp; Additionally, the owner of a trade secret must have &ldquo;taken measures to prevent the secret from becoming available to persons other than those selected by the owner to have access thereto for limited purposes.&rdquo;</p><p>To determine if the MySpace lists could potentially constitute trade secrets under Colorado law, the court looked to eight factors:</p>
<p style="padding-left: 30px;">(1) whether proper and reasonable steps were taken by the owner to protect the secrecy of the information; (2) whether access to the information was restricted; (3) whether employees knew customers&rsquo; names from general experience; (4) whether customers commonly dealt with more than one supplier; (5) whether customer information could be readily obtained from public directories; (6) whether customer information is readily ascertainable from sources outside the owner&rsquo;s business; (7) whether the owner of the customer list expended great cost and effort over a considerable period of time to develop the files; and (8) whether it would be difficult for a competitor to duplicate the information.</p>
<p>Applying these factors, the court first noted that the plaintiffs took reasonable steps to protect the secrecy of their information because they secured the profiles through web profile login and passwords.&nbsp; Further, the login and password information was restricted to personnel, including the former employee, who required access in order to promote the night clubs.&nbsp;</p>
<p>The court also found that the defendants could not have gleaned the list of names from general experience.&nbsp; Rather, the list of &ldquo;friends&rdquo; was more than a simple list of names of potential customers.&nbsp; In its analysis, the court noted that &ldquo;&lsquo;[f]riending&rsquo; a business or individual grants that business or individual access to some of one&rsquo;s personal information, information about his or her interests and preferences, and perhaps most importantly for a business, contact information and a built-in means of contact.&rdquo; The names themselves, readily available to the public, are not the important factor.&nbsp; &nbsp;</p>
<p>The court also noted that the plaintiffs expended at least some cost and effort in developing the social networking aspect of its business.&nbsp; In fact, while employed by plaintiffs, the former employee defendant was paid to assist in building, maintaining, and using the lists and profiles.&nbsp;</p>
<p>After analyzing the relevant factors, the court denied the motion to dismiss, concluding that the plaintiffs had alleged sufficient facts to maintain their trade secret claim as to the MySpace information.&nbsp; Because the existence of a trade secret is inherently fact-specific, it remains to be seen whether this claim will ultimately succeed and whether other employers will be able to assert trade secret protection for social media information.&nbsp; Given the use of social media and the ease with which electronic information can be copied or transferred, this will become an increasingly common claim in litigation.&nbsp;</p>]]></description>
         <link>http://www.unfaircompetitiontradesecretscounsel.com/trade-secrets-1/can-friends-be-trade-secrets/</link>
         <guid isPermaLink="false">http://www.unfaircompetitiontradesecretscounsel.com/trade-secrets-1/can-friends-be-trade-secrets/</guid>
         <category domain="http://www.unfaircompetitiontradesecretscounsel.com/">Trade Secrets</category>
         <pubDate>Wed, 02 May 2012 13:53:27 -0800</pubDate>
         <dc:creator>Unfair Competition &amp; Trade Secrets Counsel</dc:creator>







      </item>
      
      <item>
         <title>Should Courts Revisit the Rule Limiting a Non-Competition Injunction to the Term Provided in an Employment Contract?</title>
         <description><![CDATA[<p><em>By </em><a href="http://www.littler.com/people/shannon-morales"><em>Shannon Morales</em></a><em></em></p>
<p>It is well-established that an injunction to enforce a non-compete provision should not extend beyond the period set forth in the non-compete agreement.&nbsp; Whether based on the belief that a contract should be enforced as written or because restrictive covenants are generally not favored by law, the majority of courts have declined to enforce a non-compete provision beyond the expiration of the period set forth in the agreement.&nbsp; In its March 1, 2012 decision in <a href="http://www.unfaircompetitiontradesecretscounsel.com/Finkel.pdf">Finkel v. Cashman Prof.</a> [pdf], the Nevada Supreme Court reinforced this rule.&nbsp; The New Jersey Supreme Court has reached the same conclusion.&nbsp; <em>See</em> <em>Community Hospital Group v. More,</em> 183 N.J. 36, 63 (2005).&nbsp;&nbsp; But have the courts considered whether this solution is sufficient?&nbsp; In an effort to enforce the plain terms of the contract, are courts depriving employers of the benefit of their bargain?&nbsp; Some argue that in limiting a non-competition injunction to the period provided for in the non-compete agreement, courts have largely failed to award the relief necessary to fully compensate employers for the injuries incurred by a breached non-compete provision.&nbsp;</p>
<p>In New Jersey, courts follow the rule that non-competes should not extend beyond the period set forth in the non-compete agreement with one catch: a non-compete provision may be enforced beyond the expiration of the term in the agreement if no other relief (i.e. monetary damages) is available.&nbsp; In <em>Jackson Hewitt, Inc. v. Childress</em>, 2008 U.S. Dist. LEXIS 4640 (D.N.J. 2008), the district court issued a twenty-four month injunction, prohibiting the defendant from competing with the company, but only because it was evident monetary damages were not available.&nbsp; In <em>Childress</em>, the defendant, who had &ldquo;openly refused to comply&rdquo; with his non-compete obligations, filed for bankruptcy two days after the company brought suit seeking a preliminary injunction.&nbsp; By the time the district court addressed the issue, the twenty-four month non-compete period had expired.&nbsp; At that point, because the defendant filed for bankruptcy (discharging the plaintiff&rsquo;s claim), issuing a new twenty-four month injunction, based on the non-compete period in the contract, was the only remedy for the plaintiff&rsquo;s injury.&nbsp;</p>
<p>The question is whether a non-compete provision should be enforced as written, and expire at the end of the period specified by the contract, as in <em>More </em>and <em>Finkel</em>, or whether the injured party is entitled to an injunction prohibiting the breaching party from competing for the full period set forth in the agreement, as done in <em>Childress</em>.&nbsp; While the <em>Childress</em> court prohibited the defendant&rsquo;s competitive behavior for an extended twenty-four month period, the court explained that this remedy was issued only because a monetary remedy was not available.&nbsp; To remedy wrongful competitive behavior, an injunction should issue prohibiting competitive behavior for the full non-compete period set forth in the contract.&nbsp; This is not to say that the injured party should not be entitled to damages; rather, an injunction reflecting the duration anticipated by the non-compete provision should issue <em>separate and apart</em> from a monetary award to compensate the injured party for damages incurred.&nbsp;</p><p>Some argue that to enforce the full non-compete period (for example, 12 months), in addition to providing monetary damages, would amount to a double recovery for the injured party.&nbsp; This is not the case.&nbsp; For example, if an employee subject to a 12-month non-compete provision separated from his employer on January 1, 2012 and abided by the non-compete term, which would expire on December 31, 2012, he would have engaged in no competitive activities during the non-compete period and the company would have suffered no injury.&nbsp;</p>
<p>If, however, the former employee began to engage in competitive activities shortly after he separated from employment on January 1, 2012, and the company discovered the breach on April 1, filed a lawsuit on April 15, and obtained a preliminary injunction on July 1, according to the decisions in <em>More</em> and <em>Finkel</em>, the non-compete would only remain in effect &nbsp;until January 1, 2013, the date the non-compete period would have ended pursuant to the contract.&nbsp; In this case, the employer would suffer two separate injuries: (1) the loss of the 12-month non-compete period it bargained for; and (2) the damages incurred by the former employee&rsquo;s nefarious activities in breach of the agreement.</p>
<p>Employers should be aware that the current rule generally enforces a non-compete provision only through the contractual expiration of the term, which only partially addresses the employer&rsquo;s injury.&nbsp; To make the injured party whole, a 12-month injunction (to address the first injury), in addition to monetary damages (to address the second injury) would be necessary to provide the company a complete recovery from a former employee&rsquo;s breach of a non-compete agreement.&nbsp;&nbsp;&nbsp;</p>
<p><em><strong>An Alternative Solution</strong></em></p>
<p>Because courts may continue to issue preliminary injunctions focusing on the non-compete period provided in the agreement, employers may want to consider adding language to the non-compete agreements to ensure they will receive the benefit of the full non-compete period in the event of the employee&rsquo;s breach.&nbsp; In a recent New York Appellate Division case, the court supported this creative solution.&nbsp;</p>
<p>In <a href="http://www.unfaircompetitiontradesecretscounsel.com/Delta%20Complaint%20PDF1.pdf">Delta Enterprise v. Cohen</a> [pdf], a New York appellate court held that, in issuing a preliminary injunction, the trial court should have enforced the tolling provision set forth in a confidentiality agreement.&nbsp; In <em>Cohen</em>, the agreement contained language that provided for the tolling of various restrictive periods &ldquo;during any period in which the Employee is in violation&rdquo; of the restrictive covenants, and that &ldquo;all restrictions shall automatically be extended by the period Employee was in violation of any such restrictions.&rdquo;&nbsp; In determining that the company was entitled to the restrictive period contained in the agreement, the court rejected the employee&rsquo;s arguments that the tolling provision was, as a matter of law, unenforceable or in violation of public policy, particularly in light of the consideration the employee received.&nbsp;</p>
<p>In light of <em>Cohen</em>, companies should consider adding tolling language to their non-compete agreements to ensure they will receive the benefit of the full non-compete period anticipated by the agreement.&nbsp; Without such language, a company can expect to receive only partial recovery for the injuries incurred due to a former employee&rsquo;s failure to abide by his non-compete obligations.&nbsp;</p>]]></description>
         <link>http://www.unfaircompetitiontradesecretscounsel.com/covenants-not-to-compete/should-courts-revisit-the-rule-limiting-a-non-competition-injunction-to-the-term-provided-in-an-empl/</link>
         <guid isPermaLink="false">http://www.unfaircompetitiontradesecretscounsel.com/covenants-not-to-compete/should-courts-revisit-the-rule-limiting-a-non-competition-injunction-to-the-term-provided-in-an-empl/</guid>
         <category domain="http://www.unfaircompetitiontradesecretscounsel.com/">Covenants Not To Compete</category>
         <pubDate>Tue, 24 Apr 2012 14:42:59 -0800</pubDate>
         <dc:creator>Unfair Competition &amp; Trade Secrets Counsel</dc:creator>







      </item>
      
      <item>
         <title>Ninth Circuit Rules the CFAA Requires Proof of Hacking</title>
         <description><![CDATA[<p><em><img class="mt-image-left" style="float: left; margin: 0 20px 20px 0;" src="http://www.unfaircompetitiontradesecretscounsel.com/Locked%20Keyboard.jpg" alt="Locked Keyboard.jpg" width="300" height="199" />By <a href="http://www.littler.com/people/lena-k-sims" target="_blank">Lena K. Sims</a> </em></p>
<p>Last week, the Ninth Circuit published its long awaited <em>en banc</em> decision, authored by Chief Judge Alex Kozinski, in <a href="http://www.unfaircompetitiontradesecretscounsel.com/UnitedStatesVsNosal.pdf"><em>United States v. Nosal</em></a> [pdf].&nbsp; The 9-2 reversal of the 3-judge appellate decision&nbsp;holds that the <a href="http://www.law.cornell.edu/uscode/text/18/1030" target="_blank">Computer Fraud and Abuse Act's</a> phrase &ldquo;exceeds authorized access&rdquo; is limited to violations of restrictions on <em>physical access to information</em> and does not extend to violations of restrictions on <em>the use of information</em>.&nbsp; Prosecution under the CFAA thus requires proof of &ldquo;hacking&rdquo; and employers will not be able to bring a claim for violation of the CFAA based on a violation of a computer <em>use</em> policy.&nbsp; &nbsp;&nbsp;</p>
<p>The decision calls out for United States Supreme Court review.&nbsp; It departs from the Fifth, Seventh and Eleventh Circuit decisions concerning interpretation of the same statutory language and criticizes those courts for taking a short-sighted approach that focused on the facts of the cases before them while criminalizing acts that are wide-spread, commonplace and trivial. &nbsp;</p>
<p>Unlike those cases, the <em>Nosal</em> decision makes only a quick introductory recitation of the facts of the case.&nbsp; Those following the case will recall that Nosal persuaded his former colleagues still working for his former employer to help him start a competing business by accessing information from the company&rsquo;s database and then transferring that information to Nosal.&nbsp; The employees had access to the database, but use of the information was restricted by policy:&nbsp; &ldquo;This product is intended to be used by Korn/Ferry employees for work on Korn/Ferry business only.&rdquo;&nbsp; Nosal was criminally prosecuted for aiding and abetting the employees in &ldquo;exceeding their authorized access&rdquo; with intent to defraud the employer.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p><p>The <em>Nosal</em> decision sets aside its factual underpinnings and takes an expansive and some may say alarmist view of the CFAA&rsquo;s potential impact, focusing on the ubiquity of computers and internet use in contemporary society generally and in the workplace. &nbsp;It envisions employees being charged with federal crimes for &ldquo;g-chatting with friends, playing games, shopping, or watching sports highlights&rdquo; while at work and in violation of their employer&rsquo;s policies prohibiting use of the employer&rsquo;s computer systems for those activities.&nbsp; These are &ldquo;minor workplace dalliances&rdquo; that employers&rsquo; policies would turn into federal crimes. &nbsp;While the CFAA <em>could</em> be interpreted to criminalize violations of such use policies, the <em>en banc </em>panel rejected that interpretation to avoid the undesirable result of criminalizing common-place conduct that is not inherently wrong and which is without criminal intent.&nbsp; &nbsp;&nbsp;</p>
<p>Where does this leave employers?&nbsp; While <em>Nosal</em> was a criminal case, it is not limited to application in the criminal context. Very few employment cases are prosecuted criminally, and because the decision itself arises out of the employment context, its application in the civil context is expected.&nbsp; While California employers may still bring claims for trade secret misappropriation, breach of contract, and certain torts, they will likely not have a basis for claiming federal subject matter jurisdiction under the CFAA. While they may no longer have a federal claim, employers will still want to have policies that clearly and appropriately restrict both <em>access to</em> and <em>use</em> <em>of</em> their information.&nbsp;&nbsp;</p>]]></description>
         <link>http://www.unfaircompetitiontradesecretscounsel.com/federal-law/ninth-circuit-rules-the-cfaa-requires-proof-of-hacking/</link>
         <guid isPermaLink="false">http://www.unfaircompetitiontradesecretscounsel.com/federal-law/ninth-circuit-rules-the-cfaa-requires-proof-of-hacking/</guid>
         <category domain="http://www.unfaircompetitiontradesecretscounsel.com/">Federal Law</category>
         <pubDate>Thu, 19 Apr 2012 11:06:12 -0800</pubDate>
         <dc:creator>Unfair Competition &amp; Trade Secrets Counsel</dc:creator>







      </item>
      
      <item>
         <title>Seventh Circuit Case Highlights Importance of Documenting Steps to Maintain Privacy of Trade Secrets</title>
         <description><![CDATA[<p><em><img class="mt-image-left" style="float: left; margin: 0 20px 20px 0;" src="http://www.unfaircompetitiontradesecretscounsel.com/law%20books.JPG" alt="law books.JPG" width="425" height="282" />By </em><a href="http://www.littler.com/people/matthew-j-hank"><em>Matthew J. Hank</em></a><em></em></p>
<p>Under the Uniform Trade Secrets Act, a &ldquo;trade secret&rdquo; is information that (1) derives independent economic value by virtue of its being secret; and (2) is the subject of reasonable efforts by the plaintiff to maintain its secrecy.&nbsp; Although the first criterion is often discussed in judicial opinions, the second is not. The recent Seventh Circuit Court of Appeals case <a href="http://www.unfaircompetitiontradesecretscounsel.com/Fail-Safe%20opinion%5B1%5D.pdf">Fail-Safe, LLC v. A.O. Smith Corporation</a><em> </em>[pdf], No. 11-1354 (Mar. 29, 2012)&nbsp;is among the few reported cases that turn on the second prong of analysis.</p>
<p>Fail-Safe, LLC and A.O. Smith Corporation (AOS) held a series of discussions over the course of two years concerning a possible joint project to develop technology to make swimming pool drains safer.&nbsp; Throughout these meetings and conversations, Fail-Safe shared with AOS sensitive technical information.&nbsp; Yet Fail-Safe never entered an agreement requiring AOS to keep that information confidential, nor did Fail-Safe even identify the information it provided to AOS as confidential.&nbsp; (AOS, by contrast, required Fail-Safe to sign a one-way confidentiality agreement.)&nbsp; After the two companies decided not to pursue the joint development project, Fail-Safe alleged AOS introduced two pump motors incorporating Fail-Safe&rsquo;s trade secrets.&nbsp; Fail-Safe then filed a complaint alleging, among other things, that AOS thus violated the Uniform Trade Secrets Act.</p>
<p>The district court granted summary judgment in favor of AOS, reasoning (in relevant part) that, because Fail-Safe failed to take reasonable steps to protect the secrecy of its data, the information that AOS allegedly incorporated into its pump motors was not a trade secret.&nbsp; The Seventh Circuit affirmed on the ground that, because Fail-Safe &ldquo;failed to take any steps&rdquo; to maintain the secrecy required for trade secret protection, its claim failed as a matter of law.&nbsp;</p><p>Although <em>Fail-Safe</em> did not arise in the employment context, and the Seventh Circuit aptly characterized <em>Fail-Safe</em> as an &ldquo;extreme case,&rdquo; it underscores the importance of an employer&rsquo;s documenting the steps it took to maintain the secrecy of any information it seeks to protect.&nbsp; For example, an employer may include in its employees&rsquo; restrictive covenants a provision identifying the categories of the employer&rsquo;s secrets, noting how those secrets are protected (e.g., via employee confidentiality agreements, password protections, etc.), and requiring the employee&rsquo;s acknowledgment that such protections are reasonable under the circumstances.&nbsp; Employers should also periodically audit their categories of secret information and update their security procedures.&nbsp; <em>Fail-Safe</em> emphasizes that, although the bar is low for proving that information was the subject of reasonable efforts by the plaintiff to maintain its secrecy, that bar does exist.&nbsp; Companies that lose sight of that burden may forfeit protections for their sensitive data.</p>]]></description>
         <link>http://www.unfaircompetitiontradesecretscounsel.com/federal-law/seventh-circuit-case-highlights-importance-of-documenting-steps-to-maintain-privacy-of-trade-secrets/</link>
         <guid isPermaLink="false">http://www.unfaircompetitiontradesecretscounsel.com/federal-law/seventh-circuit-case-highlights-importance-of-documenting-steps-to-maintain-privacy-of-trade-secrets/</guid>
         <category domain="http://www.unfaircompetitiontradesecretscounsel.com/">Federal Law</category>
         <pubDate>Tue, 10 Apr 2012 09:40:59 -0800</pubDate>
         <dc:creator>Unfair Competition &amp; Trade Secrets Counsel</dc:creator>







      </item>
      
      <item>
         <title>Employee Handbook Provision Not Enough for Enforceable Confidentiality Agreement</title>
         <description><![CDATA[<p><em>By&nbsp;<a href="http://www.littler.com/people/i-michael-kessel">I. Michael Kessel</a></em></p>
<p>A New Jersey district court recently held that an employee handbook provision could not be enforced as a valid confidentiality agreement between a company and a former employee.&nbsp; <a href="http://www.unfaircompetitiontradesecretscounsel.com/Metropolitan%20Food%20v%20Kelsch%20-%20Doc%2036%20-%20Opinion.pdf">Metropolitan Foods, Inc. d/b/a Driscoll Foods v. Kelsch</a> [pdf] involved a former employee of Driscoll Foods (Kelsch), who was accused of soliciting orders for his new employer while still working for Driscoll.&nbsp; Driscoll sued Kelsch under a number of causes of action, including breach of contract.&nbsp; This claim was based upon a provision in the Driscoll employee handbook which stated that employees may &ldquo;not disclose to unauthorized persons, including subsequent employers, Driscoll Foods&rsquo; confidential information.&rdquo;</p>
<p>Usually, it is a plaintiff-employee replying upon an employee handbook as a basis for suing an employer for breach of contract, <em>e.g.</em>, the employer did not follow proper procedures in the handbook when discharging the employee.&nbsp; <em>Woolley v. Hoffman-LaRoche, Inc.</em>, 99 N.J. 284 (1985).&nbsp; In this case, the employer tried to use the provisions of the handbook as a basis to sue the employee.</p>
<p>However, as with most handbooks that were drafted with the advice of counsel, the Driscoll handbook was &ldquo;rife with&rdquo; disclaimers and statements that the handbook was &ldquo;not a contract.&rdquo;&nbsp; Therefore, while Driscoll had other valid causes of action to sue Kelsch, namely, breach of the duty of loyalty, the court held that the handbook provision concerning confidentiality could not be enforced as a valid contractual provision.</p><p>Employers with concerns about employee access to their confidential information can avoid this result by having employees sign a short confidentiality agreement apart from the employee handbook.&nbsp; Such an agreement puts the employee on notice that he or she will be using confidential information in the course of his or her employment, and that the company expects the employee to protect such information.&nbsp; Employers should consider including the following&nbsp;in confidentiality agreements:</p>
<ul>
<li>a definition of confidential information;</li>
<li>a commitment by the employee to keep such information in absolute confidence; </li>
<li>a provision stating that the agreement survives the termination of employment (unless the information becomes part of the public domain); </li>
<li>a provision providing that the company shall be entitled to all remedies, including injunctive relief, for breach of the agreement;&nbsp; </li>
<li>a provision providing that the employee shall return all confidential information upon termination of employment; and </li>
<li>a provision stating that the agreement does not change the employee&rsquo;s at-will status.</li>
</ul>]]></description>
         <link>http://www.unfaircompetitiontradesecretscounsel.com/confidentiality-agreements/employee-handbook-provision-not-enough-for-enforceable-confidentiality-agreement/</link>
         <guid isPermaLink="false">http://www.unfaircompetitiontradesecretscounsel.com/confidentiality-agreements/employee-handbook-provision-not-enough-for-enforceable-confidentiality-agreement/</guid>
         <category domain="http://www.unfaircompetitiontradesecretscounsel.com/">Confidentiality Agreements</category>
         <pubDate>Fri, 30 Mar 2012 09:54:02 -0800</pubDate>
         <dc:creator>Unfair Competition &amp; Trade Secrets Counsel</dc:creator>




      </item>
      
      <item>
         <title>District Court Shows Way to Obtain Non-Solicitation Injunction in California</title>
         <description><![CDATA[<p><em><img class="mt-image-left" style="float: left; margin: 0 20px 20px 0;" src="http://www.unfaircompetitiontradesecretscounsel.com/businesspeople.jpg" alt="businesspeople.jpg" width="452" height="265" />By <a href="http://www.littler.com/people/stephen-c-tedesco">Stephen C. Tedesco</a></em></p>
<p>Companies seeking to prohibit unlawful solicitation of customers should be encouraged by a recent federal court decision.&nbsp; In the U.S. District Court for the Eastern District of California, Magistrate Judge Hollows issued an injunction that prohibited the defendant from directly or indirectly initiating any contact with any current Northern California or Hawaii customer of the plaintiff with whom he had contact or for whose accounts he had responsibility while employed by the plaintiff, for the purpose of encouraging, inviting, suggesting or requesting transfer of their business from plaintiff.&nbsp; The <a href="http://www.unfaircompetitiontradesecretscounsel.com/pyro.pdf">Pyro Spectaculars North, Inc. v. Steven Souza</a> [pdf] court distinguished its case from the decision in <em><a href="http://www.littler.com/publication-press/publication/retirement-group-inc-v-galante-lesson-avoidable-consequences">Retirement Group v. Galante 176 Cal. App. 4th 226 (2009)</a></em>, finding that California Business and Professions Code section 16600 does not constrain a court in equity from fashioning an appropriate remedy for tortious conduct in violation of the California Uniform Trade Secret Act.&nbsp; The case provides a clear rebuke to the now common argument that <em>Galante</em> prohibits non-solicitation restraints.</p>
<p>The defendant in<em> Pyro Spectaculars North, Inc. </em>downloaded and retained detailed information on the plaintiff's customers. The court found that the information downloaded provided "a virtual encyclopedia of specific PSI customer, operator and vendor information at a competitor&rsquo;s fingertips, allowing the competitor to solicit both more selectively and more effectively without having to expend effort to compile the data." &nbsp;The evidence also showed that the defendant solicited numerous customers of the plaintiff using the stolen information.&nbsp; The court also found that the conduct explicitly targeted the plaintiff&rsquo;s customer goodwill and therefore supported the existence of irreparable harm for preliminary injunction.</p>
<p>The court declined to adopt a narrow reading of <em>Galante</em> that would effectively bar any non-solicitation restrictions under Business and Professions Code section 16600. The court noted that the paramount issue is how a court might fashion an appropriate relief via injunction.&nbsp; While a court should be cognizant of the policies embodied in section 16600, that section does not constrain a court in equity from fashioning an appropriate remedy to prevent the misappropriation of trade secrets. &nbsp;The court concluded "that a narrow, time-limited non-solicitation restriction is necessary to prevent defendant's misuse of PSI trade secret information in competing with PSI.&rdquo;</p>
<p>For those practitioners attempting to prevent someone who stole trade secrets from soliciting customers, this case provides clear guidance of the evidence needed to support a non-solicitation injunction and how to fashion such an injunction. The case provides a much needed counterpoint and balanced view as to the scope of remedies available to a court to prevent the misappropriation of trade secrets.</p>]]></description>
         <link>http://www.unfaircompetitiontradesecretscounsel.com/non-solicitation/district-court-shows-way-to-obtain-non-solicitation-injunction-in-california/</link>
         <guid isPermaLink="false">http://www.unfaircompetitiontradesecretscounsel.com/non-solicitation/district-court-shows-way-to-obtain-non-solicitation-injunction-in-california/</guid>
         <category domain="http://www.unfaircompetitiontradesecretscounsel.com/">Non-Solicitation</category>
         <pubDate>Tue, 27 Mar 2012 09:33:31 -0800</pubDate>
         <dc:creator>Unfair Competition &amp; Trade Secrets Counsel</dc:creator>

      </item>
      
      <item>
         <title>Computer Forensics Fill in Wrinkles in Botox Trade Secrets Dispute</title>
         <description><![CDATA[<p><em><img class="mt-image-left" style="float: left; margin: 0 20px 20px 0;" src="http://www.unfaircompetitiontradesecretscounsel.com/botox.jpg" alt="botox.jpg" width="424" height="283" />By <a href="http://www.littler.com/people/dylan-w-wiseman">Dylan W. Wiseman</a> and <a href="http://www.littler.com/people/todd-m-ratshin">Todd M. Ratshin</a></em></p>
<p>In the ongoing battle between competitors in the aesthetics field, the court in <em>Allergan, Inc. v. Merz Pharmaceuticals, LLC, et al</em>. recently completed a nine-day bench trial resulting in <a href="http://www.unfaircompetitiontradesecretscounsel.com/Allergan_v._Merz_Injunction_Order%5B1%5D.pdf">an injunction</a> [pdf] against the defendants to prevent the actual or threatened misappropriation of Plaintiff Allergan, Inc.&rsquo;s (Allergan) trade secrets.</p>
<p>Allergan produces several different prescription medicines, including Botox Cosmetics and Juvederm, which are injectable treatments used to correct facial wrinkles and folds.&nbsp;&nbsp; Merz Aesthetics also had for years been in the facial aesthetics market, and had a product that competed with Allergan&rsquo;s Juvederm product.</p>
<p>In July of 2010, Merz Aesthetics announced that it received FDA approval for a new product to compete with Allergan&rsquo;s Botox Cosmetic product.&nbsp; A related company, Merz Pharma, announced that it too would begin selling a product to compete with Cosmetic Botox by the end of the year.</p><p>In the summer of 2010, four of Allergan&rsquo;s employees, who sold Botox Cosmetic, left and were hired by Merz Aesthetics.&nbsp; &nbsp;Shortly thereafter, three more regional sales representatives left Allergan and were hired by Merz Pharma as territory business managers.&nbsp; All of Allergan&rsquo;s former employees had signed confidentiality agreements, executed Allergan&rsquo;s employee handbook, and agreed to the terms of Allergan&rsquo;s Code of Business Ethics.&nbsp;&nbsp; Allergan&rsquo;s employment agreement identified as confidential numerous categories of information including, &ldquo;information relating to investigational or market products . . . business studies . . . marketing and sales programs and data . . . design and engineering specs [and] product development plans.&rdquo;</p>
<p>When the departing employees arrived at the two Merz entities, they too signed written agreements committing they would not &ldquo;improperly use, disclose, or induce [the Merz entities] to use any proprietary information or trade secrets of any former employer,&rdquo; and they also agreed not to bring to Merz or transfer to its computer systems any confidential data from any prior employer.&nbsp; The same obligations were found in Merz Pharma&rsquo;s and Merz Aesthetics&rsquo; employment offers to the former Allergan employees.</p>
<p>After sending a cease and desist letter, Allergan filed a lawsuit in the Orange County Superior Court and sought a temporary restraining order.&nbsp; At the TRO hearing, counsel for the Merz defendants expressly disavowed having or wanting Allergan&rsquo;s trade secret information. &nbsp;&nbsp;At the hearing counsel for the Merz defendants proclaimed Merz &ldquo;[has] never seen it, [Doesn&rsquo;t] know what it is. [Doesn&rsquo;t] want it, and [hasn&rsquo;t] done anything.&rdquo;&nbsp; The court denied the TRO, and Allergan proceeded with further investigation and discovery, and the action was apparently removed to the federal court.</p>
<p>Allergan&rsquo;s discovery and investigation revealed that, contrary to the statements made at the TRO hearing, Merz Pharma and Merz Aesthetics had in fact been in possession of Allergan&rsquo;s confidential information <em>months</em> before the TRO hearing.&nbsp; Indeed, the court&rsquo;s <a href="http://www.unfaircompetitiontradesecretscounsel.com/Allergan_v._Merz_Findings_of_Fact_and_Conclusions_of_Law%5B1%5D.pdf">factual findings </a>[pdf] chronicle the extensive use and transmission of Allergan&rsquo;s data via email within both Merz Pharma and Merz Aesthetics.</p>
<p>To its credit, Merz Pharma sought to educate its employees about compliance with their confidentiality obligations.&nbsp; Merz also engaged in a program to identify those involved in the hiring of the former Allergan employees to determine whether they had received any of Allergan&rsquo;s information.&nbsp; Merz Pharma&rsquo;s in-house counsel also gave a presentation to the entire sales force reminding them not to solicit or use any competitors&rsquo; confidential business information.&nbsp;</p>
<p>The Merz defendants also hired a private computer forensics firm.&nbsp; However, the Merz defendants&rsquo; own computer forensic review was arguably superficial. &nbsp;The search terms were developed by the Merz defendants without consultation or input from their computer forensic expert.&nbsp; Further, the search terms oddly did not include the term &ldquo;Allergan.&rdquo;&nbsp; The Merz defendants also did not search the computers belonging to the four former Allergan employees who had joined Merz Aesthetics.&nbsp; &nbsp;The Merz defendants also did not include any portable storage media from the 50 custodians they had identified as potentially having Allergan&rsquo;s information.&nbsp; Likewise, the results of the Merz defendants&rsquo; computer forensics, which produced &ldquo;thousands&rdquo; of hits, were not analyzed by its own consultant, but rather were turned over to the Merz defendants and their outside counsel.&nbsp; The court concluded that &ldquo;the Merz Defendants&rsquo; searches for Allergan&rsquo;s trade secrets and confidential information were inadequate.&rdquo;&nbsp;</p>
<p>Allergan&rsquo;s initial computer forensic discovery revealed that while working at Allergan several of its former sales employees who joined Merz sent &ldquo;numerous documents and electronic files&rdquo; to their personal email addresses.&nbsp; Those files included &ldquo;the entire nationwide list of nearly 24,000 physician customers, contact information, and details concerning sales volumes and future targets . . .&rdquo; and other lists, new product information, and sales presentations.&nbsp; Allergan&rsquo;s further computer forensic review established similar facts and showed that certain employees had transferred files to portable electronic storage media.&nbsp; Indeed, one of the departing employees backed-up over 700 Allergan files to a 2 terabyte hard drive.&nbsp; That same former Allergan employee returned a 320 gigabyte drive to Allergan during her exit interview and made no mention of the 2 terabyte drive.&nbsp; The computer forensics also established that other former Allergan employees had copied and transferred to external devices numerous files and spreadsheets about &ldquo;top doctors&rdquo; and &ldquo;target physicians.&rdquo;</p>
<p>Nearly a year after the TRO hearing, and just hours before the parties&rsquo; pretrial conference, counsel for Merz Pharma and Merz Aesthetics hand-delivered a box containing a hard drive, a CD containing electronic documents, and various hard copy records.&nbsp; Among the materials &ldquo;returned&rdquo; to Allergan were email messages containing Allergan&rsquo;s files as attachments, information about Allergan&rsquo;s customer loyalty program, a confidential PowerPoint presentation, and other confidential information belonging to Allergan.&nbsp; The Merz defendants then also sent two subsequent packages claiming they had &ldquo;returned&rdquo; Allergan&rsquo;s confidential information.</p>
<p>Contrary to the Merz defendants&rsquo; assertions, the court made the express findings that &ldquo;[t]here is overwhelming circumstantial and direct evidence that Defendants . . . improperly acquired, disclosed, or used [Allergan&rsquo;s trade secrets] and that Allergan faces a substantial threat of impending injury as a result of this misappropriation.&rdquo;&nbsp; The court also concluded that &ldquo;numerous witnesses affiliated with the Defendants were not credible.&rdquo;</p>
<p>The court also took note that &ldquo;[n]either Merz Aesthetics nor Merz Pharma has terminated or reassigned&rdquo; any of the former Allergan employees even after they were &ldquo;found to be in possession of Allergan information.&rdquo;</p>
<p>The court also made several important legal conclusions.&nbsp; First, the court found that the information which had been taken by the former Allergan employees was a &ldquo;trade secret&rdquo; under California&rsquo;s Uniform Trade Secrets Act (CUTSA).&nbsp; In doing so, the court found that Allergan had taken reasonable measures under the circumstances to maintain the secrecy of the information, which &ldquo;need not be overly extravagant, and absolute secrecy is not required . . . .&rdquo;&nbsp;</p>
<p>Next, the court concluded that the Merz defendants had engaged in a &ldquo;misappropriation&rdquo; under the CUTSA.&nbsp; The theft of the data and copying it to external media was also a breach of the former Allergan employees&rsquo; confidentiality obligations, and amounted to an &ldquo;acquisition by improper means.&rdquo;&nbsp;&nbsp;</p>
<p>Third, the court concluded that the Merz entities were &ldquo;liable for the acts of misappropriation committed by their employees and former employees&rdquo; because the CUTSA imposes liability where an employer knew or should have known of an employee&rsquo;s wrongdoing.&nbsp;&nbsp; In making that finding, the court discounted the Merz defendants&rsquo; argument that the former Allergan employees had &ldquo;secretly taken&rdquo; the information unbeknownst to the Merz defendants because &ldquo;an act of this nature was generally foreseeable as part of [his] duties to solicit customers for Defendant.&rdquo;</p>
<p>In issuing an injunction, the court also made several important factual findings.&nbsp;&nbsp; For the element of irreparable injury, the court determined it was appropriate to &ldquo;presume that Plaintiff will suffer irreparable harm if its proprietary information is misappropriated.&rdquo;&nbsp; The court further concluded that &ldquo;the risk of losing established customers to defendants&rsquo; new business due to the defendants&rsquo; improper use of plaintiff&rsquo;s proprietary information would obviously create lasting, irreparable harm.&rdquo;&nbsp;</p>
<p>The court also concluded that Allergan&rsquo;s monetary damages were insufficient resulting from the misappropriation &ldquo;where the threat of injury is imminent and the measure of that injury defies calculation, damages will not provide a remedy at law.&rdquo;&nbsp;&nbsp; Most importantly, in response to the Merz Defendants&rsquo; stated position that &ldquo;they have returned, and no longer possess, any of Allergan&rsquo;s trade secrets, the court concluded &ldquo;[i]t is the duty of the courts to beware of efforts to defeat injunctive relief by protestations of repentance and reform, especially when abandonment seems timed to anticipate suit, and there is a probability of resumption.&rdquo;</p>
<p>The practical lessons learned from <em>Allergan </em>are significant.&nbsp; First, when hiring sales personnel from a direct competitor, employers should be expected to make thorough, meaningful, and diligent efforts to ensure that their new hires have not taken any of their employer&rsquo;s electronic or hard copy records.&nbsp; Second, in this electronic era, conducting a superficial computer forensic review is completely inadequate, particularly in the face of evidence of actual wrongdoing.&nbsp;&nbsp; Third, any efforts to &ldquo;return&rdquo; electronic and hard copy records may likely have little impact on the issuance of injunctive relief.&nbsp; &nbsp;The fact that new hires may have &ldquo;secretly&rdquo; or without the approval of the employer taken files may be of little consequence, particularly where it was foreseeable by their job duties to solicit customers. &nbsp;Lastly, when confronting obvious wrongdoing, the failure to discipline or re-assign employees who have engaged in a misappropriation can certainly be problematic.</p>]]></description>
         <link>http://www.unfaircompetitiontradesecretscounsel.com/trade-secrets-1/computer-forensics-fill-in-wrinkles-in-botox-trade-secrets-dispute/</link>
         <guid isPermaLink="false">http://www.unfaircompetitiontradesecretscounsel.com/trade-secrets-1/computer-forensics-fill-in-wrinkles-in-botox-trade-secrets-dispute/</guid>
         <category domain="http://www.unfaircompetitiontradesecretscounsel.com/">Trade Secrets</category>
         <pubDate>Thu, 22 Mar 2012 09:39:15 -0800</pubDate>
         <dc:creator>Unfair Competition &amp; Trade Secrets Counsel</dc:creator>










      </item>
      
      <item>
         <title>Minnesota Court Narrowly Interprets the Computer Fraud and Abuse Act</title>
         <description><![CDATA[<p><em>By </em><a href="http://www.littler.com/people/kerry-l-middleton"><em>Kerry L. Middleton</em></a><em></em></p>
<p>Recently, a Minnesota federal district court construed the federal Computer Fraud and Abuse Act narrowly and dismissed an employer&rsquo;s CFAA claim against three former high-level employees.&nbsp;&nbsp; In <a href="http://www.unfaircompetitiontradesecretscounsel.com/Walsh%20Bishop.pdf">Walsh Bishop Associates, Inc. v. O&rsquo;Brien, et al.</a> [pdf], the court held that civil liability under the CFAA does not extend to an employee&rsquo;s alleged later misuse of information that the employee was authorized to access.&nbsp; Thus, the court concluded that civil liability under the statute turns on whether the former employees were authorized to access the data at issue, not on whether the former employees allegedly misused the data after accessing it.&nbsp;</p>
<p>The <a href="http://www.law.cornell.edu/uscode/text/18/1030">CFAA</a> makes it unlawful for any person to obtain information from a computer by intentionally accessing the computer without authorization or by exceeding authorized access.&nbsp;&nbsp;Employers frequently include a CFAA claim in suits against former employees for trade secret misappropriation.&nbsp; &nbsp;&nbsp;</p>
<p>In <em>Walsh Bishop</em>, the defendants were former executive-level employees.&nbsp; Among other things, the employer alleged that the defendants accessed documents the employer claimed were confidential and took those documents with them after leaving the employer&rsquo;s employ.&nbsp;&nbsp;&nbsp;&nbsp;</p><p>In reaching its decision regarding the scope of civil liability under the CFAA, the <em>Walsh Bishop</em> court recognized a split of authority among federal courts on the issue of whether the statute&rsquo;s &ldquo;exceeds authorized access&rdquo; requirement was intended to include the alleged misuse of information properly accessed.&nbsp; In rejecting the employer&rsquo;s argument for a broad reading of this requirement, the court referenced the CFAA&rsquo;s legislative history and emphasized that Congress amended the statute in 1986 to remove &ldquo;use&rdquo; as a basis for exceeding authorization.&nbsp; The court relied on the plain language of the statute and focused on whether the defendants accessed information that they were forbidden to access.&nbsp;</p>
<p>In its complaint, the employer alleged that the defendants had the &ldquo;highest level&rdquo; of access to the employer&rsquo;s confidential and proprietary information.&nbsp; The court concluded, therefore, that the employer had authorized the defendants to access &nbsp;the data at issue and dismissed the CFAA claim, reasoning that the statute does not impose liability on individuals who have permission to access information, but later allegedly use it for an improper purpose.</p>
<p>Minnesota&rsquo;s federal courts likely will continue to address the scope of civil liability under the CFAA and the issue of prohibited access versus use, given the relatively small number of CFAA cases that exist in that district.&nbsp; The recent Minnesota case adopts the narrower reading of the CFAA&rsquo;s &ldquo;exceeds authorized access&rdquo; requirement (following other, similar decisions from that district and other districts) and tightens the requirements needed before an employer can prevail against former employees under the CFAA.&nbsp; In most trade secret cases, a former employee is accused of taking and using confidential information that was accessible to him or her in the course of employment.&nbsp; The typical trade secret case does not involve employees gaining unauthorized access to confidential electronic data.&nbsp;&nbsp; If Minnesota&rsquo;s courts continue to read the CFAA narrowly, as the court did in <em>Walsh Bishop</em>, civil liability under the CFAA will not usually be a claim that employers may rely upon as part of their arsenal of claims against departing employees.&nbsp;</p>]]></description>
         <link>http://www.unfaircompetitiontradesecretscounsel.com/federal-law/minnesota-court-narrowly-interprets-the-computer-fraud-and-abuse-act/</link>
         <guid isPermaLink="false">http://www.unfaircompetitiontradesecretscounsel.com/federal-law/minnesota-court-narrowly-interprets-the-computer-fraud-and-abuse-act/</guid>
         <category domain="http://www.unfaircompetitiontradesecretscounsel.com/">Federal Law</category>
         <pubDate>Tue, 20 Mar 2012 08:54:03 -0800</pubDate>
         <dc:creator>Unfair Competition &amp; Trade Secrets Counsel</dc:creator>




      </item>
      
   </channel>
</rss>

