Software Copyright Notice And Disclaimer

All software developed at UC Berkeley should be copyright protected and thereby bear a clear, standardized copyright notice along with a disclaimer notice. This copyright and disclaimer notice protects the software author(s) and the University of California from any liability that might result, however remote, from the use of the software. Accordingly, the use of this notice is especially applicable to software made available for use beyond the author(s), and includes software distributed as "freeware" or open source via either computer networks, the Office of Technology Licensing, or other UC Berkeley organizations.

For software distributed with source code, the copyright and disclaimer notice should be imbedded within each file. For software distributed on physical media (e.g. CD ROM), the copyright and disclaimer notice should be printed on an external label (as well as in any source code). For software binary code distributed over a network, the copyright notice should be embedded in a "readme.txt" file that is sent along with the software. If practicable, the copyright notice should appear on an opening binary code display.

The approved format for the UC Berkeley Copyright and Disclaimer Notice is appended below. An acknowledgement of the software author(s) can be added to this notice. Note that the following copyright and disclaimer language assumes the most likely application of the UC Copyright Policy -- which is that the University is the sole owner of the software. Your particular software ownership situation might differ; for example, you might solely own the software, or there might be joint ownership of the software. If you have questions regarding software ownership, or any other questions about copyrightable software, then contact the Office of Technology Licensing.

Disclose Software

Get started protecting software, multimedia, or algorithms

Contact OTL

For questions regarding software ownership or copyrightable software.

UC Berkeley's Standard Copyright and Disclaimer Notice:

Copyright ©20XX. The Regents of the University of California (Regents). All Rights Reserved. Permission to use, copy, modify, and distribute this software and its documentation for educational, research, and not-for-profit purposes, without fee and without a signed licensing agreement, is hereby granted, provided that the above copyright notice, this paragraph and the following two paragraphs appear in all copies, modifications, and distributions. Contact the Office of Technology Licensing, UC Berkeley, 2150 Shattuck Avenue, Suite 408, Berkeley, CA 94704-1362, otl@berkeley.edu, for commercial licensing opportunities.

IN NO EVENT SHALL REGENTS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF REGENTS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

REGENTS SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE AND ACCOMPANYING DOCUMENTATION, IF ANY, PROVIDED HEREUNDER IS PROVIDED "AS IS". REGENTS HAS NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

*Other Notes: Insert year software was first published as well as any subsequent years when a modified version is published. Publication is defined in the U.S. Copyright Act as the distribution or offer of distribution of a work to the public by sale or other transfer of ownership or by rental, lease, or lending. Since some keyboards or fonts cannot reproduce the © symbol, the symbol (c) may be used instead, although the latter will not always be accepted as a substitute for the former. Use of the symbol "©" in combination with certain other requirements affords copyright protection in some foreign countries.

Software Disclosure FAQs

collapse all expand all

What protection does copyright offer?

Copyright, a form of intellectual property law, protects the expression of original ideas, but not the ideas themselves.

Copyright protects original works of authorship, such as software source code, manuals, survey instruments, and videos, when they are fixed in a tangible medium of expression. Copyright does not protect facts, ideas, systems, or methods of operation, although it may protect the way these things are expressed.

Copyright gives a copyright holder exclusive rights in some uses of the copyrighted work....

Who is an author of software?

The "author" of software is generally the original creator or creators of the code (note that a piece of software may have several different authors). The author(s) own(s) the copyright in the program. Under U.S. Copyright Law, when software is created in the course of the creator's employment, however, the employing institution (such as a company or academic institution) is considered the "author" of the code for copyright purposes under the "work made for hire" doctrine. This means that the institution owns the copyright, rather than the individual creator(s). Consistent with U.S....

What is the difference between patenting and copyrighting software?

Patents and copyrights are two different types of intellectual property rights. U.S. patent law gives the patent holder the right to prevent others from making, using, selling or importing a program that performs the same function or process as the patented software, even if the code is entirely different from the patented software, whereas copyright law protects only the code as it is written. It is possible to protect some software under both copyright and patent law. Another significant difference between patent and copyright for software is in the definition of an inventor versus...

Who owns software that I have developed while working at the University?

Under the UC Copyright policy, with some exceptions called out in the policy, the University owns software that is produced by its employees in the course and scope of their employment, and software that is produced with the use of University facilities or funds, and software that is produced by or through the University in the performance of a written agreement between the University and a sponsor. Software that embodies a patentable invention is also subject to the UC Patent Policy. For software governed by both policies, the UC Patent Policy takes precedence.

Which laws and University policies govern the disclosure and release of software?

Primarily, software is governed by the UC Copyright Policy (and any local copyright policies implemented by the campus) and the UC Patent Policy. The UC Copyright Policy specifies ownership of various categories of copyrighted works and provides for the sharing of licensing revenues received by the University with the authors of copyrighted works as determined by local campus policies. Under the UC Patent Policy, as a condition of their employment, employees agree to disclose potentially patentable inventions made during the term of their employment, and to assign their rights to the...

