Video Blog: Start-Up Trade Secrets

TRANSCRIPT & LINKS:

Welcome to Protecting Trade Secrets. I’m Eric Ostroff. I’m a partner at Meland Russin & Budwick and I’m coming to you from my office in Miami Florida. I’m doing something new here on the Protecting Trade Secrets blog. Obviously, I’m on video right now, and I’ll be using video to create blog posts for at least some of the blog posts in the future. I’ll also go ahead and post a transcript of the video down below.

Today I want to talk about issues facing start-up companies who are looking to protect their proprietary information and trade secrets. I recently read an article on inc.com and I’ll go ahead and post a link to the article in the transcript below.

This article told the story of a company called HIDEit Mounts. They had a product that mounted video game consoles and camouflaged them so you didn’t have wires and things sticking out all over your living room.

When this company started out, it was a husband-and-wife team. They didn’t have any experience with product development, product design, or manufacturing, so they did with a lot of startup companies do; they partnered with a manufacturing company and worked with that company to design a prototype and then manufacture these products.

Things were going great. They were selling a lot of products; there were no direct competitors, and the company seemed like it was going to be successful. But then they hit a problem. Another company all of a sudden started selling very similar products, except they were actually a little bit better. And the HIDEit company thought that they might have to go out of business.

They did some research and were able to figure out that it was actually their manufacturer who was behind this competing company. Now thankfully for HIDEit, they went ahead and had their manufacturers sign a nondisclosure agreement early in the relationship. And they were able to use that contract to protect their IP rights and to protect their business. But a lot of startup companies just either ignore, try and use self-help, or don’t give enough thought to potential ways that having a lawyer or using legal solutions can protect against major problems down the road. A lot of companies will use forms off the internet or just won’t use lawyers at all.

The reality is that an extremely modest investment on the front end for a startup company in a competent lawyer who can can create agreements and give advice about ways that this company can protect its proprietary information can go a tremendous way to mitigate against and to deter really serious issues in the future.

So the lesson from this inc.com article for start-up companies is: Don’t think that you’re too early or you don’t have enough money to hire a lawyer. Speak with a lawyer early on in the process. Doing that can solve a lot of really terrible problems in the future.

That’s all for today. I appreciate your time.

 

Can Filing for Bankruptcy Invalidate a Noncompete?

Guest post by Solomon B. Genet.

Debtors and their lawyers sometimes use a bankruptcy filing as an offensive tool. In a recent case, a debtor tried to use his prior bankruptcy to shed his non-compete obligations. While this attempt was not successful, non-compete practitioners should be aware of this effort.

In In re Capps, a July 26, 2018 decision from the District of Kansas Bankruptcy Court, the individual debtor sold his company and signed an employment agreement with the buyer, agreeing to a series of non-compete, non-solicit and confidentiality obligations. The debtor later filed for bankruptcy, and the buyer fired him soon thereafter.  The buyer then discovered that the debtor was breaching his restrictive covenants and brought an action for declaratory relief in the bankruptcy court seeking a finding that the bankruptcy process and discharge did not relieve him of these obligations.

Bankruptcy Judge Nugent agreed with the plaintiff-buyer and rejected the debtor’s arguments, reasoning that: (1) the debtor’s breaches of the restrictive covenants occurred post-bankruptcy, and gave rise to “equitable” (i.e., injunctive) relief and not “a right to payment,” so the debtor did not discharge any debts arising from the agreements; and (2) the restrictive covenants were not “executory” contracts (material obligations on both sides), and therefore could not be rejected through the bankruptcy process.

The Capps debtor was unsuccessful in shedding his obligations.  But—hypothetically—a strategic legal counselor could use the Capps debtor’s arguments in a case with more favorable facts (and perhaps different applicable law) to assist a person subject to a non-compete to obtain relief long before his contracted time-period for his non-compete obligations expired.

A copy of the opinion can be downloaded here.

Federal Circuit Invalidates Financial Analysis Patent, Suggests Trade Secret Protection

