Trade Data Sample Clauses

Trade DataRegistered Partner may locate ECCN (Export Control Classification Number), HTS (Harmonized Tariff Schedule), French DCSSI Authorization, Encryption Strength, Encryption Status and CCATS (Commodity Classification Automated Tracking System) number at the following URL: xxxx://xxxxx.xxxxx.xxx/legal/export/pepd/Xxxxxx.xx.
AutoNDA by SimpleDocs
Trade DataYou acknowledge that we own any and all trade data generated from the trading conducted by you with us (the “Trade Data”); subject to any and all rights or obligations under this Agreement, the Trade Data shall not be used in a manner that (a) allows access by a third party to any personally identifiable information about you or (b) is manifestly detrimental to any of your interests. We shall retain ownership of the Trade Data and may license the use thereof, in our sole discretion, to our Associates or to other persons. You will not acquire any such right, title or interest and to the extent that such right, title or interest therein first vests in you by operation of law or otherwise you hereby irrevocably and unconditionally assign to us throughout the world without reservation or encumbrance all such right, title and interest in and to all such Trade Data, and improvements to and modifications of them without the requirement of further payment.
Trade Data. Despite the efforts to remove barriers in trade with the CIS countries by creating a free-trade area, trade of the Kyrgyz Republic with these countries continued to decline significantly. At the same time, due to liberal trade and exchange systems of the Kyrgyz Republic, the Agreement did not have a diverting effect on trade with non-CIS countries. As the table below indicates, since the Agreement has become effective for the Kyrgyz Republic, trade with the CIS countries has dropped by 50.3 per cent, whereas, trade with non-CIS countries has increased by 32 per cent. 880,3 755,1 683,9 671,2 611,0 558,0 CIS countries Non CIS 462,8 442,5 1996 1998 1999 Consolidated data on intra-trade with the Parties to the Agreement and its breakdown by individual countries are represented in Annex II. 2 Effect of these duties on the coverage in trade with the Russian Federation and Uzbekistan in 1999 is shown in Annex I.
Trade Data. Under certain circumstances as more fully described below, certain Participants may receive from Cboe FI at approximately 10:00 p.m., Eastern Time (ET), on each trading day, certain post-trade Data in respect of the trading day which had ended at 5:00 p.m., ET the prior trading day. Generally, Participants which satisfy Cboe FI’s Liquidity Provider (“LP”) Standards (which are part of these Operating Procedures and described below) may receive, in Cboe FI’s sole determination, such post-trade Data. Cboe FI is under no obligation to send such Data to any such Participant and may discontinue to do so with respect to any or all Participants at any time. In the event that Cboe FI determines, in its sole discretion, to send such Data to certain Participants which are deemed by Cboe FI to be LPs as set forth above, such Data may include information on orders that such LP had interacted with during the trading day, such as (a) a list of all of the Transactions entered into on the Cboe FI Platform by the LP on such trading day, (b) a list of all orders sent to the LP on the Cboe FI Platform on such trading day which were rejected (or deemed to have been rejected) by such LP and which did not result in the consummation of a transaction, or (c) a list of volumes of such LP’s trading activity on the Platform in respect of a given day, and any such reports may also include such other post-trade Data as Cboe FI may determine in its discretion. In all cases, the counterparty to such Transactions and the party sending such rejected orders shall be identified to the LP by way of a numeric identifier and shall not be identified by name or by any other personally identifiable information.
Trade Data. 10.1 Could the Parties provide an update to Appendices I and II to document L/7044, which show each Party's total exports and imports by destination? 10.2 Could some information be provided concerning MERCOSUR trade? For the last three years: - total trade between MERCOSUR countries and the rest of the world; - trade with LAIA countries; - trade among MERCOSUR countries. 10.3 How much preferential trade is there between the MERCOSUR countries and the LAIA countries?
Trade Data. The trade coverage of the Agreement in total trade between the Parties is as follows: Imports of Turkey from Hungary (1,000 US$) Total Trade Trade Covered % of Trade Covered 1995 69,904 65,041 93% 1996 94,412 64,895 69% 1997 106,508 100,125 94% 1995 46,106 42,634 92% 1996 56,912 50,168 88% 1997 68,854 59,002 86%
Trade DataNotwithstanding anything to the contrary herein, CT shall not (x) share any trade data of Customer with any other party or (y) use any trade data of Customer to make any trade decisions for itself or others and shall implement measures to prevent its Representatives or any other person that has access to such trade data from making any such trade decisions.
AutoNDA by SimpleDocs

