Transferred Data Sample Clauses

The 'Transferred Data' clause defines the specific data that is being moved from one party to another under the agreement. It typically outlines the types or categories of data involved, such as personal information, business records, or technical files, and may specify the format or method of transfer. By clearly identifying what data is subject to the agreement, this clause ensures both parties understand their obligations and helps prevent disputes over the scope of data being transferred.
Transferred Data. If the Data Recipient: (a) wishes to access the Schedule 1 Data about: (i) a Child; or (ii) any Close Connection to the extent that the relevant Schedule 1 Data is identified as Schedule 1 Data applicable to a Close Connection; and (b) intends to use that Schedule 1 Data for a Permitted Purpose, then: (c) by entering into this Agreement, the Data Provider authorises the transfer, provided the Data Recipient is compliant with this Agreement; (d) the Data Recipient may initiate the transfer by the Digital Services Manager of that Schedule 1 Data from the Agency Database to the 360VoC Data Hub; (e) once that Schedule 1 Data is transferred to the 360VoC Data Hub, that Schedule 1 Data becomes Transferred Data for the purpose of this Agreement; and (f) the Transferred Data held in the 360VoC Data Hub will be displayed to Authorised Users in the 360VoC Application on and from the Go Live Date.
View SourceView Similar (4)
Transferred Data. 1.1 Each party may supply, licence or otherwise make available data to the other party pursuant to the terms of this Agreement and any Statement of Work. Such data shall be processed in accordance with the terms of this Agreement. 1.2 The Parties acknowledge that they are separate and independent data controllers. 1.3 The parties shall each comply with their respective obligations under the Data Protection Laws when processing data. 1.4 In respect of data supplied by the Customer to Equifax and Searches: 1.4.1 the Customer shall adopt ▇▇▇▇▇ into its terms of business or otherwise provide an appropriate written notification to data subjects setting out that:
View SourceView Similar (3)
Transferred Data. During the due diligence, BII has made available to CENTREXION a data package relating to Development Compounds including (i) all regulatory applications, submissions and approvals, and (ii) copies of pre-clinical and clinical data owned or controlled by BII. All Transferred Data shall be delivered to CENTREXION or its designee pursuant to the technology transfer agreement entered into by the parties as of the Effective Date (the “Tech Transfer Agreement”). Conditional solely upon receipt of all upfront payments by BII, BII hereby assigns and transfers to CENTREXION BII’s rights to all such documents, and CENTREXION accepts such assignment and transfer.
View SourceView Similar (2)
Transferred Data. In the event that Client transfers data from another service provider to Metavante to convert Client’s end users to Metavante’s systems, Metavante will not be responsible for any errors, delays, or problems in providing the Services that arise from the quality, reliability, or currency of the transferred data, including, without limitation, late fees for payments that are delayed due to the conversion of inaccurate or outdated payee data. In addition, Client shall reimburse Metavante, at Metavante’s then-current rates for professional services, for any additional work that Metavante must perform to address claims or support arising from errors or inadequacies of transferred data.
View SourceView Similar (2)
Transferred Data. The Parties acknowledge and agree that, notwithstanding Section 2.01(a), certain Transferred Data expressly identified in the Transition Services Agreement will be transferred to Purchaser following the Closing Date pursuant to and in accordance with the terms of the Transition Services Agreement.
View Source
Transferred Data. The Customer's data is communicated to our commercial partner Maxxton (19.4) and may be accessible at its office located in India as part of support operations. Maxxton formally guarantees the respect of an adequate level of protection recognised by the European Union within the framework of a dedicated agreement with Siblu France. With the exception of this case, the Customer's data is not intended to leave the European Union.
View Source

Related to Transferred Data

  • Buyer Data for all Defaults by the Supplier resulting in direct loss, destruction, corruption, degradation or damage to any Buyer Data, will not exceed the amount in the Order Form

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

  • Transferred Assets (i) From the Closing Date to the Effective Date, OLS sold and/or contributed, assigned, transferred, and conveyed to the Depositor, and the Depositor acquired from OLS, without recourse except as provided under the Original Receivables Sale Agreement, all of OLS’s right, title and interest, whether now owned or hereafter acquired, in, to and under each Receivable (1) in existence on the Closing Date and in existence on any Business Day after the Closing Date and prior to the Effective Date that is listed as a “Designated Servicing Agreement” on the Designated Servicing Agreement Schedule as of the date such Receivable is created (the “Initial Receivables”), and (2) all monies due or to become due and all amounts received or receivable with respect thereto and all proceeds (including “proceeds” as defined in the Uniform Commercial Code in effect in all applicable jurisdictions (the “UCC”)), together with all rights of OLS to enforce such Initial Receivables (collectively, the “Original Transferred Assets”). (ii) Commencing on the Effective Date, and until the opening of business on the MSR Transfer Date for each Designated Servicing Agreement, pursuant to the Purchase Agreement, OLS will sell to HLSS, for a cash purchase price equal to 100% of the Receivable Balances thereof, (1) each Receivable, in existence on any Business Day on or after the Effective Date and until the opening of business on the related MSR Transfer Date, that arises under any Servicing Agreement that is listed as a “Designated Servicing Agreement” on the Designated Servicing Agreement Schedule as of the date such Receivable is created (“OLS Additional Receivables”) for which the MSR Transfer Date has not yet occurred, and (2) all monies due or to become due and all amounts received or receivable with respect thereto and all proceeds (including “proceeds” as defined in the UCC), together with all rights of HLSS to enforce such OLS Additional Receivables (collectively, the “OLS Transferred Assets”). (iii) Commencing on the Effective Date, and until the close of business on the Receivables Sale Termination Date, subject to the provisions of this Agreement, HLSS, as receivables seller, hereby sells and/or contributes, assigns, transfers, and conveys to the Depositor, and the Depositor acquires from HLSS, without recourse except as provided herein, all of HLSS’s right, title and interest, whether now owned or hereafter acquired, in, to and under (1) each Receivable in existence on any Business Day on or after the Effective Date and prior to the Receivables Sale Termination Date (including the OLS Additional Receivables) that arises under any Servicing Agreement that is listed as a “Designated Servicing Agreement” on the Designated Servicing Agreement Schedule as of the date such Receivable is created (“Additional Receivables”), and (2) all monies due or to become due and all amounts received or receivable with respect thereto and all proceeds (including “proceeds” as defined in the UCC) (including the OLS Transferred Assets), together with all rights of HLSS to enforce such Additional Receivables (collectively, the “Transferred Assets”). Until the Receivables Sale Termination Date, HLSS shall, automatically and without any further action on its part, sell and/or contribute, assign, transfer and convey to the Depositor, on each Business Day, each Additional Receivable not previously transferred to the Depositor and the Depositor shall purchase each such Additional Receivable together with all of the other Transferred Assets related to such Receivable.

  • Transfer Timing (A) The final paragraph of Paragraph 3(a) shall be deleted and replaced with the following: “Subject to Paragraph 4, and unless otherwise specified, any transfer of Eligible Credit Support or Equivalent Credit Support (whether by the Transferor pursuant to Paragraph 2(a) or by the Transferee pursuant to Paragraph 2(b)) shall be made not later than the close of business on the Settlement Day.” (B) The definition of Settlement Day shall be deleted and replaced with the following: “Settlement Day” means the next Local Business Day after the Demand Date”.