![[Unicode]](https://www.unicode.org/webscripts/logo60s2.gif)
The Unicode Consortium’s mission is to enable people around the world to use computers in any language. Our freely-available specifications and data form the foundation for software internationalization in all major operating systems, browsers, search engines, applications, and the World Wide Web.
In support of this mission, the Consortium has adopted terms of use and a single outbound license that are intended to make the Consortium’s standards, specifications, documentation, data, and software as widely and freely available as reasonably possible while protecting the integrity of these products. All Consortium standards, specifications, documentation, data, and software are generally covered by the Unicode Copyright & Terms of Use. Additionally, the Consortium’s data files and software are globally and freely licensed under the Unicode License, also known as the Unicode Inc. License Agreement - Data Files & Software. These two documents should be read together to ensure an understanding of how the Consortium makes its various products available for use.
The Unicode® Standard is generally made available for use under the Unicode Copyright & Terms of Use, but each version of the Standard has further specifications of rights and restrictions on use, and these further specifications and restrictions should be consulted for each specific version of the Standard. For further information regarding the Standard and its versions, please refer to About the Unicode Standard.
In addition, the Unicode Code Charts are made available under their own specific and narrow terms and conditions, which may be found on each individual code chart. As a general rule, code charts may be freely used only for personal or internal business uses and may not be incorporated either wholly or in part into any product or publication, or otherwise be distributed without express written permission from the Unicode Consortium. (Linking to code charts is generally permitted.) Moreover, the fonts and font data used in production of code charts are generally used by the Consortium under narrow license from the font owner(s) and accordingly may not be extracted, or used in any other way by others in any product or publication, without permission or license granted by the font owner(s). Please consult the specific terms and conditions on each code chart for the specific restrictions and permitted uses for that code chart.
The Unicode Consortium’s data files and software are globally and freely licensed under the Unicode License, also known as the Unicode Inc. License Agreement - Data Files & Software. The Unicode License is a free and open source permissive license based on the MIT License. The primary difference between the MIT License and the Unicode License is that the Unicode License expressly covers data and data files. The Unicode License was approved by the Open Source Initiative (OSI) in 2018. The Unicode License should be read in conjunction with the Unicode Copyright and Terms of Use.
The Unicode Consortium’s intellectual property and technical contribution policies are informed by the Consortium’s mission and its commitment to making the Consortium’s standards, specifications, data, and software as widely and freely available as reasonably possible.
Accordingly, the Consortium requires contributors to its standards, specifications, data, and software to license (or in some cases assign) to the Consortium any intellectual property rights they may have in their contributions, so as to allow the Consortium to make those contributions freely available under the Unicode Terms of Use and/or the Unicode License, as appropriate. The Consortium has several different agreements and policies under which contributions are made, as set forth in further detail below.
Contributors to our large data and software projects, namely, CLDR, ICU, and ICU4X, are generally required to contribute under a contributor license agreement (CLA). The Unicode CLAs are license agreements that ensure that a contributor retains ownership of any intellectual property rights in their contribution while granting the Unicode Consortium the necessary legal rights to use and redistribute that contribution in the various Consortium projects.
The latest and current Unicode CLAs are based on the Apache Software Foundation's CLAs, which are well-known in the industry and widely adopted by many respected open source projects. The primary difference between the Apache CLAs and the Unicode CLAs is that the Unicode CLAs explicitly cover contributions of data as well as code.
There are two versions of the CLA, the Unicode Corporate CLA and the Unicode Individual CLA. Which version needs to be signed depends on who owns the contribution being made: the individual making the contribution or the contributor’s employer. It is the contributor's responsibility to know (or determine) whether or not their contribution is or may be owned by their employer.
(For further guidance on how to execute a Unicode CLA so that you may contribute to CLDR, ICU, and/or ICU4X, please refer to the section below regarding How to Sign a Unicode CLA.)
Those who submit a proposal for a new emoji do so in accordance with the Guidelines for Submitting Emoji Proposals and pursuant to the Unicode Emoji Proposal Agreement & License, which grants to the Consortium a broad license to any intellectual property rights in the proposed emoji.
Those who contribute a font for characters to be encoded or a font otherwise intended to be used in a publication of the Unicode Consortium do so under the Unicode Font Submission Policy and pursuant to a Grant of Font License.
Certain contributions may be made from time to time under bespoke grant agreements or independent contracts.
If you wish to contribute to one or more of the Unicode Consortium’s data and software projects, namely CLDR, ICU, and/or ICU4X, you will need to sign a Unicode CLA. This can generally be done directly in the Unicode GitHub repositories following the instructions found there.
There are two versions of the Unicode CLA, the Unicode Corporate CLA and the Unicode Individual CLA. Which version needs to be signed depends on who owns the contribution being made, the individual making the contribution or the contributor’s employer. It is the contributor's responsibility to know (or determine) whether or not their contribution is or may be owned by their employer.
The Unicode Corporate CLA should be signed by your employer if you are not self-employed but rather employed by a company that does or may have rights in your contributions. In many jurisdictions/situations, employers retain intellectual property rights for works produced by their employees. Thus, it is important that your employer sign the Corporate CLA to ensure that Unicode has the appropriate permissions to use your contribution. To check if your employer has already signed the Unicode Corporate CLA, please refer to this list of corporate signatories or contact member-services@unicode.org.
You should sign the Unicode Individual CLA if you are an individual or are self-employed, e.g., a sole proprietor or you have your own business.
If you are unsure which CLA to sign, please first discuss this question with your employer to determine whether your employer has rights in your contributions and consents to your making contributions to the Unicode Consortium. Your manager and/or your company’s open source compliance or legal department should be able to advise you as to the steps required by your company. This is your legal responsibility and it is important to protect you, your employer, and the Unicode Consortium. If you have further questions, please contact member-services@unicode.org.
If a Corporate CLA is needed, it cannot be signed in GitHub. You will need to arrange for your employer to sign the Corporate CLA by contacting member-services@unicode.org. The Corporate CLA must be signed by someone with signing authority for the corporation (typically a director, vice president, or higher), and must also be reviewed by the Unicode Consortium legal counsel. Therefore, corporate CLAs may take some time to process.
If a contributor has been contributing under a Corporate CLA but then changes employment status, they will need to stop contributing until a new CLA is signed covering their contributions. If this describes your situation, you should first notify Unicode immediately with the date your employment ends so you can be deleted from your prior CLA. If you wish to continue contributing you will need to put a new CLA in place. If you have become self-employed you should personally sign the Individual CLA, or if you have a new employer, you will need to ensure that your new employer has signed the Corporate CLA and that you are covered by it. To start this process, email member-services@unicode.org.