Since the Supreme Court decided Alice Corp. v. CLS Bank International in 2014, companies have had a difficult time patenting software and business methods. I am not a patent lawyer and this is not a patent blog. But a recent Federal Circuit case shows how companies with this type of IP may want to look to trade-secret laws for protection.

Last week, the Federal Circuit decided SAP America, Inc. v. InvestPic, LLC (a pdf of the opinion can be downloaded here). In this case, a judge in the Northern District of Texas granted judgment on the pleadings in favor of SAP, which filed a declaratory-judgment action seeking to invalidate InvestPic’s patent. The Federal Circuit affirmed.

InvestPic’s patent involved a technique that “utilizes resampled statistical methods for the analysis of financial data[.]” InvestPic claims this is superior to typical financial-market forecast methods that rely on the flawed assumption that “financial data follows a normal or Gaussian distribution.” (This reminds me of The Black Swan’s chapter on “The Bell Curve, That Great Intellectual Fraud.”)

Citing Alice, the Federal Circuit invalidated InvestPic’s patent, finding that it was directed to an abstract idea and did not contain an innovative concept.  This is not an uncommon post-Alice result. But at the end of its opinion, the Federal Circuit made a comment that caught my attention:

There is, in short, nothing “inventive” about any claim details, individually or in combination, that are not themselves in the realm of abstract ideas. . . . [P]atent law does not protect such claims, without more, no matter how groundbreaking the advance. An innovator who makes such an advance lacks patent protection for the advance itself. If any such protection is to be found, the innovator must look outside patent law in search of it, such as in the law of trade secrets, whose core requirement is that the idea be kept secret from the public.

Given the current state of patent law, many companies face a dilemma when trying to monetize potentially abstract ideas: make the disclosures necessary to seek a patent and risk having the patent rejected or invalidated, or adopt a business model that allows for trade-secret protection. This is a complicated analysis that involves many business and legal factors.

As the Federal Circuit noted, trade secrets cannot be publicly disclosed, and they must be reasonably protected. Business models can incorporate these restrictions. For example, it may be possible for a company to license its technology and include confidentiality obligations in the licensing agreement. Companies facing this choice need to involve trade-secret lawyers in strategy discussions and decisions.

Federal Court Addresses Defend Trade Secret Act Immunity

The Defend Trade Secrets Act, 18 U.S.C. 1030, et seq., provides immunity from liability for misappropriation of trade secrets in certain circumstances, namely if the disclosure:

(A) is made–

(i) in confidence to a Federal, State, or local government official, either directly or indirectly, or to an attorney; and

(ii) solely for the purpose of reporting or investigating a suspected violation of law; or

(B)  is made in a complaint or other document filed in a lawsuit or other proceeding, if such filing is made under seal.

Since the DTSA was enacted in May 2016, there have not been many cases analyzing this portion of the statute. The Eastern District of Pennsylvania examined it in a recent opinion, Christian v. Lannett Co., Inc., E.D. Pa. Case No. 16-963 (the opinion can be downloaded below).

Christian is an unusual trade-secret case, as it started when the plaintiff asserted claims for employment discrimination. During discovery, the defendant learned that the plaintiff had retained a company laptop, which led to the plaintiff producing 22,000 pages of documents. Per the defendant, these contained trade secrets.

The defendant then filed a counterclaim under the DTSA, as well as other related claims, based on the plaintiff’s disclosure of trade secrets. But there was apparently no evidence of disclosure to anyone except the plaintiff’s lawyer, who only received the documents to produce them in the litigation.

The court concluded that “Plaintiff’s alleged disclosure was made to Plaintiff’s counsel pursuant to a discovery Order of this Court, within the context of a lawsuit regarding violations of Title VII, the ADA, and the FMLA,” and applied the immunity provision above to bar the DTSA claim.

The court did not specifically cite the immunity provision. And a strict application of that provision would seem to exclude the plaintiff from its protection, since the disclosure was not “solely for the purpose of reporting or investigating a suspected violation of law.” But the court’s decision is well within the spirit of the DTSA, which should not be used to prevent parties in litigation from communicating freely with, and providing discoverable documents to, their counsel.

