Filed under: confidentiality, copyright, dispute resolution, limitation of liability, negotiation, trademark, transfer, TWoTW
These are the discussions that happened around the web this week – maybe you already read about them, maybe you need to again. Come join the party on twitter (follow me here and you’ll participate in the conversation live.)
I also realized that many of you might have no idea what you’re seeing below. Sorry. These are “tweets”, 140 maximum character messages sent via Twitter. Within the Twitterverse individual users follow others and have followers (think of it like overlapping Venn diagram circles). To read a tweet, you have to wade through a bit of jargon used to make the most of the 140 character limitation. “RT” for example, is shorthand for “Re-tweet” and the @____ is the username of some other individual on Twitter. Combined together, then, “RT @_____” means that someone else wrote a tweet that I found important and I now want to forward along to my followers. The URL’s are then also shortened by shortening services like bit.ly to make the most of the character limitation, too. Lastly, you might see “hash” identifiers “#______” which are ways to tag tweets of a particular flavor for easy searching later and “<” which means that I am commenting on what came before it.
- RT @raesmaa: Do your lecture notes violate your prof’s copyright? Holy crap! http://bit.ly/1yyPoT < Read comment #8 for the best analysis.
- RT @CopyrightLaw: “Focusing In On The Value: Google Books Provides An Amazing Resource” http://bit.ly/3d8YJB < Ends do not justify the means
- How to Avoid a Bad Bargain: Don’t Threaten: http://bit.ly/zPEzF
- Second Life sends TM infringement notice to SL educators: http://bit.ly/4qA2XO
- RT @gfiremark: New case throws cold water on constitutional challenges to statutory damages awards http://bit.ly/123lyz
- RT @CopyrightLaw: “Ideas, originality, and copyright. Coldplay accused of infringement again.” http://tinyurl.com/y8krmku
- RT @DanaNewman: Apple and Eminem settle copyright infringement case: http://bit.ly/22VfWw
- RT @fscavo: “Safe to say that the stimulus bill has been a failure” http://bit.ly/Y0TMY
- RT @vpynchon @cbsalary: First Court Order Served Via Twitter http://bit.ly/LQYRc
- RT @richards1000 @copycense Sweet: Complete collection of all USTR Special 301 Reports from 1989-2009 http://bit.ly/4xOXbX
- RT @CopyrightLaw: “Court rules (again) that Vernor can sell Autodesk software” http://tinyurl.com/ydm65tk
- RT’ing original thought w/o attribution is a copyright violation. Grrrrr.
- Amazon clarifies their Kindle book deletion policy: http://bit.ly/ESmwq
- RT @DanaNewman: Copyright Alliance asks Obama to support creators’ rights: http://bit.ly/18GR4T
- RT @nikiblack: “Is Twitter Grounds for Trademark Infringement?” | Corporate Legal … http://bit.ly/3ubzCM (via feedly)
- @kevino80 Actually, the BSA really can’t audit anyone. People only believe they can.
- RT @DeistPatriot: “Let us never negotiate out of fear. But let us never fear to negotiate.” – J.F.K. #tcot
- RT @mgmtmatters: The single most important thing to figure out during a negotiation – the other party’s position <Wrong. Know YOUR position.
- “I just stole a baby’s intellectual property.” – Modern Family <– Awesome.
- RT @vpynchon: Greatest predictor of long lifespan is being appointed to US Supreme court < Hehehehe. Awesome.
- RT @raesmaa: Nice blog on negotiations but seen that win-win is worth zero when a lawyer compensated for avoiding risks http://bit.ly/phaF1
- RT @maryadamsICA: New blog post: What’s the Right Definition of Intellectual Property? http://bit.ly/QKX5r
- RT @raesmaa: 1990s question for IT vendors – what’s your sales model? 2010s IT – what’s your scales model? (via @monkchips)
- RT @BrettTrout: Microsoft gets $388M patent infringement judgment tossed out http://is.gd/3OUWc
- RT @drjimanderson: He Who Works the Hardest Wins the Negotiation: http://EzineArticles.com/?i…
- New post at licensinghandbook.com : Response to 50 Tips http://bit.ly/pdBsc
- @DanaNewman I love Track Changes (one of only 10 key Word features that should exist). 24# paper? Please. I’m happy if it’s signed. 🙂
- RT @smallfirm Berge’s 2nd Principle of Practicing Law, “Sue solvent defendants.”
- 50 Tips for Writing a Contract http://bit.ly/MON8g (HT to @dananewman for the link) < But only abt 30 of the tips are actually good ideas
- RT @DanaNewman: Judge tosses out remaining claims against Disney in long-running Pooh copyright case: http://bit.ly/ZmtlV
- RT @GregBufithis: RT @JanusPatents: Patent BlackBerry Battle: RIM/NTP Patent Case Takes New Turn http://bit.ly/7lztW < NTP not satf w/ $612M
- RT @TradeSecretLaw: Intangible assets make up 75% or more of your company’s value. Can you identify your intangible assets?
- RT @CopyrightLaw: “Corporate Reorg Caused Breach of Non-Transfer Provision of License” http://bit.ly/IJKVR < I want to see the full license.
- RT @CopyrightLaw: “I wish law professors realized that’s what lawyers should always do.” http://tinyurl.com/ydf34o4
- Apple Introduces New Educational Software Licensing Program for Institutions: http://bit.ly/TgbuY (via MacRumors.com)
- RT @GregBufithis: RT @dnball Licenses to use intellectual property are not transferable unless that right is in writing http://bit.ly/UTMPe
- RT @gtiadvisors: Mega-Breaches Employed Familiar, Preventable Attacks http://bit.ly/W3bHP < Which is why I won’t remove cont’l liability.
Filed under: confidentiality, current events, information security, limitation of liability
When Clear announced their intent to terminate operations, the big question was: “What’s going to happen to each users’ private data (things like, um, fingerprints and background checks)?”
Now we know. They intend to SELL IT! This is why I harp on making sure that you have the proper provisions in your contract(s) for confidentiality, indemnification, information security and limitation of liability
Interestingly enough, however, this violates the terms of that agreement (as it existed when I pulled it from flyclear.com on June 29, 2009) – boldings are mine:
3. ADDITIONAL LIMITATIONS ON APPLICANT AND MEMBER PERSONAL INFORMATION
A. We do not sell or give lists or compilations of the personal information of our members or applicants to any business or non-profit organization. We do not provide member or applicant personal information to any affiliated or non-affiliated organizations for marketing.
B. None of the information that we collect may be used for any purpose outside the operation and maintenance of the Clear Services.
C. We would only disclose personal information about members or applicants if required to do so by law or legal process.
The termination of operation might be considered a “legal process” – but the way the language is written, 3.C. would not be valid as a result of the company’s dissolution. Thus, they’re limited to 3.A. – which clearly states that they won’t sell the information to “any business.” I wonder what the chance is now that they’ll only sell it to someone who’s TSA-approved.
*Not that the government doesn’t now already have your information as a result of the background check. I’m just sayin’.
Filed under: confidentiality, IP Indemnity, limitation of liability, risk, SaaS
Well, it didn’t take too long. C-Net reports today that Google inadvertently shared some Google docs files with folks they weren’t supposed to be shared with.
Lifehacker ponders whether this is a “minor privacy blunder”.
Meanwhile, Google is busy blaming it on the user (italics are mine): “We’ve identified and fixed a bug which may have caused you to share some of your documents without your knowledge.”
Yeah, Lifehacker, this isn’t minor. It never is. Especially to those individuals who have data that was shared without knowledge. Oh, and C-Net, you shouldn’t downplay this either – so while mentioning that lost laptops are a security risk, too, it doesn’t do anything to resolve the issue at hand.
Look folks, any breach of privacy, especially in a SaaS/cloud-computing environment is a HUGE problem. Shore up your contracts today, please (confidentiality, IP indemnification, and exclusions for breach of confidentiality in your limitation of liability language). Need help doing it? Just give me a shout.
Filed under: limitation of liability, process, SL Ed Series, Uncategorized, warranty
Designed for the busy or on-the-go professional, the Software Licensing Education Series (SLES) is video-based training on the complete gamut of software licensing topics. Presented in a college-course level format, with topics increasing in complexity and building upon prior lessons, the SLES allows an audio-visual learner another way to gain knowledge on licensing topics. Each video is approximately 20-30 minutes in length, so each Track contains about 2 hours of expert instruction in core software licensing topics!
The 300 Track videos include:
SLES 301 – Warranties
SLES 302 – Indemnification
SLES 303 – Limitation of Liability
SLES 304 – Services Issues 1
(400s-500s Tracks are currently in production and will be released shortly!)
Videos are formatted for a computer or portable video player (such as an iPod) and consist of a slide-show format with voice-over instruction, so you can even learn just by listening!
As promised, purchasers of the Second Edition of the Software Licensing Handbook are eligible for a discount on the purchase of a Track from the SLES. When redeeming your free Software License Risk Matrix, you’ll receive a coupon code for the SLES via e-mail.
A contract is an allocation of risk and liability limits are a huge bone of contention.
Vendors want to limit their liability to very specific types of damages: 1. They want to only be responsible for direct damages; and, 2. They only want to be liable up to a capped dollar amount. Generally speaking, this is acceptable (we’ll talk about the dollar amount in a second), as it’s a question of reasonability.
With respects to the types of damages (direct, indirect, consequentials, specials, etc), direct damages (in a very layperson definition) are those that are connected to the cause of the liability. So, for example, if Person A steals from Person B, the cost of the stolen goods would be direct damages. But, in the event that the theft led to Person B being unable to complete another business transaction (and thus negatively impacting Person B), that negative impact would be “consequential.” You can quickly see that damages other than directs can be hard to quantify or calculate – and someone who would be liable for more than directs would not have a good way to understand their total portfolio of liability.
For dollar amounts, most people used to say that you could reasonably ask for 3x the amount “spent” under the terms of the agreement. But to be fair to both sides, any amount I might recommend here isn’t a fair assessment of damages. When discussing software deals gone bad, I typically want every penny I’ve paid over the term of the agreement returned to me – this is less an exact science of knowing the amount of future damage and more of an understanding of what it costs to replace software once integrated into an environment.
With respects to both limitations on liability (type and amount), customers should be able to get three exceptions: A. Indemnification Obligations (including both IP and general indemnity), B. Breach of Confidentiality, and C. Gross Negligence or Willful Misconduct. These three things, in my (supported) opinion, are eligible for ALL forms of liability and without any financial limit, either. In almost all cases, vendors do not challenge these exclusions from the limits. They recognize, as does the customer, that indemnification is only valuable when unlimited, that breaches of confidentiality have far reaching implications, and that willful acts shouldn’t be capped, either.
However, even a generous vendor is only going to allow themselves to be “on the hook” for indemnification for software that they licensed in the form in which it was licensed, or for certain types of damages. Modifications to the software, for example, usually prevent indemnification to the extent that the infringement is a result of those modifications and not based on the unmodified software received from the provider. However, in many instances, vendors rely heavily on talking the customer through various issues via phone or via e-mail and they provide a variety of bug fixes in numerous ways. It is advisable to change any language limiting liability as a result of modifications made by licensee to read “modifications made by customer unless authorized by provider.” This allows for the ability of the customer to make changes to the software at the vendor’s direction but not remove the vendor’s liability for the changes that are made.
In some cases, vendors are concerned that even this language is not enough protection as the customer might not follow the directions/instructions provided by the vendor. If that is the case, language such as “modifications made by customer unless authorized in writing by vendor and such modifications explicitly conform to the changes contained in the written authorization” can be used. The net result is that the customer should not be harmed as a result of following the directions of the provider with respect to their software.
Recently, I’ve seen some significant push-back on the limitations section – a desire to avoid the exclusions and reductions in the financial amount, as well. I’m pushing back and I continue to use one of my favorite bad-cop/jerk phrases when discussing what will happen if the vendor breaches confidentiality (“I want to own your company.”). What’s happening in your deals?