Category Archives: Contracts

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.

“Right to audit” provisions in technology services agreements can benefit both parties

“Right to audit” provisions in technology services agreements are common. You’ve seen them. A typical section will read something like this:

Vendor will keep accurate and complete records and accounts pertaining to the performance of the Services. Upon no less than seven (7) days’ written notice, and no more than once per calendar year, Customer may audit, or nominate a reputable accounting firm to audit, Vendor’s records relating to its performance under this Agreement, including amounts claimed, during the term of the Agreement and for a period of three months thereafter.

Clearly these provisions generally benefit the customer, to give it some transparency and assurance that the vendor is performing the services according to the agreement and that vendor is charging customer for the services appropriately.

But a right to audit provision can benefit the vendor (and go against the customer) as well. As a recent court decision shows (Carlson, Inc. v. IBM, 2013 WL 6007508 (D. Minn. November 13, 2013)), a customer’s comprehensive audit rights can preclude it from claiming that vendor owes it a fiduciary duty.

In the case, the customer sued its software vendor alleging, among other things, that the vendor breached its fiduciary duty. The customer argued that it had to essentially “hand over the keys” of its operations to the vendor. But the court ruled that vendor did not owe customer a fiduciary duty because the customer had several important rights to know about and control the vendor’s performance.

The master services agreement between the parties reserved for the customer the right to audit the vendor’s performance and challenge its pricing and delivery of services. Under the agreement, customer had:

  • regular and recurring access to vendor personnel;
  • access to complete records and supporting documentation underlying vendor’s services;
  • the right to conduct operational audits to examine vendor’s performance of the services;
  • the right to audit performance for comparison to standards in the service level agreement;
  • the right to financial audits to verify the accuracy and completeness of invoiced charges.

The court found that “[t]hese audit and oversight provisions [were] meaningless if [customer] was as helpless as it [claimed].”

So while vendors may find right to audit clauses to be a nuisance, they should remember that the presence of such a clause could provide an important defense in litigation over the technology agreement.

Evan Brown is a Chicago attorney helping businesses negotiate and draft technology services and development contracts. He also handles many other issues involving the internet, copyright and trademarks, and new media. Call him at (630) 362-7237 or email ebrown@internetcases.com.

Jury finds in favor of IMDb in case brought by actress over published age

Hoang v. IMDb.com, No. 11-1709, W.D.Wash. (Jury verdict April 11, 2013)

Actress Junie Hoang was upset that IMDb published her real age (she was born in 1971). She sued IMDb claiming it breached its Subscriber Agreement (particularly its privacy policy) by using information she provided to cross-reference public records, and thereby ascertaining her correct age.

The case went to trial on the breach of contract claim. The jury returned a verdict in favor of IMDb.

Though we don’t know the jury’s thinking (we only have a simple verdict form), IMDb had argued, among other things, that its investigations of plaintiff’s birthday were in response to requests she had made. In 2008, plaintiff had asked IMDb to remove a false (1978) birthdate plaintiff had submitted a few years earlier. When IMDb conducted its own research, it found plaintiff’s real birthdate in public records, and published that. The jury found this did not violate IMDB’s Subscriber Agreement.

GoDaddy outage reminds us why limitation of liability clauses are important

The legal team at GoDaddy today probably had more than one conversation about Section 13 of the company’s Universal Terms of Service. That Section contains pretty widely used language which limits how badly GoDaddy could get hurt by an epic failure of its system like the one that happened today.

We are conspicuously told that:

IN NO EVENT SHALL Go Daddy, ITS OFFICERS, DIRECTORS, EMPLOYEES, OR AGENTS BE LIABLE TO YOU OR ANY OTHER PERSON OR ENTITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES WHATSOEVER . . .

Language like this is critical to technology service agreements. Today’s huge blackout illustrates the extent to which GoDaddy would be on the hook if such a limitation were not in place. Thousands of sites were offline for hours, losing uncountable pageviews and ecommerce sales. Holding GoDaddy responsible for those millions of lost dollars (which would be in the categories of indirect, special and consequential damages) could put a company into bankruptcy. GoDaddy would be big enough (probably) to pick up the tab in such a situation once or twice. Smaller enterprises would likely not be as lucky.

This kid is like GoDady inasmuch as he's trying to limit his liability.

To illustrate the effect of limitation of liability clauses, I have often used the example of similar language in Microsoft’s end user license agreement for Office. Because that is there, you cannot go after Microsoft for the business you lose if Word fails on your computer and you miss the deadline for submitting that big proposal. After today we have a new, perhaps more relevant example. GoDaddy would be pretty protected if you claim that you missed out on that million dollar client because your website was down.

So if you were looking for me through my site today, let me know, so I can send a bill for what you would have paid me to GoDaddy. Then again, I guess I’ve already shown why that won’t get paid.

Photo courtesy Flickr user Mikol under this Creative Commons license.

DMCA takedown notices are not just for content

Apple using the DMCA to stop early sales of iOS 6.

The infamous Digital Millennium Copyright Act takedown process gets quite a bit of press when content owners such as movie studios and record companies use it to take infringing copies of films or music offline. The safe harbor provisions of the DMCA are at the heart of content-distribution platforms’ defenses against infringement occasioned by users of the platform. (Think Viacom v. YouTube.)

Apple reminds us, however, that the DMCA gives all copyright owners — not just those who own copyrights in content – a mechanism for getting infringing works off the internet. According to this piece on Engadget, Apple has been contacting hosting providers of sites that offer unauthorized copies of the forthcoming iOS 6 for sale.

So the DMCA, acting in the name of copyright protection, provides a remedy for software providers to keep the clamps on parties who may have access to software for their own use (in this case, iOS developers) but go outside the bounds of such use and offer the technology for sale to others.

Megaupload takedown reminds us why website terms and conditions can be important

Kashmir Hill pointed out that at least one erstwhile file sharing service has changed its business model in response to the federal government’s action against Megaupload. She observes that:

FileSonic users can’t be too happy to have one of the main features of the site taken away. But the company must be less worried about its breach of contract with existing users than it is about the possibility of getting the Megaupload treatment, i.e., arrest, seizure of its property, and a criminal indictment.

This raises an important point. Any kind of online service that pushes the legal envelope may want to build in some mechanisms to pull back with impunity if it gets freaked out or loses its envelope-pushing courage. Said another way, that service should not make promises to its users that it cannot keep in the event the service wants to change what it is doing.

Some well known user generated content sites do this pretty well already in their terms of service. For example:

  • Dropbox: “We reserve the right to suspend or end the Services at any time, with or without cause, and with or without notice.”
  • YouTube reserves the right to discontinue any aspect of the Service at any time.”
  • Reddit: “We also reserve the right to discontinue the Program, or change the content or formatting of the Program, at any time without notice to you, and to require the immediate cessation of any specific use of the Program.”
  • Facebook (being kind of vague): “If you . . . create risk or possible legal exposure for us, we can stop providing all or part of Facebook to you.”

All good examples of foresight in drafting website terms and conditions that help innovative sites with damage control.

Wedding photographer not responsible for risque photos of bride posted online

Bostwick v. Christian Oth, Inc., 2012 WL 44065 (N.Y.A.D. 1 Dept. January 10, 2012)

Plaintiff bride logged onto her wedding photographer’s website and saw photos of herself wearing only underwear. She emailed an employee of the photographer, who promised to take the offending photos down. But they remained on the website even after plaintiff shared the online password with her family and friends.

So she sued the photographer for breach of contract, fraud and concealment, and negligent infliction of emotional distress. The trial court threw the case out on summary judgment. Plaintiff sought review, but the appellate court affirmed.

Breach of contract

The court found that defendant was authorized by agreement to post the photos. Defendant owned the copyright in the photos and otherwise had the right to put the proofs online. Any demand by plaintiff that the photos be taken down did not serve to revoke any of defendant’s rights, as plaintiff never had the rights to make such a determination to begin with. Moreover, the court found that because the agreement between the parties had an integration clause which provided that any amendments had to be in writing, the subsequent communications between plaintiff and defendant’s employee did not serve to amend the contract. (This decision by the court is puzzling, as the communications about taking the photos down were apparently by email. Other New York courts have held emails sufficient to amend written contracts.)

Fraud and concealment

To have been successful on her fraud and concealment claim, plaintiff was required to show, among other things, that she reasonably relied on defendant’s statement that the underwear photos had been taken offline before she gave the password to her friends and family. The court found in favor of defendant on this point because plaintiff could have checked to see whether the photos were actually taken down before she allowed others to access the photos. What’s more, the court found that the failure to take the photos down was not “concealment” but merely an oversight.

Negligent infliction of emotional distress

Despite its sympathy with plaintiff, and an acknowledgment that having others see the photos would be embarrassing and upsetting, the court found that plaintiff failed to establish a case of negligent infliction of emotional distress. This part of the case failed because plaintiff did not show that she had been exposed to an unreasonable risk of bodily injury or death. There was nothing in the record to cause plaintiff to fear that she was exposed to physical harm.