Sublicense of Red Cross IP Within Program Materials Sample Clauses

Sublicense of Red Cross IP Within Program Materials. Company is granted a limited right to sublicense the Red Cross IP contained within the Program Materials under the terms and conditions hereof to its customers in the Program Channel whereby such customers desire to offer the Product to their own end-user corporate customers, as evidenced by their placing an order for the Product through Company’s standard ordering process. This limited sublicense to Program Channel customers is a non-exclusive, revocable (by Red Cross only), non-assignable, non-sublicensable, non- transferable license to use the Red Cross IP solely within the Program Materials. For the avoidance of doubt, Program Channel customers are only permitted to use the Product, Product Packaging and Program Materials approved by Red Cross and provided to them by Company. Company shall cause the Authorized Distributors to comply with this Section 4 and any other provisions hereof concerning the use of the Red Cross IP.
AutoNDA by SimpleDocs

Related to Sublicense of Red Cross IP Within Program Materials

  • Marking of Licensed Products To the extent commercially feasible and consistent with prevailing business practices, Company shall xxxx, and shall cause its Affiliates and Sublicensees to xxxx, all Licensed Products that are manufactured or sold under this Agreement with the number of each issued patent under the Patent Rights that applies to such Licensed Product.

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Licensed Technology (a) LICENSOR is not aware of any interference, infringement, misappropriation, or other conflict with any intellectual property rights of third parties, and LICENSOR has never received any charge, complaint, claim, demand, or notice alleging any such interference, infringement, misappropriation, or violation (including any claim that LICENSOR must license or refrain from using any intellectual property rights of any third party). To the knowledge of LICENSOR, no third party has interfered with, infringed upon, misappropriated, or otherwise come into conflict with any of the LICENSED TECHNOLOGY. (b) Exhibit A identifies each patent or registration which has been issued to LICENSOR with respect to any of the LICENSED TECHNOLOGY and identifies each pending patent application or application for registration which LICENSOR has made with respect to any of the LICENSED TECHNOLOGY. LICENSEE acknowledges that LICENSOR has previously made available to LICENSEE correct and complete copies of all such patents, registrations and applications (as amended to-date) in LICENSOR’s possession and has made available to LICENSEE correct and complete copies of all other written documentation in LICENSOR’s possession evidencing ownership and prosecution (if applicable) of each such item. (c) Exhibit A identifies each item of LICENSED TECHNOLOGY that is assigned to LICENSOR or that LICENSOR uses pursuant to license, sublicense, agreement, or permission. LICENSOR has made available to LICENSEE correct and complete copies of all such licenses, sublicenses, agreements, patent prosecution files and permissions (as amended to-date) in LICENSOR’s possession. With respect to each item of LICENSED TECHNOLOGY required to be identified in Exhibit A and to the knowledge of LICENSOR: (i) the license, sublicense, agreement, or permission covering the item is legal, valid, binding, enforceable, and in full force and effect; (ii) the license, sublicense, agreement, or permission will continue to be legal, valid, binding, enforceable, and in full force and effect on identical terms following the consummation of the transactions contemplated hereby; (iii) no Party to the license, sublicense, agreement, or permission is in breach or default, and no event has occurred which with notice or lapse of time would constitute a breach or default or permit termination, modification, or acceleration thereunder; (iv) no party to the license, sublicense, agreement, or permission has repudiated any provision thereof; (v) the underlying item of LICENSED TECHNOLOGY is not subject to any outstanding lien or encumbrance, injunction, judgment, order, decree, ruling, or charge; (vi) no action, suit, proceeding, hearing, investigation, charge, complaint, claim, or demand is pending or is threatened which challenges the legality, validity, or enforceability of the underlying item of LICENSED TECHNOLOGY; and (vii) except as provided in Exhibit A, LICENSOR has not granted any license or similar right to the LICENSED TECHNOLOGY within the GENERAL FIELD or PARTHENOGENESIS FIELD.

  • Existing Products Except as set forth below, Contractor shall retain all rights, title and interest in Existing Products.

  • Sublicense Agreements Sublicenses under this Section 2.3 shall be granted only pursuant to written agreements, which shall be subject to and consistent with the terms and conditions of this Agreement. Such Sublicense agreements shall contain, among other things, provisions to the following effect: 2.3.2.1 all provisions necessary to ensure Licensee’s ability to comply with Licensee’s obligation under or not violate the provisions of Sections 4.4, 4.5, 4.6, 5.1, 5.3, 5.4, 8.1 and 11.1; 2.3.2.2 a section substantially the same as Article 9 (Indemnification), which also shall state that the Indemnitees (as defined in Section 9.1) are intended third party beneficiaries of such Sublicense agreement for the purpose of enforcing such indemnification; 2.3.2.3 in the event of termination of the license set forth in Section 2.1.1 above (in whole or in part (e.g., termination of the license as to a Licensed Product or in a particular country)), any existing Sublicense shall terminate to the extent of such terminated license; provided, however, that, for each Sublicensee, upon termination of the license, if the Sublicensee is not then in breach of the Sublicense agreement such that Licensee would have the right to terminate such Sublicense agreement, such Sublicensee shall have the right to obtain a license from Harvard on the same terms and conditions as set forth herein, which shall not impose any representations, warranties, obligations or liabilities on Harvard that are not included in this Agreement, provided that (a) the scope of the license granted directly by Harvard to such Sublicensee shall be coextensive with the scope of the license granted by Licensee to such Sublicensee, (b) if the Sublicense granted to such Sublicensee was non-exclusive, such Sublicensee shall not have the right to participate in the prosecution or enforcement of the Patent Rights under the license granted to it directly by Harvard and (c) if there are more than one Sublicensee, each Sublicensee that is granted a direct license shall be responsible for a pro rata share of the reimbursement due under Section 6.2.3 of this Agreement (based on the number of direct licenses under the Patent Rights in effect on the date of reimbursement); 2.3.2.4 the Sublicensee shall only be entitled to sublicense its rights under such Sublicense agreement on the terms set forth in this Section 2.3; and 2.3.2.5 the Sublicensee shall not be entitled to assign the Sublicense agreement without the prior written consent of Harvard, except that Sublicensee may assign the Sublicense agreement to a successor in connection with the merger, consolidation or sale of all or substantially all of its assets or that portion of its business to which the Sublicense agreement relates; provided, however, that any permitted assignee agrees in writing in a manner reasonably satisfactory to Harvard to be bound by the terms of such Sublicense agreement.

  • Third Party Technology The Company makes use of third party technology to collect information required for traffic measurement, research, and analytics. Use of third party technology entails data collection. We therefore would like to inform clients the Company enables third parties to place or read cookies located on the browsers of users entering the Company’s domain. Said third parties may also use web beacons to collect information through advertising located on the Company’s web site. Please note that you may change your browser settings to refuse or disable Local Shared Objects and similar technologies; however, by doing so you may be disabling some of the functionality of Company’s services.

  • New Products You agree to comply with NASD Notice to Members 5-26 recommending best practices for reviewing new products.

  • Licensed Product The term “Licensed Product” shall mean any product (a) the manufacture, use, importation, sale or offer for sale of which would, in the absence of the license granted by this Agreement, infringe a Valid Claim of any of the Licensed Patent Rights, or (b) that is comprised of, utilizes or incorporates Licensed Biological Materials, or (c) that is discovered, developed or made using a Licensed Process.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!