INTERCHANGE OF DATA Clause Samples

The INTERCHANGE OF DATA clause governs the exchange of information between parties involved in an agreement. It typically outlines the methods, formats, and protocols for sharing data, such as requiring electronic transmission or specifying secure channels for sensitive information. This clause ensures that both parties have clear expectations regarding how data will be communicated, thereby reducing misunderstandings and promoting efficient, secure collaboration.
INTERCHANGE OF DATA. All technical data in regard to the PROJECT existing in the office of the STATE or existing in the offices of the CONSULTANT shall be made available to the other party to this Agreement without expense to such other party.
INTERCHANGE OF DATA. All technical data in regard to the Project whether existing in the office of the Commissioner, or existing in the office of the Consultant, shall be made available to the other party to this Agreement without expense to such other party, as the case may be. This may include but not necessarily be limited to reference drawings, notes, reports, etc.
INTERCHANGE OF DATA. All technical data in regard to the Project existing in the office of the Municipality or existing in the offices of the Consultant shall be made available to the other party to this Agreement without expense to such other party. The Municipality shall be responsible for, and the Consultant may rely upon, the accuracy and completeness of all reports, data, and other information furnished by the Municipality to the Consultant in connection with the Project. The Consultant may use such reports, data, and information in performing or furnishing services under this Agreement.
INTERCHANGE OF DATA. All technical data in regard to services provided under this Agreement by the Contractor whether existing in the offices of the Contractor or existing in the offices of the STATE shall be made available to the NYSDOT and NYSERDA without expense to such other party.

Related to INTERCHANGE OF DATA

  • Storage of Data The Company agrees to store and process the School District Data in a manner that is no less protective than those methods used to secure the Company’s own data. The Company agrees that School District Data will be stored on equipment or systems located within the United States.

  • Use of Data by User Registry Operator will permit user to use the zone file for lawful purposes; provided that (a) user takes all reasonable steps to protect against unauthorized access to and use and disclosure of the data and (b) under no circumstances will Registry Operator be required or permitted to allow user to use the data to, (i) allow, enable, or otherwise support the transmission by email, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than user’s own existing customers, or (ii) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator or any ICANN-­‐accredited registrar.

  • Use of Data (a) In connection with the provision of the services and the discharge of its other obligations under this Agreement, State Street (which term for purposes of this Section XXIX includes each of its parent company, branches and affiliates (''Affiliates")) may collect and store information regarding a Trust and share such information with its Affiliates, agents and service providers in order and to the extent reasonably necessary (i) to carry out the provision of services contemplated under this Agreement and other agreements between the Trusts and State Street or any of its Affiliates and (ii) to carry out management of its businesses, including, but not limited to, financial and operational management and reporting, risk management, legal and regulatory compliance and client service management.

  • Removal of Data County PHI or PI must not be removed from the premises of the Contractor except with express written permission of County.

  • Source of Data A description of (1) the process used to identify claims in the Population, and (2) the specific documentation relied upon by the IRO when performing the Quarterly Claims Review (e.g., medical records, physician orders, certificates of medical necessity, requisition forms, local medical review policies (including title and policy number), CMS program memoranda (including title and issuance number), Medicare contractor manual or bulletins (including issue and date), other policies, regulations, or directives).‌‌‌