Christian v Lannett

 

AIPLA Trade Secrets Summit in San Diego, March 1-2

The American Intellectual Property Law Association’s annual Trade Secrets Summit is next week in San Diego. This event, which I have attended for the past three years, is a great opportunity to learn from and network with trade secret practitioners, while racking up CLE credits.

I will be moderating a panel on Corporate Best Practices, and there are a number of great presentations scheduled. You can find out more information here.

Hope to see you there!

Blockchain & Trade Secrets: Miami Conference 1/18-19

Tomorrow and Friday, I will be attending the North American Bitcoin Conference, which will take place two blocks from my office in downtown Miami. A number of startup and more established companies in the blockchain space will be presenting. I’ll be live tweeting the conference from @BlogTradeSecret, with a focus on trade-secrets and related legal issues facing companies in this developing field.

Will Two Lawyers Go to Jail for Asserting Trade Secrets in Bad Faith?

Two South Florida lawyers are facing possible jail time, in part because of allegedly asserting in bad faith that documents contained trade secrets. They supposedly wanted to prevent disclosure of documents that proved their witness testified inaccurately. In a case pending in Miami-Dade County Circuit Court, Green Tree Servicing v. Sibon, the judge decided yesterday to go forward with an arraignment for the two lawyers representing the plaintiff, a large loan servicer, on charges of indirect criminal contempt.

This started as a mortgage foreclosure case. The defendants asserted defenses relating to the plaintiff’s “loan boarding” process, i.e., how the plaintiff uploads information from prior servicers’ records, including borrowers’ payment history.

During a deposition, the plaintiff’s representative testified that the company’s training manuals included protocols for verifying this information, including a flow chart showing the process. But the plaintiff had not previously produced those manuals. Not surprisingly, the defendants’ lawyers demanded their production.

The court entered an order requiring production of the manuals and a further deposition of the plaintiff. Three days before the deposition, the plaintiff filed an emergency motion, asserting that the manuals contained trade secrets and work product. The next day, the court entered an order ruling that the motion was not an emergency and directed the plaintiff to set the motion for a hearing (the usual protocol in Miami-Dade Circuit Court for having a judge rule on a motion).

The deposition went forward without production of the manuals. But the plaintiff never set its emergency motion for hearing. Several months later, the court entered an order requiring production of the manuals by noon that day. At 11:59, the plaintiff produced them.

Apparently, the manuals contradict the witness’s testimony. According to the judge, “the document does not contain any ‘flow chart’ that mentions ‘red flags’ that prevent loans from boarding as Mr. Ogden testified he reviewed. To the contrary, it appears from the document produced that [the plaintiff] boards the prior servicer’s records . . . and makes the loan live on its system before any verification process would even begin.”

And then it got interesting. The judge entered an order to show cause, which can be downloaded here. That order informs both the witness and the plaintiff’s attorneys that “this is now a criminal matter” and directs them to appear to show cause why they should not be held in indirect criminal contempt:

It appears that [the plaintiff] and its counsel willfully and contumaciously ignored this Court’s order by refusing to turn over the training materials. Moreover, it appears [the plaintiff] and its counsel improperly sought to have the records deemed confidential to avoid disclosure of the fact that its witness gave grossly inaccurate testimony[.]

According to an article in the Daily Business Review, yesterday, the new judge handling the case (the prior judge recused himself) “ruled that [the witness] was ‘operating at the will of the lawyers’ and dismissed him from the criminal contempt proceedings.” But she will be going forward with the criminal case against the lawyers, pending an appeal.

If true, this is an egregious abuse of the trade-secrets laws. It’s one thing to be over broad when asserting trade-secret protection. It’s another thing entirely to assert trade secrets when none exist, solely to hide a witness’s inaccurate testimony. It will be interesting to see whether these lawyers are sanctioned, and if so, how harshly.

Florida Supreme Court Issues Landmark Noncompete Opinion

