My final post in my series on Key Software Escrow Strategies will discuss the use rights to a developer’s intellectual property if a software escrow release occurs. It will also touch on copyright protection behind the development of the intellectual property (IP) and the responsibility of managing someone else’s “brainchild.”
When two parties enter an escrow relationship, the last thing either party wants is an escrow release. For good reason, the developer is usually afraid of outside parties accessing their intellectual property; and licensees really don’t want to manage the software themselves. (Hence the reason for the business relationship, so the developer can manage the software for the licensee.)
When it comes to software, trade secrets protect the source code and copyright is used to protect the expression of intellectual property (software application) that the developer is creating. Software is basically a set of instructions for computers to follow. The developer is a lot like an author writing a guidebook in the 0s and 1s of binary code, explaining instructions for an application to perform.
According to the U.S. Copyright Office, Publications Section, the challenge with a “right to use” is it may give the licensee more rights to the software than the developer realizes. To eliminate potential confusion, the developer should determine upfront:
- Will the licensee have the right to distribute the code to a third party to modify/support?
- Can the licensee reproduce the software? And, if so,
- How long can your licensee reproduce the software?
On the other hand, as the recipient of intellectual property (software) from an escrow release, the licensee has the right to use the software for the sole purpose of continuing the benefits afforded to them via the license agreement. This also means the licensee is obligated to maintain the confidentiality of the released software. I’m pretty sure you can see the problem. If the licensee has the right to use the software for the “sole purpose of continuing the benefits,” but they lack the aptitude required (“reasonable knowledge”) to manage the software, then outsourcing the problem to a third party becomes the only option. It reminds me of the scene from Wayne’s World (which is a parody of the Faberge Organics shampoo commercials that aired in the 1970s and 80s) – “First they tell two friends, then they tell two friends, and so on.”
At the end of the day, your licensing agreement should provide clarity in regard to the actual “rights” in the “use rights” clause in your agreement. It’s too easy for misinterpretation and nobody wants their software misappropriated. The developer should determine what level of access they feel comfortable with before entering an escrow agreement.
As the developer, will you provide:
- Source code for modifying or creating derivative work
- The right to share under existing confidentiality provisions with a third party that will maintain or support
- The right to use within the company and not be restricted by the current platform, machine or server.
Of course, if the software is embedded or distributed, then the example above targeted around internal use does not apply and you would want use rights that allow you to sell, reproduce, enhance, and continue with your intended plans around embedding in your service or product that you sell.
I hope this has been helpful in explaining more about use rights for software source code in escrow. If you missed any of my previous posts for managing a software escrow agreement from start to finish, here are the links for the other topics.
In my first post, “What’s in Your Software Deposit?“, we discuss the suggested materials for escrow. In “Why Would You Verify your Software Escrow Deposit?” we discuss how the “devil is in the details” when it comes to managing an escrow relationship.
I followed those blogs with a post that addressed the age-old question of “Who Pays for Software Escrow?” and provided an explanation of the standard release conditions for an escrow agreement in my post “Please Release my Escrow!“. In my last post, we walked through a simulated event of a hypothetical escrow release in “What you Need to know about the Software Escrow Release Process.”
My goal is that you now better understand the methodology of a strong escrow relationship and the value Iron Mountain can provide as a trusted third party. If you have any questions, feel free to email me at firstname.lastname@example.org.