What if a visiting scientist develops some code?

The UC Copyright Policy provides that the University owns software developed using University resources, funds and facilities. If the software embodies a patentable invention, there may be additional ownership issues to consider.

Do I need to disclosure the software I have developed to the OTL? If so, why?

Software should be disclosed to OTL before it is distributed outside the University, so that the University can determine under which conditions the software may be legally distributed. Also, disclosure may be required by the contract under which the software was developed, or may be required by a co-owner of the software. Software that embodies a patentable invention may have additional disclosure requirements under federal statute or under the development contract that funded the creation of the software.

How do I disclose software?

Software is disclosed by submitting to the Berkeley IPIRA Office of Technology Licensing a brief description of the software along with information about the authors and sources of sponsorship utilized in creating the software, related software such as underlying works and derivative works, and an indication of how the authors would like to release the software. This disclosure may be downloaded from the IPIRA web site.

How does the OTL evaluate software disclosures?

OTL works with the authors to determine ownership and third party rights, and to evaluate the software for commercial value and the most appropriate form of distribution and intellectual property protection. Determination of ownership and rights involves sorting out authors from other contributors, determining the employment status of the authors and contributors, establishing whether works are "works made for hire" or made through independent effort, and considering whether a work is a joint work, a compilation, a derivative work or uses pre-existing content owned by others. OTL...

Which types of licensing models can I use to distribute the software I have developed at Berkeley?

There are many different types of licenses that can be used to release software, depending on the form in which the code is being released (source or object), what rights the licensee will have in the software, and whether the software is protected by patent as well as copyright. Options include licenses that allow commercial use, licenses that allow only non-commercial or academic use, open source licenses, and many others. The OTL can work with the authors/inventors to determine the licensing program that best meets your needs.

If I want to release software under an open source license, how long will the OTL evaluation take?

If the software disclosure indicates the authors' preference for a specific form of distribution, such as distribution under an open source license, the University's evaluation of the software would consist primarily of determining third party rights, the most appropriate form of intellectual property protection, whether the software can legally be distributed as requested by the authors, and obtaining concurrence of any co-owners of the software. If the distribution method affects the authors' right to a share of revenue in accordance with campus policies, OTL needs to confirm the...

Can software be released under more than one type of license? When would this be a good idea?

Software may be released simultaneously under several different types of licenses. For example, software may be released as object code for one purpose and as source code for another application, or may be released at one fee for commercial users and at a reduced fee or for no charge under a license that allows only academic use. Some sections of the code could be released under an open source license and the entire code under a traditional proprietary license. Software may be licensed to one user for internal use only, but a license to another user may allow external distribution of...

If the University licenses software to a company, will I still be able to use it in research?

Yes. All commercial licenses reserve to University researchers the right to continue using the licensed software authored while employed by the University and subject to UC Copyright Policy for research and educational purposes.

What are some open source licenses that are commonly used by the UCB community, and where can I obtain a copy?

Different types of projects may favor different kinds of open source licenses. You may want to check with others in your department or field of study to find out what types are commonly used. If you are planning to release software into an existing collaborative project, you may find that a license has already been chosen. If this is the case, it is a good idea to check with the OTL before committing to the project. The OTL can work with you to help you choose an appropriate open source license and provide you with an example of the open source license document. Some licenses that...

What is open source software?

Open source is a term that loosely describes software that is licensed under terms that allow the user of the software to look at the source code and modify it, and to distribute the modifications. Beyond these general characteristics, open source licenses vary widely in their requirements. Some open source licenses (for example, the BSD license) allow modifications to be kept proprietary; some (such as the General Public License, or...

I have developed some software and would like to release it under an open source software license. How can I do this?

Fill out the software disclosure form. Please indicate the type of open source license under which you want to release your software. The academic license commonly used at Berkeley may be viewed. The OTL will work to quickly determine any possible encumbrances and will work with you to release the software under your chosen license or another appropriate license that meets your goals. Please make sure, however, that all authors of the software sign the completed form before submitting it to the OTL. If you are planning to release software into an existing collaborative project, you...

My research group will be starting a software development project soon. Should we talk to OTL before we start the project?

Yes, it is a good idea to make certain arrangements beforehand if you plan to use a particular distribution model to ensure your ability to easily distribute the code in a manner consistent with your goals for the project. For example, if you plan to distribute under a license that will preclude authors from realizing their right to share potential revenue from licensing the resulting software, then the project needs the informed participation of all authors and concurrence of any other owners. OTL can work with you to obtain the informed participation and concurrence. OTL...

My research group is planning to release some or all of our work under an open source license. Should we talk to OTL before we start the project?

Yes, this is a good idea, just as it is with any software development project. For open source licensing plans, in particular, it will be important to determine whether you need informed consent from all UCB authors and to check for conflicting license terms. In addition, it is important to understand the open source licensing model you have chosen, as the licenses vary widely in their implications and may force you and future project participants to accept certain obligations regarding the use and distribution of any modification to the code. The OTL can help you answer questions...