Derived Data ATP White Label Licence Sample Clauses

Derived Data ATP White Label Licence. 4.9.1. Subject to the remainder of this section 4.9, the Customer may “white label” Derived Data ATP or related services to third parties (“White Label Clients”) allowing them to rebrand or change the “look and feel” of that Derived Data ATP so that it appears to the End Customers as if it is operated or managed by the White Label Client. 4.9.2. Before white labelling any Derived Data ATP, the Customer must first complete and send to the relevant Exchange (or procure that the White Label Client completes and sends to the relevant Exchange) an Alternative Trading Platform – White Label Licence Application Form available on the website: xxx.xxxxxxxxxxxxxxxxxxx.xxx. The Exchange may at its discretion approve such White Label Client by countersigning the relevant form. The Customer is only permitted to white label Derived Data ATP to White Label Clients approved by the relevant Exchange. 4.9.3. In addition to the fees specified in section 4.8, the Customer shall pay a fixed fee in respect of any Derived Data ATP provided to a White Label Client as specified in: (a) in respect of LSE Data, Schedule B, Section 1.11 (Category 11 – White Label ATP Licence Charge); and (b) in respect of Borsa Italiana Data, Schedule B, Section 6.13 (Category 13 - “White Label ATP Licence Charge”). 4.9.4. For the avoidance of doubt, distribution of any Data for the purposes of operating of a Raw Data ATP or white labelling any Raw Data ATP is only permitted subject to provisions regarding redistribution of Data and Service Facilitators provisions and the payment of the applicable Redistribution Licence Charges.
AutoNDA by SimpleDocs
Derived Data ATP White Label Licence. 4.9.1. Subject to the remainder of this section 4.9, the Customer may “white label” Derived Data ATP or related services to third parties (“White Label Clients”) allowing them to rebrand or change the “look and feel” of that Derived Data ATP so that it appears to the End Customers as if it is operated or managed by the White Label Client. 4.9.2. Before white labelling any Derived Data ATP, the Customer must first complete and send to the relevant Exchange (or procure that the White Label Client completes and sends to the relevant Exchange) an Alternative Trading Platform – White Label Licence Application Form available on the website: xxx.xxxxxxxxxxxxxxxxxxx.xxx. The Exchange may at its discretion approve such White Label Client by countersigning the relevant form. The Customer is only permitted to white label Derived Data ATP to White Label Clients approved by the relevant Exchange. 4.9.3. In addition to the fees specified in section 4.8, the Customer shall pay a fixed fee in respect of any Derived Data ATP provided to a White Label Client as specified in: (a) in respect of LSE Data, Schedule B, Section 1.12 (Category 12 – White Label ATP Licence Charge); and
Derived Data ATP White Label Licence. 4.6.1. Subject to the remainder of this section 4.6, the Customer may “white label” Derived Data ATP or related services to third parties (“White Label Clients”) allowing them to rebrand or change the “look and feel” of that Derived Data ATP so that it appears to the End Customers as if it is operated or managed by the White Label Client. 4.6.2. Before white labelling any Derived Data ATP, the Customer must first complete and send to BIT (or procure that the White Label Client completes and sends to BIT) an Alternative Trading Platform – White Label Licence Application Form available on the website: xxxxx://xxx.xxxxxxxxxxxxx.xx/borsaitaliana/information- services/pricing/pricing.htm. BIT may at its discretion approve such White Label Client by countersigning the relevant form. The Customer is only permitted to white label Derived Data ATP to White Label Clients approved by BIT. 4.6.3. In addition to the fees specified in section 4.5, the Customer shall pay a fixed fee in respect of any Derived Data ATP provided to a White Label Client as specified in Schedule B, Section 1.14 (Category 14 - “Derived Data ATP White Label Licence Charges”). 4.6.4. For the avoidance of doubt, distribution of any Data for the purposes of operating of a Raw Data ATP or white labelling any Raw Data ATP is only permitted subject to provisions regarding redistribution of Data and Service Facilitators provisions and the payment of the applicable Redistribution Licence Charges.