It’s been a difficult week in Florida, as the state recovers from Hurricane Irma. But the storm did not deter the Florida Supreme Court from issuing what could be one of the most important opinions in the state’s history regarding Section 542.335, Florida Statutes, the statute governing restrictive covenants. I’m still dealing with hurricane-related issues as my office in Miami prepares to re-open tomorrow, which prevents me from relaying an in-depth analysis. But I wanted to pass along some key takeaways. A more comprehensive analysis will follow in the coming weeks.

This opinion, White v. Mederi Caretenders Visitng Services of Southeast Florida, LLC, resolves a District split on the issue of whether referral sources can constitute a legitimate business interest, a prerequisite under the statute. Referral sources are not included in the statute’s list of protectable business interests, but the statute prefaces that list with the words “includes, but is not limited to.”

I previously wrote about the divergent holdings on this issue. I argued that the Florida Supreme Court should give life to the statute’s “includes, but is not limited to” provision by ruling that referral sources can be a legitimate business interest. The opinion ended up mirroring my analysis, holding that “the subject statute protects a plethora of protected legitimate interests far beyond those listed in the subject statute.” Here are a few key points:

  • This opinion has far-reaching implications beyond cases involving referral sources. It makes clear that courts should engage in industry-specific, context-based analysis to determine whether the plaintiff has a legitimate business interest, regardless of whether that interest is listed in the statute:

The illustrative list guides courts in their interpretation of what types of non-enumerated business interests qualify as legitimate under Section 542.335. However, because the statue protects more business interests than those specifically listed, courts must necessarily engage in fact- and industry-specific determinations when construing non-enumerated interests.

  • The opinion repeatedly references industry-specific determinations. Lawyers attempting to enforce a restrictive covenant should consider what types of industry-specific evidence is necessary to justify the restrictive covenant.
  • The Court also emphasized the purpose of the statute: “preventing unfair competition by protecting critical business interests.” This focus on unfair competition may shift courts’ analysis towards a determination of the unfair advantage provided to the new employer. This was always a consideration on some level, but it may rise in prominence.
  • The opinion also contains language that will likely be cited by defendants: “For an employer to be entitled to protection, there must be special facts present over and above ordinary competition such that, absent a non-competition agreement, the employee will gain an unfair advantage in future competition with the employer.”
  • Lawyers drafting restrictive covenants under Florida law should consider whether it makes sense to include language in which the employee acknowledges the importance of the business interest at issue to the company, particularly when that interest is not enumerated in the statute.

This opinion may embolden companies looking to enforce restrictive covenants. I would not be surprised if this case leads to increased litigation involving alleged business interests outside those listed in the statute. More analysis to come.

A copy of the opinion can be downloaded here.

Bitcoin, Blockchain & Trade Secrets: An Introduction

I’m willing to bet that most readers of this blog have heard of Bitcoin. But I’m not sure how many know about the technology it’s based on, called blockchain. If you haven’t heard of blockchain, now’s the time to learn, since it has the potential to be the most transformative technology since the internet.

I’m going to be writing more about blockchain and the unique trade-secrets issues facing the many companies rushing to develop applications and other technology based on blockchain. But first, I want to give a primer for those who haven’t heard of it.

Blockchain is essentially a database that is distributed among a large number of computers on a network. Each computer with access to the blockchain has an identical copy of the database. Here’s a simple example to explain how it works, from this explanatory post that compares blockchain to a “record book”:

To be clear, this isn’t just one record book stored in a central location that is shared by many. There are thousands of copies of this record book, stored on computers all around the world, both home computers and business servers – hence the term “decentralised”. This record book can be used to record many kinds of things, however I’ll use sending and receiving money as the primary example, as it’s the most common one right now.

When John wants to send money to Sue, a new line item is created detailing that transaction. This line item then gets sent off to hundreds of other computers who have a copy of the record. Those computers confirm that this transaction is authorised, and ultimately they agree (or disagree) that everything about the transaction is legitimate before giving that line item a tick of approval. It has to match up perfectly on every copy of the record.

Each transaction, here John sending money to Sue, is a “block,” which when added to all the prior blocks forms a kind of “chain.” Hence, blockchain.

Since each computer with access to the blockchain has an identical copy of the database, fraudulent transactions are nearly impossible. If any one computer has a blockchain entry that all of the others don’t recognize, that entry is rejected. Entries are only added if all of the computers with access to the database agree.

The first “app” based on blockchain is Bitcoin, a cryptocurrancy. You can watch a short video that explains Bitcoin here. Bitcoin was the first truly digital currency, which allowed the transfer of money without the need for any centralized institution like a bank. Now there are a number of cryptocurrancies with names like Ether and litecoin.

But blockchain’s potential goes far beyond currencies. It can be used to streamline, simplify, and secure a wide variety of transactions, such as supply-chain management, digitial voting, collecting taxes, and recording real estate transfers and ownership. Essentially, any transaction involving value could be conducted—and improved—on the blockchain. Some think that the entire worldwide financial system will eventually move to blockchain — and I agree. Additionally, developers are using a blockchain platform called Etherium (which also underpins the Ether cryptocurrancy) to create “smart contracts” — essentially programming code that is capable of executing or enforcing contractual terms. This is a powerful, but complicated, concept that I will discuss in more detail in a future post.

Companies large and small are racing to develop new “apps” based on blockchain technologies.  This entire industry is essentially in the research-and-development phase, which means that trade-secrets issues abound. These companies can benefit from tech-savvy lawyers who understand how to protect this rapidly developing information.

This post is a very basic introduction to blockchain. I’m fascinated by the technology and see virtually limitless potential. If you want to learn more, I’d recommend The Internet of Money, an excellent book by Andreas M. Antonopoulos. And stay tuned — I intend to explore the intersection of blockchain and trade secrets here at Protecting Trade Secrets.

Florida Companies: Are Your Non-Competes Missing This Critical Provision?

Under Florida’s restrictive-covenant statute, Section 542.335(f), a restrictive covenant is only enforceable by a successor entity or third-party beneficiary if the agreement so provides. This provision can become very important following corporate merger or sale transactions. Or in the due-diligence period leading up to those transactions.

In a recent Florida case, Collier HMA Physician Mgmt, LLC v. Menichello, the plaintiff almost fell victim to this statutory requirement. A copy of the opinion can be downloaded here.

In this case, the plaintiff owns a healthcare business employing approximately 40 doctors. It also operates two hospitals and clinics. The defendant, a physician, previously worked for the plaintiff, where he signed a non-compete agreement prohibiting him from working for certain of the plaintiff’s competitors. After his departure, he accepted a position with one of those competitors, and the plaintiff filed suit.

The physician argued that a merger transaction involving the plaintiff’s corporate parent triggered the statutory provision above. Per the physician, since the agreement did not expressly provide for enforcement by successors, the merger invalidated the non-compete. The trial court agreed and granted summary judgment in the defendant’s favor.

The appellate court reversed. To reach that conclusion, it interpreted the term “successor” in the statute as “a corporation that, through amalgamation, consolidation, or other assumption of interests, is vested with the rights and duties of an earlier corporation.”

The court found that “the status of [the plaintiff] after the merger does not comport with the standard definition of a successor as it relates to corporations or other business entities.” In particular, there were several tiers of corporate entities between the plaintiff and the parent company that was subject to the merger. While the ownership of the ultimate parent company changed, “nothing about the corporate structure or ownership of [the plaintiff] was different after the merger”; it “continued in existence as a single member limited liability company.”

In the end, the plaintiff here was able to enforce its non-compete agreement. But all of this trouble could have been avoided. This leads to a very simple takeaway: when drafting restrictive covenants in Florida, include a provision allowing their enforcement by successors and assigns. Florida companies with existing restrictive-covenants should have a lawyer review them for compliance with this statute.

Similarly, anyone considering acquiring or merging with a company with Florida employees/independent contractors needs to have a lawyer review any restrictive covenants for this purpose.

The failure to include this provision could lead to all sorts of problems. For example, it could impede a later merger or sale of the company. But any Florida company can avoid these problems by having a lawyer conduct a simple review.

 

%d bloggers like this: