Attorney Evan Brown

January 18, 2023 Contracts, Licensing

Why are limitation of liability provisions important in technology agreements?

liability cap

Limitations of liability are an important aspect of any technology agreement, as they help to define and limit the amount of financial responsibility that each party in the agreement must accept in the event of a dispute or legal action.

Caps

One of the main limitations of liability in a technology agreement is the cap on the amount damages. This means that even if a party is found to be at fault in a dispute, the maximum amount of financial responsibility that it is willing to accept is limited to a specific dollar amount. For example, a technology company may agree to a cap on damages of $1 million in the event of a legal dispute. Or it could agree that the maximum amount it would have to pay would be whatever its insurance will cover. It is important to note that while damages caps can provide predictability and stability in terms of financial exposure, they can also limit the recovery of a party that has suffered significant losses. So they should be negotiated thoughtfully.

Exclusions

Another limitation of liability in a technology agreement is the exclusion of certain types of damages. This means that even if a party is found to be at fault, they are not responsible for certain types of losses or damages. For example, a technology company may exclude consequential damages, such as lost profits or loss of business, in the event of a legal dispute.

Carveouts

Though a limitation of liability provision may call for a damages cap or an exclusion of the types of damages available, parties recognize that in certain situations, damages should not be limited. For example, a breach of confidentiality by one party may be particularly harmful to the other party, and thus it would be unfair to cap the amount of damages. Another example arises in the context of indemnification. If one party is obligated to pick up the tab because the other party got sued for what the indemnifying party did, then the indemnified party will want to make sure it is made whole, regardless of what the damages are. In situations such as these, the parties may negotiate a “carveout” from the damages cap or exclusion, and agree that if something occurs within a defined set of circumstances, the liability caps or exclusions will not apply.

Limitations on limitations

It is important to keep in mind that limitations of liability are subject to legal interpretation and may not be enforceable in all jurisdictions. They can be evaluated and interpreted by courts in different ways. Additionally, some courts may hold that a limitation of liability clause is unenforceable if it is found to be unconscionable or against public policy.

Tough negotiation

In many technology transactions, the limitation of liability provision is among the last remaining issues to negotiate. This fact underscores how important such provisions are in making a particular transaction palatable to a party. A particular vendor may not be willing to “bet the company” on a particular deal (i.e., would not want to risk everything if something goes wrong). So these sorts of provisions are useful in giving parties comfort to enter into a deal.

Evan Brown is a technology attorney in Chicago. Follow him on Twitter: @internetcases

January 17, 2023 Anonymity, Cryptocurrency

Cryptocurrency scam victim can seek to identify Coinbase, Binance and Gemini users

A federal court in Wisconsin allowed a cryptocurrency scam victim to try to find out who stole his cryptocurrency. It found that good cause existed to allow the plaintiff-victim to send subpoenas to Coinbase, Binance and Gemini.

cryptocurrency scam victim

The Federal Rules of Civil Procedure state that a party cannot seek discovery “from any source before the parties have conferred as required by Rule 26(f).” So plaintiff was required to get authorization from the court before seeking information from the various cryptocurrency exchange platforms onto which he believed his assets had been placed. He filed a motion requesting such authorization.

The judge first observed that various trial courts within the same federal circuit (this case arose in Wisconsin federal court, which is in the Seventh Circuit) have applied different tests when deciding whether “expedited discovery” is appropriate. One such test requires, among other things, that the party seeking discovery show that it will suffer irreparable harm if the request is not granted. The other test – the good cause standard – allows expedited discovery “when the need for [such discovery], in consideration with the administration of justice, outweighs the prejudice to the responding party.”

In this case, the court applied the good cause standard. But the court did not allow plaintiff to send subpoenas concerning all of the information he had asserted should be discoverable. For example, plaintiff asked the court for permission to seek the Doe defendant’s social security number, as well as transaction logs and correspondence. The court found such requests “go far beyond seeking the defendants’ identifying information” and would instead be the types of discovery requests the court might expect plaintiff to make once the defendants have been identified and plaintiff is seeking discovery as to his substantive allegations. Instead, the court permitted expedited discovery for the sole purpose of obtaining information to identify the John Doe defendants. This information included only the name, street address, telephone number and e-mail address of each John Doe.

The court further ordered that Coinbase, Binance and Gemini had to provide a copy of the subpoena to each John Doe and any other affected user as soon as possible after service of the subpoena. The court’s order also provided that each of the platforms and any affected user must have 14 days from the date of service of the subpoena to object to the subpoena under Federal Rule of Civil Procedure 45(d)(2)(B). The platforms were ordered not to disclose any John Doe’s identifying information, or such information for any other affected user, during that fourteen-day period (unless or until the court may otherwise order). The platforms were also ordered to preserve any material responsive to the subpoena for a period of no less than 90 days to allow the plaintiff to file a motion to compel.

Wuluvarana v. Does 1-3, 2023 WL 183874 (E.D. Wisconsin, January 14, 2023)

Evan Brown is a technology and intellectual property attorney in Chicago. Follow him on Twitter at @internetcases.

See also:

January 16, 2023 Contracts

What are audit provisions in a technology contract?

audit provision

An audit provision in a technology contract is a clause that allows for one party to inspect and perhaps copy certain business records and other information of the other party. Often an audit provision authorizes a party that owns licensed technology or software (the provider or licensor) to periodically inspect and audit the customer’s use of the technology or software. These types of provisions help ensure that the customer is using the technology or software in accordance with the terms of the agreement and that it is not infringing or otherwise misusing the technology or software. They can also be used to ensure that the customer is paying the appropriate license fees or royalties.

One often sees audit provisions in reseller agreements and revenue sharing agreements, to give the right of one party to inspect records that confirm it is being paid in accordance with the terms of the agreement. Since commissions are often calculated as a percentage of revenue, a referral partner may want to see the underlying records supporting the amounts the referral partner is being paid.

The audit provision typically outlines the procedures for the audit, such as the frequency of the audits (often expressed as “no more often than x times per calendar year”), who may conduct the audits (e.g., designees of the auditing party), and what information must be made available for review during the audit. It may also outline the rights and responsibilities of both parties during the audit process, including any limitations on the scope of the audit and the handling of any confidential information that is revealed during the audit.

An audit provision in a technology contract may provide that if the audit uncovers underpayment by the audited party (perhaps by at least a certain percentage) then the audited party will be responsible not only for the amount of the underpayment, but also for the costs incurred by the auditing party in conducting the audit.

Overall, audit provisions are an important aspect of technology agreements and play a vital role in protecting the interests of both parties involved. It is important for both parties to understand the audit provisions in the agreement and to comply with them fully in order to avoid any potential legal disputes.

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, domain names and new media. Call him at (630) 362-7237 or email ebrown@internetcases.com. Follow him on Twitter: @internetcases

January 11, 2023 Contracts, Licensing

Why are indemnification provisions important in technology contracts?

vicarious liability copyright

Indemnification provisions in technology agreements play a crucial role in protecting the parties involved in a technology transaction. These provisions are often included in agreements among technology vendors, customers, software developers, and other related parties to shift the risk of losses and legal liabilities from one party to another.

Picking up the tab

Indemnification is a legal concept that involves one party (the indemnitor) agreeing to compensate the other party (the indemnitee) for any losses or damages that may occur as a result of a specific event or occurrence. Similarly, a provision of this sort may provide that one party will “defend” the other party by retaining counsel and paying the costs of defense in court, as those costs are incurred. In technology agreements, indemnification provisions are often used to shift the risk of losses or damages that may result from a party’s breach of contract or negligence. Customers will often seek to insist that the vendor indemnify the customer in the event a third party files a lawsuit against the customer because the technology infringes that third party’s intellectual property rights.

The main purpose of indemnification provisions in technology agreements is to protect the parties involved from potential financial losses, legal liabilities, and other costs associated with legal disputes. For example, a contract may provide that if a software developer breaches a contract and causes a loss to the client, the indemnification provision would require the developer to compensate the client for any damages.

Key elements

Indemnification provisions in technology agreements typically contain several key elements, including the types of losses or damages that will be covered, the parties that are responsible for indemnifying the other party, and the time frame for indemnification to take place. It also often covers the notification requirements, the documentation and information that should be provided in case of losses or damages, and the limitation of liability.

Another key aspect of indemnification provisions is that they are often mutual, meaning that both parties are responsible for indemnifying each other in certain situations. This can help to ensure that both parties are protected in the event of a legal dispute, and it also helps to create a balance of risk between the parties.

Why bother?

Indemnification provisions in technology agreements play a vital role in protecting the parties involved from financial losses, legal liabilities, and other costs associated with legal disputes. It’s important for both parties to understand the concept of indemnification, the purpose of these provisions, and how they are typically used in technology agreements.

Evan Brown is a technology and intellectual property attorney in Chicago. Follow him on Twitter at @internetcases.