Related to Derived Data ATP White Label Licence

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

  • Third Party Products and Services Any third-party hardware, software and/or services that is delivered by ResMed for use either standalone or in conjunction with ResMed products and/or services, shall be subject to the third-party terms and conditions and/or license agreements between Customer and the third party. Such third-party hardware, software and/or services is provided by ResMed "AS IS," without any warranty of any kind. Any representations or warranties as to such hardware, software and/or services shall only be as granted by the applicable third parties, if any, that accompany such products and/or software and/or services. Any representations, warranties, or other similar obligations with respect to such third-party hardware, software and/or services flow directly from the third party to Customer and ResMed shall have no responsibility at all for any such representations, warranties, obligations or lack thereof.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work. 4.12.2 Product Data are illustrations, standard schedules, performance charts, instructions, brochures, diagrams and other information furnished by the Contractor to illustrate a material, product or system for some portion of the Work. 4.12.3 Samples are physical examples which illustrate materials, equipment or workmanship and establish standards by which the Work will be judged. 4.12.4 The Contractor shall review, approve and submit, with reasonable promptness and in such sequence as to cause no delay in the Work or in the work of the State or any separate contractor, all Shop Drawings, Product Data and Samples required by the Contract Documents. 4.12.5 By approving and submitting Shop Drawings, Product Data and Samples, the Contractor represents that he / she has determined and verified all materials, field measurements, and field construction criteria related thereto, or will do so, and that he / she has checked and coordinated the information contained within such submittals with the requirements of the Work and of the Contract Documents. 4.12.6 The Contractor shall not be relieved of responsibility for any deviation from the requirements of the Contract Documents by the Architect's approval of Shop Drawings, Product Data or Samples under Subparagraph 2.2.7 of these General Conditions unless the Contractor has specifically informed the Architect and the State in writing of such deviation at the time of sub- mission and the Architect and the State has given written approval to the specific deviation. The Contractor shall not be relieved from responsibility for errors or omissions in the Shop Drawings, Product Data or Samples by the Architect's approval thereof. 4.12.7 The Contractor shall direct specific attention, in writing or on resubmitted Shop Drawings, Product Data or Samples, to revisions other than those requested by the Architect on previous submittals. 4.12.8 No portion of the Work requiring submission of a Shop Drawing, Product Data or Sample shall be commenced until the submittal has been approved by the Architect as provided in Subparagraph 2.2.7 of these General Conditions. All such portions of the Work shall be in accordance with approved submittals.

  • SINGLE-USE PRODUCTS The Board of County Commissioners has established a single-use products and plastic bags policy intended to reduce the use of products which have become globally recognized as having lasting negative impacts on the environment. Neither single-use products nor plastic bags may be sold or disbursed on County property by staff or contracted vendors, except as set forth in Orange County Administrative Regulation 9.01.03. Failure to comply with the Regulation may result in termination of the contract or other contractual remedies, and may affect future contracting with the County. The use of reusable, recyclable, biodegradable, or compostable materials is encouraged.

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

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Third Party Products 12.1 Third-party products provided to you by NCR Voyix for use with your subscription to the Service are subject to any terms provided by their supplier, including but not limited to those terms and conditions set forth in the exhibits attached hereto. Third-party terms and conditions are subject to change at any time by the supplier, and you agree that your use of such third-party products and services is governed by such supplier’s terms and conditions. You hereby release NCR Voyix from any and all liability associated with any damages or claims arising out of or related to third-party products. UNLESS NCR Xxxxx SPECIFICALLY AGREES OTHERWISE IN WRITING, YOU ACKNOWLEDGE AND AGREE THAT SUCH THIRD-PARTY PRODUCTS ARE PROVIDED “AS-IS” WITHOUT A WARRANTY FROM NCR Voyix. ACCORDINGLY, NCR Voyix EXPRESSLY DISCLAIMS ALL WARRANTIES OF ANY NATURE WITH RESPECT TO ANY SUCH THIRD-PARTY PRODUCTS, WHETHER ORAL OR WRITTEN, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT OF ANY THIRD-PARTY RIGHTS. 12.2 Third-party products and services may be advertised or made available to you for purchase directly from their supplier by email or other electronic communications, including notifications made through the Service or the Account Portal. Any representations or warranties that may be provided in connection with any such third-party products or services are provided solely by their supplier. NCR Voyix will not be responsible for any of your dealings or interactions with any of those third-party suppliers.

  • Operator Materials Operator retains all right, title and interest in and to any and all of Operator’s software, materials, tools, forms, documentation, training and implementation materials and intellectual property (“Operator Materials”). Operator grants to the LEA a personal, nonexclusive license to use the Operator Materials for its own non-commercial, incidental use as set forth in the Service Agreement. Operator represents that it has all intellectual property rights necessary to enter into and perform its obligations in this DPA and the Service Agreement, warrants to the District that the District will have use of any intellectual property contemplated by the Service Agreement free and clear of claims of any nature by any third Party including, without limitation, copyright or patent infringement claims, and agrees to indemnify the District for any related claims.

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

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