Licensed Products Lessee will obtain no title to Licensed Products which will at all times remain the property of the owner of the Licensed Products. A license from the owner may be required and it is Lessee's responsibility to obtain any required license before the use of the Licensed Products. Lessee agrees to treat the Licensed Products as confidential information of the owner, to observe all copyright restrictions, and not to reproduce or sell the Licensed Products.
SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.
New Products You agree to comply with NASD Notice to Members 5-26 recommending best practices for reviewing new products.
Royalty Term On a country-by-country and Licensed Product-by-Licensed Product basis, royalty payments in the Territory shall commence upon the first commercial sale of such Licensed Product, whether such sale is to a Public Purchaser, Governmental Authority or private entity or person and whether such sale is made under an EUA or Key Approval, in such country in the Territory and will terminate upon the later of: (a) the expiration, invalidation or abandonment date of the last Valid Claim of the Patents in the country of sale or manufacture of such Licensed Product in the Territory or (b) expiration of regulatory exclusivity of such Licensed Product in such country of sale in the Territory (the “Royalty Term”).
Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.
API License If you are purchasing an application programming interface ("API") license, other than a Learn API as defined below, we grant you a limited, non-exclusive, revocable, non-sublicensable, non-transferable license to access each API set forth in the Order Form. The API(s) are provided in the form of a web service that enables a "connection" into our servers. We will provide you with the information necessary to enable your secure use of the API(s). You may not use or install the API(s) for any other purpose without our written consent, and may not copy, rent, adapt, disassemble, lease, assign, sublicense, reverse engineer, modify or decompile, the API(s) or any part thereof. We reserve the right to limit the number and/or frequency of API requests or take other actions necessary to protect the integrity of our services.
Licensee Licensee represents and warrants that:
Territory 43.1 This Agreement applies to the territory in which Verizon operates as an Incumbent Local Exchange Carrier in the Commonwealth of Pennsylvania. Verizon shall be obligated to provide Services under this Agreement only within this territory.
Developer License We grant you a non-assignable, non-sublicensable, non-exclusive, worldwide right and license for the number of Developer(s) indicated in the Order Form to install the Software on any number of Machines in order to internally use the Software to create, develop and test Applications. For clarity, a single Software license may be re-allocated to another Developer in the event that the original Developer is no longer employed by you or has been assigned to a new role where access to the Software will no longer be required on a permanent basis.
License Key 2.5. The Application Software may include an embedded security system which if provided must be used together with a license key. The license key may limit the use of the Application Software to the applicable Use Level and prevent a single User from using more than one workstation at the same time and is valid for a certain period of time following which the license key must be renewed. Customer is solely responsible for any cost or loss arising out of Customer’s failure or delay to renew the license key.