Related to Trade Data

  • Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.

  • Customer Data 8.1 You, not bookinglab or JRNI, have sole responsibility for the entry, deletion, correction, accuracy, quality, integrity, legality, reliability, appropriateness, and right to use the Customer Data. bookinglab and JRNI is not responsible for any of the foregoing or for any destruction, damage, loss, or failure to store any Customer Data beyond its reasonable control or resulting from any failure in data transmission or operation of the Booking Service by you. 8.2 As of the MSA Start Date, JRNI is certified under ISO 27001 and shall maintain an information security program for the Services that complies with the ISO 27001 standards or such other standards as are substantially equivalent to ISO 27001. 8.3 If JRNI and/or bookinglab processes any Personal Data on your behalf when performing its obligations under this Agreement, the Parties acknowledge that you shall be the Data Controller and JRNI and/or bookinglab shall be a Data Processor and in any such case: (a) you shall ensure that you are entitled to transfer the relevant Customer Personal Data to JRNI and/or bookinglab so that they may lawfully use, process and transfer the Customer Personal Data in accordance with this Agreement on your behalf; (b) you shall ensure that the relevant third parties have been informed of, and have given their consent to, such use, processing, and transfer as required by all applicable Data Protection Laws; (c) each Party shall take appropriate technical and organisational measures against unauthorised or unlawful processing of the personal data or its accidental loss, destruction or damage; and (d) notwithstanding any other provision of this Agreement, but subject always to Appendix B(1) Data Protection and B(2) Data Processing Activities, nothing shall prevent JRNI or bookinglab from disclosing Customer Personal Data or Customer Data to their Group Companies, Affiliates and third party service providers as necessary to provide the Services in accordance with clause 3, and otherwise in order to comply with Applicable Law or at the request of a governmental, regulatory or supervisory authority. 8.4 From the MSA Start Date the Parties shall comply with Appendix B(1) Data Protection and Appendix B(2) Data Processing Activities 8.5 ensure that Customer Data and Personal Data deemed as a special category of Data under GDPR is not given to us in any form unless pre-agreed by us in writing 8.6 You are solely responsible and liable for any transfer of Customer Data made by you (or made by JRNI or bookinglab at your request) from the Booking Service to a third party and for ensuring that such transfer is in compliance with the Parties' obligations under the Data Protection Laws.

  • Subscriber Data Subscriber will timely supply Netgateway, in a form acceptable to Netgateway, with all data necessary for Netgateway to perform the ongoing services to be provided hereunder. It is the sole responsibility of Subscriber to insure the completeness and accuracy of such data.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Client Data The Subrecipient shall maintain client data demonstrating client eligibility for services provided. Such data shall include, but not be limited to, client name, address, income level or other basis for determining eligibility, and description of service provided. Such information shall be made available to Grantee monitors or their designees for review upon request.

  • Device Data We may share certain personal information and device-identifying technical data about you and your devices with third party service providers, who will compare and add device data and fraud data from and about you to a database of similar device and fraud information in order to provide fraud management and prevention services, which include but are not limited to identifying and blocking access to the applicable service or Web site by devices associated with fraudulent or abusive activity. Such information may be used by us and our third party service providers to provide similar fraud management and prevention services for services or Web sites not provided by us. We will not share with service providers any information that personally identifies the user of the applicable device.

  • Licensee Data Licensee acknowledges and agrees that Licensee will be solely responsible for backing-up, and taking all appropriate measures to protect and secure, Licensee Data. Licensee acknowledges that Nuix may make, store and maintain back up copies of Licensee Data, but is not obliged to do so. Nuix will not be liable for any loss or corruption of Licensee Data.

  • Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD 1.5.2 Response format:

  • Technical Data For the purpose of this Agreement, "TECHNICAL DATA" shall mean all information of the Company in written, graphic or tangible form relating to any and all products which are developed, formulated and/or manufactured by the Company, as such information exists as of the Effective Date or is developed by the Company during the term hereof.

  • Your Data Subject to the limited rights granted by You hereunder, We acquire no right, title or interest from You or Your licensors under this Agreement in or to Your Data, including any intellectual property rights therein.

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