Analyzed Data Clause Samples

The "Analyzed Data" clause defines how data that has been processed, interpreted, or derived from raw information is treated within an agreement. Typically, this clause clarifies ownership rights, usage permissions, and any restrictions related to data that results from analysis performed by one or both parties. For example, it may specify whether the party conducting the analysis retains exclusive rights to the insights generated, or if both parties can use the analyzed data for their own purposes. The core function of this clause is to prevent disputes by clearly allocating rights and responsibilities regarding the use and ownership of data that has been transformed through analysis.
POPULAR SAMPLE Copied 1 times
Analyzed Data. Notwithstanding anything in this Agreement, as between TRX and Siemens, TRX will own the results of all analyses using data and use information obtained or created pursuant to this Agreement or any Services, whether or not collected or aggregated by Siemens (“Analyzed Data”). Siemens may use such Analyzed Data solely for the purpose of providing Services to TRX and shall keep such Analyzed Data confidential pursuant to, and will use such Analyzed Data in accordance with, the confidentiality and privacy provisions of this Agreement.
View SourceView Similar (2)

Related to Analyzed Data

  • Covered Data All instances of "Student Data" should be replaced with "LEA Data". The protections provided within this DPA extend to all data provided to or collected by the Provider.

  • De-Identified Data Provider agrees not to attempt to re-identify de-identified Student Data. De-Identified Data may be used by the Provider for those purposes allowed under FERPA and the following purposes: (1) assisting the LEA or other governmental agencies in conducting research and other studies; and (2) research and development of the Provider's educational sites, services, or applications, and to demonstrate the effectiveness of the Services; and (3) for adaptive learning purpose and for customized student learning. Provider's use of De-Identified Data shall survive termination of this DPA or any request by ▇▇▇ to return or destroy Student Data. Except for Subprocessors, ▇▇▇▇▇▇▇▇ agrees not to transfer de- identified Student Data to any party unless (a) that party agrees in writing not to attempt re-identification, and (b) prior written notice has been given to the LEA who has provided prior written consent for such transfer. Prior to publishing any document that names the LEA explicitly or indirectly, the Provider shall obtain the LEA’s written approval of the manner in which de-identified data is presented.

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

  • Metering Data At Developer’s expense, the metered data shall be telemetered to one or more locations designated by Connecting Transmission Owner, Developer and NYISO. Such telemetered data shall be used, under normal operating conditions, as the official measurement of the amount of energy delivered from the Large Generating Facility to the Point of Interconnection.

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.