Product Family Applicable License Restrictions Sample Clauses

Product Family Applicable License Restrictions. The following license restrictions apply in addition to those set forth in section 1.2.3 (Restrictions):
AutoNDA by SimpleDocs
Product Family Applicable License Restrictions. The following license restrictions apply in addition to those set forth in section 1.2.4 (Restrictions): 3.3.1. Internal Use; No Affiliate Use. Your use of the Product and Documentation is limited to internal use within your company. The Product and Documentation may not be used by your Affiliates unless specifically authorized in the Order. Use will be in accordance with this EULA and any additional terms, if any, set out in any Order or additional agreement executed by us and you in connection with this EULA which specifically states the terms thereof will be in addition to or in lieu of any of the terms set out in this XXXX (each a “License Addendum” and collectively, the “ License Addenda”).

Related to Product Family Applicable License Restrictions

  • License Restrictions Licensor reserves all rights not expressly granted to You. The Software is licensed for Your internal use only. Except as this Agreement expressly allows, You may not (1) copy (except for back-up purposes), modify, alter, create derivative works, reverse engineer, decompile, or disassemble the Software except and only to the extent expressly permitted by applicable law; (2) transfer, assign, pledge, rent, timeshare, host or lease the Software, or sublicense any of Your license grants or rights under this Agreement; in whole or in part, without prior written permission of Licensor; (3) remove any patent, trademark, copyright, trade secret or other proprietary notices or labels on the Software or its documentation; or (4) disclose the results of any performance, functional or other evaluation or benchmarking of the Software to any third party without the prior written permission of Licensor. Hosting Restrictions. In the event that You desire to have a third party manage, host (either remotely or virtually) or use the Software on Your behalf, You shall (1) first enter into a valid and binding agreement with such third party that contains terms and conditions to protect Licensor’s rights in the Software that are no less prohibitive and/or restrictive than those contained in this Agreement, including, without limitation, the Verification section below; (2) prohibit use by such third party except for the sole benefit of You; and (3) be solely responsible to Licensor for any and all breaches of the above terms and conditions by such third party.

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.

  • License Terms This license is for one full Semester. It cannot be cancelled or terminated except under the conditions cited in this license.

  • Sublicense Requirements Any Sublicense: (A) is subject to this Agreement; (B) will reflect that any sublicensee will not further sublicense; (C) will prohibit sublicensee from paying royalties to an escrow or other similar account; (D) will expressly include the provisions of Sections 8, 9, and 10 for the benefit of Stanford; and (E) will include the provisions of Section 4.4 and require the transfer of all the sublicensee’s obligations to *****, including the payment of royalties specified in the Sublicense, to Stanford or its designee, if this Agreement is terminated. If the sublicensee is a spin-out from *****, ***** must guarantee the sublicensee’s performance with respect to the payment of Stanford’s share of Sublicense royalties.

  • 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.

  • Xxxxx of License; Limitations The Engineer is granted a limited revocable non-exclusive license to use the registered TxDOT trademark logo (TxDOT Flying “T”) on any deliverables prepared under this contract that are the property of the State. The Engineer may not make any use of the registered TxDOT trademark logo on any other materials or documents unless it first submits that request in writing to the State and receives approval for the proposed use. The Engineer agrees that it shall not alter, modify, dilute, or otherwise misuse the registered TxDOT trademark logo or bring it into disrepute.

  • Xxxxxxx Xxxxxxx Restrictions/Market Abuse Laws The Participant acknowledges that, depending on his or her country, the broker’s country, or the country in which the Shares are listed, the Participant may be subject to xxxxxxx xxxxxxx restrictions and/or market abuse laws in applicable jurisdictions, which may affect his or her ability to accept, acquire, sell, or attempt to sell or otherwise dispose of Shares or rights to Shares (e.g., Restricted Share Units), or rights linked to the value of Shares, during such times as he or she is considered to have “inside information” regarding the Company (as defined by applicable laws or regulations in the applicable jurisdictions, including the United States and the Participant’s country). Local xxxxxxx xxxxxxx laws and regulations may prohibit the cancellation or amendment of orders the Participant placed before possessing inside information. Furthermore, the Participant may be prohibited from (i) disclosing the inside information to any third party, including fellow employees (other than on a “need to know” basis) and (ii) “tipping” third parties or causing them to otherwise buy or sell securities. Any restrictions under these laws or regulations are separate from and in addition to any restrictions that may be imposed under any applicable Company xxxxxxx xxxxxxx policy. The Participant acknowledges that it is his or her responsibility to comply with any applicable restrictions, and the Participant should consult his or her personal advisor on this matter.

  • SOFTWARE LICENSE GRANT Where Product is acquired on a licensed basis the following shall constitute the license grant:

  • Sublicense Rights Licensee shall not have the right to grant sublicenses under the licenses granted to it under Section 2.1(a) (Development and Commercialization License to Licensee) and Section 6.3(d) (Use of Coherus Trademark), without the prior written consent of Coherus, which consent may be withheld [***], except with respect to [***], in which case [***]. For the avoidance of doubt, it shall be [***] with respect to [***]. If Coherus consents in writing to allow Licensee to grant a sublicense, then Licensee may grant such sublicense, through [***], subject to the following: (a) each Sublicensee shall agree to be bound by all of the applicable terms and conditions of this Agreement; (b) the terms of each sublicense granted by Licensee shall provide that the Sublicensee shall be subject to the terms and conditions of this Agreement; (c) Licensee’s grant of any sublicense shall not relieve Licensee from any of its obligations under this Agreement; (d) Licensee shall be liable for any breach of a sublicense by a Sublicensee to the extent that such breach would constitute a breach of this Agreement, and any breach of the sublicense by such Sublicensee shall be deemed a breach of this Agreement by Licensee to the extent that such breach would constitute a breach of this Agreement as if Licensee had committed such breach; provided, however, that in each instance of any breach, Licensee and/or Sublicensee shall have the right to cure any such breach pursuant to the terms of this Agreement; and (e) Licensee will notify Coherus of the identity of any Sublicensee, and the territory in which it has granted such sublicense, promptly after entering into any sublicense. Notwithstanding anything to the contrary in this Agreement, for clarity, Licensee shall not have the right to grant sublicenses under Section 2.1 (License Grants) to any Third Party to Manufacture Products or to conduct Process Development.

  • Minimum Vendor License Requirements Vendor shall maintain, in current status, all federal, state, and local licenses, bonds and permits required for the operation of the business conducted by Vendor. Vendor shall remain fully informed of and in compliance with all ordinances and regulations pertaining to the lawful provision of goods or services under the TIPS Agreement. TIPS and TIPS Members reserve the right to stop work and/or cancel a TIPS Sale or terminate this or any TIPS Sale Supplemental Agreement involving Vendor if Vendor’s license(s) required to perform under this Agreement or under the specific TIPS Sale have expired, lapsed, are suspended or terminated subject to a 30‐day cure period unless prohibited by applicable statue or regulation.

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