Spiteful Motives, Lacking Improper Conduct, do not Support Tortious Interference Claim

In a recent opinion, the Supreme Court of Virginia held that actions motivated solely by ill will or personal spite, that don’t include improper conduct, do not support a claim for tortious interference with an at-will contract. The court provided a helpful definition of when conduct is considered improper and decided that it is not enough if the actions were merely spiteful. Click here for the opinion.

The facts of the case involve a Virginia law firm, Dunn, McCormack & Macpherson (“Dunn”), who had an at-will contract with the Fairfax County Redevelopment and Housing Authority (the “Authority”). Dunn had served as legal counsel for the Authority for around thirty years until the Authority terminated the contract in September 2005.

Dunn sued Gerald Connolly (“Connolly”), Chairman of the Fairfax County Board of Supervisors, alleging that Connolly tortiously interfered with Dunn’s contract with the Authority by persuading Authority to break the contract. Dunn claimed that Connolly’s actions were motived solely by his personal spite, ill will and malice, because he didn’t get along with a partner at Dunn.

The circuit court entered an order dismissing the action for Dunn’s failure to provide facts showing Connolly used illegal means or improper methods when he communicated with the Authority. This court reviewed the circuit court’s ruling de novo and came to the same conclusion.

The elements to support a cause of action for tortious interference with contract rights are: (1) the existence of a valid contractual relationship or business expectancy, (2) knowledge of the relationship or expdctancy on the part of the interferer, (3) intentional interference inducing or causing a breach or termination of the relationship or expectancy, and (4) resultant damage to the party whose relationship or expectancy has been disrupted. Additionally, when a contract is at-will, an element is added: the defendant must have employed improper methods. Op. at 6, citing Duggin v. Adams, 234 Va. 221, 226-27, 360 S.E.2d 832, 836 (1987).

The court explained that interference is improper if it is illegal, independently tortious, or violates an established standard of trade or profession. The court quoted the Duggin case, stating:

Methods of interference considered improper are those means that are illegal or independently tortious, such as violations of statutes, regulations, or recognized common-law rules. Improper methods may include violence, threats or intimidation, bribery, unfounded litigation, fraud, misrepresentation or deceit, defamation, duress, undue influence, misuse of inside or confidential information, or breach of a fiduciary relationship. . . .

Methods also may be improper because they violate and established standard of a trade or profession, or involve unethical conduct. Sharp dealing, overreaching, or unfair competition may also constitute improper methods.

234 Va. at 227-28, 360 S.E.2d at 836-37.

Dunn’s argument that Connolly improperly interfered with its terminable at-will contract with the Authority because his actions were motived solely by Connolly’s personal spite, ill will and malice was found to be insufficient. The court found that Dunn failed to appreciate the limited nature of what constitutes “improper” interference. The court stated that it “will not extend the scope of the tort to include actions solely motivated by spite, ill will and malice.” Op. at 7. Because there were no facts alleged that showed improper interference, there was no merit to Dunn’s claim and the action was dismissed.

District of Columbia Limits Applicability of Computer Fraud and Abuse Act

In a case of first impression, a federal district court in the District of Columbia has joined those courts that restrict the applicability of the federal Computer Fraud and Abuse Act. Previously, we have written about the growing number of cases that have adopted a broad reading of this Act in a way that permits a claim to be made where an employee has accessed an employer's computer and removed proprietary data after deciding to accept a new job. See posts dated March 27, 2009 and September 7, 2010.

The CFAA protects companies from the misappropriation of proprietary information by someone who does not have authorized access to the computer or who has been authorized to access the computer, but who exceeds that authorization. The cases attempt to define the limits of authorized access.

A number of courts following the 7th Circuit's opinion in Int'l Airport Ctrs., LLC v. Citrin, 440 F.3d 418 (7th Cir. 2006) have held that an employee who has been given access to his employer's computer network, loses that right of access as a matter of law when he has decided to accept a new job and downloads proprietary information from the network to use in his new position. Courts adopting this logic posit that such conduct violates the employee's duty of loyalty owed to his employer because, once he has made the decision to leave and has accepted the new position, the employee's interests become adverse to the interests of his current employer. Those courts find that accessing the computer, and copying proprietary information under such circumstances, exceed the authorization that the current employer has provided and violate the CFAA.

Not so in the District of Columbia according to a recent opinion by Magistrate Judge John Facciola in Lewis-Burke Associates, Ltd. v. Widder, 725 F. Supp.2d 187 (D.D.C. 2010), click here. There, the court relied upon the analysis of the 9th Circuit in LVRC Holdings LLC v. Brekka, 581 F.3d 1127 (9th Cir. 2009), which held that, once an employer has authorized an employee to access the company computer, even if for limited purposes, that access is still authorized even if the employee violates those limitations. Id. at 1133. According to Brekka, whether an employee has authorization to access a computer is dependent upon whether the employer has terminated that authorization.

In the District of Columbia case, before he left his job, Widder copied proprietary and confidential electronic files onto a thumb drive that he took with him to his new employer. Some of the copying took place on his last day of work. The court found the Citrin standard to be unworkable and confusing. Instead, it held that Widder did not exceed his authorized access to the system even if he accessed and copied documents he was not entitled to see. Accordingly, the court dismissed the CFAA claim.

Based upon this decision, the CFAA is not an available remedy or a means of creating federal question subject matter jurisdiction in the District of Columbia for the theft of proprietary electronic information, except where the employer has terminated the employee's access rights before the theft occurs.

Publicly Available Software Code Can Be a Trade Secret if Compilation is Not Generally Known

A recent Fourth Circuit opinion analyzed when a software compilation can qualify for protection as a trade secret. The plaintiff company claimed that although its software used publicly-available mathematical formulas, the combination and implementation of these formulas contained in the source code for the software constitutes a trade secret. The Fourth Circuit agreed, holding that a trade secret may be composed of publicly-available information if the method by which that information is compiled is not generally known. Processes that are publicly known can become trade secrets when combined into a source code and the manner and sequence of the processes is unique and unknown to the public. The case is Decision Insights, Inc. v. Sentia Group, Inc., 2011 U.S. App. LEXIS 5151 (4th Cir. Va. March 15, 2011), and can be foundThe case can be found here.

The case arose when Decision Insights, Inc. (“Decision Insights”) filed a complaint against Sentia Group, Inc. (“Sentia”) and individual former employees alleging that Sentia’s development of a competing software application was based on materials obtained from the Sentia’s misappropriation of Decision Insight’s trade secrets. The question considered by the district court was whether Decision Insight’s software application, as a total compilation, could qualify as a trade secret under Virginia law.

Sentia had hired a former consultant for Decision Insights who worked to develop software for Sentia that would compete with Decision Insights’ software. According to Decision Insights, the software developed by Sentia is almost identical to its own. Decision Insights asserted that all the parameters, variables, and sequencing associated with the programs must have been the same as Decision Insights’ software to obtain such identical software.

The criteria for establishing the existence of a trade secret under Va. Code § 59.1-336 includes whether or not the compilation has independent economic value, is generally known or readily ascertainable by proper means, and is subject to reasonable efforts to maintain secrecy.

On appeal, the court considered whether Decision Insights adduced enough evidence at trial for a jury to reach the conclusion that Decision Insights’ software, as a compilation, is not generally known or ascertainable by proper means. At trial, Decision Insights had introduced two experts who testified that part of the source code was unknown to the public and the sequence of the processes was unique and not publicly available. One expert identified 13 proprietary processes in the source code, and stated that “[t]he collection of these processes as a whole and the sequence of these processes also serve as a proprietary aspect of [Decision Insights’ software].” Opinion at 14.

The court held that due to the evidence offered by the two experts, the trial court erred in concluding that Decision Insights had not satisfied its evidentiary burden to show that its software compilation was not generally known or readily ascertainable by proper means. The court noted that a trade secret may be composed of publicly-available information if the method by which that information is compiled is not generally known. The court cited Servo Corp. of America. v. General Electric Co., which held that a trade secret “might consist of several discrete elements, any one of which could have been discovered by study of material available to the public.” 393 F.2d 551, 554 (4th Cir. 1968). The court also found that numerous variables that were part of the Decision Insights software code were not in public literature or known outside the company.

The court remanded and directed the district court to consider other criteria specified by the Virginia Trade Secret Misappropriation Act, including whether Decision Insights’ software code has independent economic value and whether Decision Insights engaged in reasonable efforts to maintain the secrecy of the software code. See Va. Code. Section 59.1-336.

In the past, parties have claimed that a company’s products or process are not trade secrets unless kept strictly and wholly confidential. This case is important because it allows some components of trade secret information to be publicly known in certain circumstances while maintaining their trade secret status so long as other important information, such as the way those public pieces of software code are put together, remains confidential. The question of whether information was adequately kept confidential frequently arises in unfair business practices cases and this opinion helps clarify the issue.