Limitation of liability clause in software license agreement did not excuse customer from paying fees

Customer did not like how software it had bought performed, so it stopped paying. Vendor sued for breach of contract, and customer argued that the agreement capped its liability at $5,000. Both parties moved for summary judgment on what the following language from the agreement meant:

NOTWITHSTANDING ANYTHING TO THE CONTRARY, THE TOTAL DOLLAR LIABILITY OF EITHER PARTY UNDER THIS AGREEMENT OR OTHERWISE SHALL BE LIMITED TO U.S. $5,000.

Customer argued that the sentence meant what it said, namely, that customer would not be liable for anything over $5,000. But the court read otherwise, holding that construe the language as excusing customer’s payment of fees would render those provisions calling for fees (which were much more that $5,000) meaningless.

The court observed that when parties use the clause “notwithstanding anything to the contrary contained herein” in a paragraph of their contract, they contemplate the possibility that other parts of their contract may conflict with that paragraph, and they agree that the paragraph must be given effect regardless of any contrary provisions of the contract.

In this situation, the $5,000 limitation language was the last sentence of a much longer provision dealing with limitations of liability in the event the software failed to function properly. The court held that the rule about “notwithstanding anything to the contrary” applies if there is an irreconcilable difference between the paragraph in which that statement is contained and the rest of the agreement.

There was no such irreconcilable difference here. On the contrary, reading in such difference would have rendered the other extensive provisions dealing with payment of goods and services meaningless, which would have violated a key canon of construction.

IHR Sec., LLC v. Innovative Business Software, Inc., — S.W.3d —, 2014 WL 1057306 (Tex.App. El Paso March 19, 2014)

Evan Brown is an attorney in Chicago, advising clients on matters dealing with software licensing, technology, the internet and new media.

Related:

In software dispute, court enforces forum selection clause and transfers case from California to Michigan

Though parties often think of forum selection clauses as throwaway “boilerplate” language, a recent case demonstrates the influence such a clause can have on where litigation takes place.

Plaintiff sued defendant in California for fraud and other claims relating to the alleged defective performance of electronic medical records software. Defendant moved to transfer the matter to federal court in Michigan, based on a forum selection clause in the agreement that provided, in relevant part, that “[a]ny and all litigation arising from or relating to this Agreement will be filed and prosecuted before any court of competent subject matter jurisdiction in the State of Michigan.” Plaintiff objected to the motion, arguing that enforcement would violate California public policy in a number of ways. The court rejected plaintiff’s arguments and granted the motion to transfer.

Plaintiff argued that transfer would go against California’s public policy against unfair business practices, and would also be against the policy of incentivizing medical providers to adopt electronic medical records systems. The court rejected these arguments because plaintiff’s motion dealt with venue, i.e., where the lawsuit would occur, not which substantive law would apply. Given that the potential existed for the federal court in Michigan to consider whether California law should apply, transferring the case would not cut against public policy.

The court further rejected plaintiff’s argument that the forum selection clause was unconscionable, given that plaintiff did not dispute that she read the clause, and was a sophisticated party. Moreover, citing to language of the Supreme Court on the issue, the court refused to consider arguments about the parties’ private interests. “When parties agree to a forum-selection clause, they waive the right to challenge the preselected forum as inconvenient or less convenient for themselves or their witnesses, or for their pursuit of the litigation.”

East Bay Women’s Health, Inc. v. gloStream, Inc., 2014 WL 1618382 (N.D.Cal. April 21, 2014)

Evan Brown is an attorney in Chicago, advising clients on matters dealing with technology, the internet and new media. Follow him on Twitter @internetcases

Related:

[This is a cross post from the InfoLawGroup blog.]

Daughter’s Facebook post costs dad $80,000

A recent case illustrates why (1) it is important for parties to abide by the confidentiality provisions of settlement agreements, and (2) people who learn confidential information should keep their social media mouths shut.

Plaintiff sued his former employer (a private school) for age discrimination and retaliation. The parties later settled the case and entered an agreement containing the following provision:

13. Confidentiality … [T]he plaintiff shall not either directly or indirectly, disclose, discuss or communicate to any entity or person, except his attorneys or other professional advisors or spouse any information whatsoever regarding the existence or terms of this Agreement … A breach … will result in disgorgement of the Plaintiffs portion of the settlement Payments.

After the parties signed the settlement agreement, plaintiff’s college-age daughter posted this on Facebook:

Mama and Papa Snay won the case against Gulliver. Gulliver is now officially paying for my vacation to Europe this summer. SUCK IT.

facepalmDefendant school district refused to pay a portion of the settlement payments ($80,000), claiming plaintiff’s disclosure of the settlement to his daughter violated the confidentiality provision. Plaintiff asked the trial court to enforce the settlement agreement, which it did. Defendant sought review with the Court of Appeal of Florida. On appeal, the court agreed with the school and reversed.

The court found that “before the ink was dry on the [settlement] agreement, and notwithstanding the clear language of section 13 mandating confidentiality, [plaintiff] violated the agreement by doing exactly what he had promised not to do.” And his daughter “then did precisely what the confidentiality agreement was designed to prevent, advertising . . . that plaintiff had been successful in his age discrimination and retaliation case against the school.”

Gulliver Schools, Inc. v. Snay, — So.3d —, 2014 WL 769030 (Fla.App. 3 Dist. Feb 26, 2014)

Photo credit Flickr user haikus under this Creative Common license.

Court sides with software developer in open source dispute

Case provides rare opportunity to get court’s analysis of GPL.

300px-Heckert_GNU_white.svgPlaintiff wrote an XML parser and made it available as open source software under the GPLv2. Defendant acquired from another vendor software that included the code, and allegedly distributed that software to parties outside the organization. According to plaintiff, defendant did not comply with the conditions of the GPL, so plaintiff sued for copyright infringement.

Defendants moved to dismiss for failure to state a claim. The court denied the motion.

Plaintiff claimed that defendant directly infringed its copyright by distributing the software without any attribution to plaintiff, without plaintiff’s copyright notice, without reference to plaintiff’s source code, and without any offer to convey the source code.

Defendant argued that it did not violate the terms of the GPL because its “distribution” of the software was merely internal, mainly to its own financial advisors. Accordingly, defendant argued, the requirements under the GPL to, among other things, attribute plaintiff and provide the source code were not triggered.

The court rejected defendant’s argument, looking to the allegations in the complaint that defendant distributed the software to it vendors in India, as well as providing it to “thousands of non-employee financial advisors.”

Despite the popularity of open source software, not a lot of courts have interpreted and applied the provisions of open source licenses. This case — if it does not settle — provides a rare opportunity to see serious legal treatment of the oft-used GPL.

XimpleWare Corp. v. Versata Software, Inc., 2014 WL 490940 (N.D.Cal. February 4, 2014)

Evan Brown is a Chicago technology and intellectual property attorney helping software vendors and customers alike navigate the many issues pertaining to technology development and licensing.

1 2 3 4 5 12 13 14