December 20, 2022 Trademarks

Does tagging the wrong account in an Instagram post show actual confusion in trademark litigation?

In a recent trademark infringement case, the court considered whether Instagram users tagging photos of one product with the account of another company’s product was evidence of actual confusion. In this case, the court found that it was not evidence of actual confusion.

Plaintiff makes premium tequila sold in bottles and defendant makes inexpensive tequila-soda product sold in cans. Plaintiff sued defendant for trademark infringement and sought a preliminary injunction against defendant. To support its assertion that it was likely to succeed on the merits of the case, plaintiff argued there was actual confusion among the consuming public. For example, on Instagram, at least 30 people had tagged photos of plaintiff’s products with defendant’s account.

The court found that in these circumstances, particularly where a marketing survey also showed less than 10% of people were confused by the defendant’s mark, that the incorrect tagging did not show actual confusion.

Though the bar for showing actual confusion is low, the court noted that a showing of confusion requires more than a “fleeting mix-up of names” and that confusion must be caused by the trademark used and must “sway” consumer purchase.

In this case, the court found that defendant’s evidence regarding mistaken Instagram tags did not establish a likelihood of trademark confusion that would result in purchase decisions based on the mistaken belief that the defendant’s tequila-soda product was affiliated with the plaintiff. At best, in the court’s view, the plaintiff’s evidence demonstrated a “fleeting mix-up of names,” which was not evidence of actual confusion.

The court likened this case to the recent case of Reply All Corp. v. Gimlet Media, LLC, 843 F. App’x 392 (2d Cir. 2021), wherein “instances of general mistake or inadvertence—without more—[did] not suggest that those potential consumers in any way confused [plaintiff’s] and [defendant’s] products, let alone that there was confusion that could lead to a diversion of sales, damage to goodwill, or loss of control over reputation.”

Casa Tradición S.A. de C.V. v. Casa Azul Spirits, LLC, 2022 WL 17811396 (S.D. Texas, December 19, 2022)

November 14, 2022 Blockchain, Trademarks

Meta prevails in trademark infringement litigation over its logo

In the case of Dfinity Foundation v. Meta Platforms, Inc., the court considered whether the new logo that Meta adopted after its 2021 rebranding infringed upon Dfinity’s trademark. In the infringement litigation that Dfinity brought over the issue, Meta moved to dismiss. The court granted the motion.

Dfinity operates the Internet Computer – a public blockchain network that seeks to provide developers and entrepreneurs with a public compute platform for building websites, enterprise systems and internet services within an open environment. Key to Dfinity’s efforts are “dapps” or decentralized applications. In 2021, the United States Patent and Trademark Office granted Dfinity a registration for the following mark: dfinity

When Meta rebranded in 2021, Mark Zuckerberg indicated, among other things, that the company would work with creators and developers in a decentralized fashion. In connection with the rebranding, Meta adopted and sought registration of this logo: meta logo

Dfinity sued in federal court in California alleging, among other things, trademark infringement. It alleged that the similarities between the marks, coupled with the related services and customer bases, will cause confusion because “consumers will mistakenly believe that Meta and its services … are connected with, sponsored by, affiliated with, or related to Dfinity and the Internet Computer.”

Meta moved to dismiss. In granting the motion to dismiss, the court found that confusion between Meta’s logo and Dfinity’s logo was unlikely as a matter of law.

Similarity of the marks

Employing the “sight, sound, and meaning” test, the court found the marks were dissimilar: Dfinity’s shape was a traditional infinity sign, with the lines crossing at the horizontal and vertical midpoint, rendered in a precise multicolor format that Dfinity instructs users of the logo not to alter. In the court’s view, the Meta logo looks different – while it includes two loops and bears some resemblance to an infinity sign, the lines cross above the vertical midpoint and the two loops are squished into vertical oblong shapes. Meta did not claim color as a feature of its mark.

Relatedness of services

On the question of whether the services provided under the two marks were similar, the court remained neutral. It noted that Dfinity has targeted developers interested in using blockchain to “build websites, enterprise systems and internet services within an open environment.” At the same time, “Meta targets everyone, including developers, some of whom presumably are interested in building their products within, or at least compatible with, such an ‘open environment.'” Meta argued that its products are antithetical to that vision, and there is no indication that it is interested in expanding into the realm occupied by Dfinity and the Internet Computer. But the court found that given Meta’s metamorphosis over the last few years, such a move is not implausible on the pleadings, particularly in light of Zuckerberg’s statement at the launch of the Meta brand.

Sophistication of users

The court then evaluated the types of users that would encounter the Dfinity and Meta logos, and whether, given their level of sophistication, confusion would be likely. The court found that because of the high level of sophistication, it is less likely one would be confused: “That these sophisticated people, immersed in the intricacies of the tech world, would be duped by a logo, particularly one that is not similar in key respects . . . borders on implausible.”

Actual confusion

Next the court considered whether purported instances of actual confusion weighed in favor of Dfinity. In this situation, Dfinity had provided six tweets that purported to show that users were confused. But the court disagreed. First, it noted that because the tweets were in reply to a Dfinity tweet, they did not express how the users would experience an encounter with the mark “organically”. And second, the court found that the content of the tweets indicated the users actually knew the difference between the two enterprises.

Marketing channels

Having found that the parties’ services were not “totally unrelated” at this stage, the court also found that the parties’ marketing channels were similar, but that this factor did not weigh as heavily as the others previously discussed.

Meta’s intent

Though Dfinity alleged “willful and wonton disregard of Dfinity’s established and superior rights” in its trademark, it did not provide evidence of that. And given that the court found the marks to be dissimilar, the court also found that Meta’s intent did not support a finding of likelihood of confusion.

Dfinity Foundation v. Meta Platforms, Inc., 2022 WL 16857036 (N.D. California, November 10, 2022)

November 10, 2022 Uncategorized

No breach of contract claim against Twitter for account suspension

The issues in the case of Yuksel v. Twitter were whether Twitter, by terminating plaintiff’s account (1) breached its contract with plaintiff, and (2) violated the Racketeer Influenced and Corrupt Organizations Act (“RICO”). Twitter moved to dismiss the breach of contract and RICO claims. The court granted the motion because Section 230 barred the claims and because plaintiff failed to plausibly allege the claims.

The gist of plaintiff’s claims centered on allegations that Twitter suspended plaintiff’s account due to deference to the Turkish government. He claims that by being cut from his 142,000 followers and by having 7 years’ worth of “intellectual content” destroyed, he was damaged to the tune of $142 million.

Section 230 immunity

The court held that Twitter was immune from plaintiff’s claims, under 47 U.S.C. §230(c)(1). That provision states that:

No provider or user of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider.

If found that Twitter is a provider of an interactive computer service, and that plaintiff sought to hold Twitter liable for decisions regarding information provided by another information content provider. In this situation, that other information content provider was plaintiff himself. The court also found that plaintiff sought to treat Twitter as a publisher in connection with its decision to suspend his account. But the decision to suspend an account is within the scope of “traditional publishing functions”. Quoting the well-known case of Barnes v. Yahoo!, Inc., 570 F.3d 1096, 1102 (9th Cir. 2009), the court noted that “removing content is something publishers do.”

Plaintiff tried to get around Section 230 immunity by asserting that his RICO claim fit into the statute’s carveout for federal criminal prosecution (Section 230 (e)(1) provides that “[n]othing in this section shall be construed to impair the enforcement of . . . any . . . Federal criminal statute.”) The court rejected this argument, concluding that the carveout from immunity extends only to criminal prosecutions and not civil actions based on criminal statutes.

Failure to state a claim

The court held that even without Section 230 immunity, the breach of contract and RICO claims would fail. Plaintiff had alleged breach of contract in the complaint, but in responding to the motion to dismiss stated that he did not claim breach of contract between himself and Twitter, but rather asked the court to find Twitter’s terms of service unenforceable because they permit the arbitrary and reckless deletion of user accounts. The court noted that it was constrained to not look beyond the complaint to allegations plaintiff made only in response to Twitter’s motion to dismiss.

On the RICO claim, the court found that plaintiff failed to identify the “enterprise” subject to the RICO claim, nor any purported “pattern,” “racketeering activity,” or “injury” to “business or property” caused by it. Moreover, according to the court, plaintiff’s conclusory allegations that Twitter was somehow in cahoots with foreign dictators failed to meet basic pleading standards in federal court.

Yuksel v. Twitter, Inc., 2022 WL 16748612 (N.D. California, November 7, 2022)

Company successfully defends against trade dress and copyright infringement claims over online software tool

trade dress

A federal court in Delaware dismissed most of the intellectual property infringement claims concerning a competing online room-planning software tool. The court held that plaintiff’s trade dress infringement and breach of contract claims failed, and that its copyright infringement claims failed, except for those allegations relating to the copying of computer code.

No trade dress protection where look and feel was functional

On the trade dress claim, plaintiff had identified fifteen elements that formed a cohesive “look and feel” of its software. And the court found – based on extensive use, wide advertisement and appearance in industry publications – that the trade dress had acquired secondary meaning. But the court found that the look and feel was merely functional and not subject to trade dress protection.

Copyright infringement – mixed bag

Similarly, the court dismissed the copyright infringement claim regarding the selection, arrangement and coordination of visual elements of the program. In the court’s view, these elements were merely functional and thus not subject to copyright protection. The court dismissed the copyright infringement claim as well concerning the tool’s graphics. On this point the court was even more bold – it found after a visual comparison of the works that they simply were not similar.

The court allowed the copyright infringement claim concerning the program’s code to move forward. It found that plaintiff had alleged both access and similarity. Plaintiff had also alleged that defendant repeatedly accessed the program to stress test the design, and that there were extensive similarities in the tools’ mechanics. These allegations were enough to survive a motion to dismiss.

Browsewrap not enough

Finally, the breach of contract claim failed, not on the basis of preemption as one might expect, but because the court found plaintiff had not sufficiently alleged that a contract had been formed. Plaintiff asserted that its website’s terms of service prohibited copying of the software, and that defendant’s employees should have been aware of those terms on a browsewrap theory – there was a link to the terms at the bottom of the page. But the court would not find that plaintiff alleged enough facts to plausibly allege that defendant’s employees manifested assent to those browsewrap terms.

Design With Friends, Inc. v. Target Corporation, 2022 WL 4448197 (D. Delaware, September 23, 2022)

Court dismisses company executive’s name and likeness lawsuit over YouTube videos

name likeness

Strouse was the president and CEO of a company but departed with the company was sold. He did not approve of how the new company continued to use YouTube videos Strouse had made when he was with the company. So Strouse sued under Pennsylvania law for unauthorized use of his name and likeness. The company moved to dismiss the claim and the court granted the motion.

There are three elements to a claim for unauthorized use of name and likeness under Pennsylvania law:

a natural person’s name or likeness must have commercial value;
the accused party must make an unauthorized use of that name or likeness; and
the use is for commercial or advertising purposes.

The court found that Strouse’s claim failed on the first and second elements.

Although he claimed he suffered substantial damages due to the company’s supposed misappropriation, the court found he offered no explanation for how or why these damages occurred. He did not allege that his name had any special reputation or prestige such that mention of his name or use of his image in a video on the company’s website could confer an actionable benefit.

And the court found that Strouse’s pleadings did not establish that the company was using the videos without authorization. Strouse had made the videos as president and CEO of the company – he certainly authorized such use then. The acquiring company purchased the business’s assets, including the videos that were made.

Wurth Baer Supply Co. v. Strouse, 2022 WL 4125802 (M.D. Pennsylvania, September 9, 2022)

Can a company snoop on its employee’s personal email account?

Plaintiff was an administrative assistant at defendant company. When her supervisor got word that plaintiff had been asked to join a competing company started by some other former company employees, the supervisor allegedly logged onto plaintiff’s work computer and without authorization accessed plaintiff’s Gmail account to get more information confirming plaintiff’s plans. Plaintiff was later terminated.

So she sued under the federal Stored Communications Act (“SCA”) and the Federal Wiretap Act (under a part of that act often called the Electronic Communications Privacy Act (“ECPA”)). Defendant moved to dismiss both the claims. The court denied the motion to dismiss the SCA claim but dismissed the ECPA claim.

The SCA prohibits, among other things, the intentional unauthorized access of a “facility through which an electronic communication service is provided”—thereby obtaining access to an electronic communication while in electronic storage. 18 U.S.C. § 2701(a). A court may award actual damages, statutory damages, and punitive damages for violation of the SCA. If a plaintiff seeks statutory damages under the SCA, it must prove actual damages. But one need not prove actual damages to recover punitive damages. The ECPA prohibits, among other things, the “interception” of electronic communication. 18 U.S.C. § 2511(a). Courts have generally held that such “interception” must be contemporaneous with transmission.

The court held plaintiff could move forward with her SCA claim even though she had not pled actual damages. She had sufficiently pled that she should be awarded punitive damages. And the court tossed the ECPA claim because the facts as alleged showed that the email messages the employer allegedly accessed had already been delivered and therefore were not intercepted as the statute requires for liability.

Benz v. PHB Realty Co., 2022 WL 3098579 (D. Kansas, August 4, 2022)

See also: