DATA RECIPIENT OBLIGATIONS Sample Clauses

DATA RECIPIENT OBLIGATIONS. The obligations of this Section 3.0 apply to a Participant that is a Data Recipient. These obligations do not apply to a Participant that will not have access to the Data in the ICare System.
Sample 1Sample 2
AutoNDA by SimpleDocs
DATA RECIPIENT OBLIGATIONS. 5.1 As a condition of receiving the Data for carrying out the Purpose set forth above and as authorized under this Agreement, BCSH agrees to comply with applicable federal and state privacy and security laws, including, but not limited to, the California Information Practices Act of 1977 (Civ. Code, § 1798 et seq.). In addition, BCSH agrees to comply with relevant state and federal standards addressing the gathering, use and protection of personal data and information, including the 2004 HMIS Data and Technical Standards Final Notice issued by HUD and the State of California Information Security Policies, Standards and Procedures (Outlined in State Administrative Manual Chapter 5300).
Sample 1
DATA RECIPIENT OBLIGATIONS. 5.1 As a condition of receiving the Data for carrying out the Purpose set forth above and as authorized under this Agreement, THN agrees to comply with applicable federal and state privacy and security laws, including, but not limited to, the Texas Public Information Act3. In addition, THN agrees to comply with relevant state and federal standards addressing the gathering, use, and protection of personal data and information, including the 2004 HMIS Data and Technical Standards Final Notice issued by HUD and the Texas Public Information Act.
Sample 1
DATA RECIPIENT OBLIGATIONS. 6.1 The Requesting Agency shall:
Sample 1
DATA RECIPIENT OBLIGATIONS. The obligations of this Section 3.0 apply to Participant if either the "Both" or the "Data Recipient" line is checked on summary page of the Agreement. These obligations do not apply to Participants who have only checked the "Data Supplier" line on the summary page of the Agreement, as those Participants will not have access to the Data in the Exchange.
Sample 1
DATA RECIPIENT OBLIGATIONS. The obligations set forth in this Section 3 of this Exhibit A shall apply to Participant that is a “Data Recipient” as described on the Summary pages of this Agreement. The obligations set forth in this Section 3 of this Exhibit A shall not apply to Participants that is a “Data Supplier” as described on the Summary pages of this Agreement, as those Participants will not have access to the Data in the Exchange.
Sample 1
DATA RECIPIENT OBLIGATIONS 
Sample 1
AutoNDA by SimpleDocs

Related to DATA RECIPIENT OBLIGATIONS

  • Recipient Obligations 2.1 The Recipient agrees to support the Project in accordance with this Agreement.

  • Client Obligations 3.1 The Client shall:

  • PROCUREMENT OBLIGATIONS Notwithstanding any other provisions of this Part B, where in this Part B the Customer accepts an obligation to procure that a Former Supplier does or does not do something, such obligation shall be limited so that it extends only to the extent that the Customer's contract with the Former Supplier contains a contractual right in that regard which the Customer may enforce, or otherwise so that it requires only that the Customer must use reasonable endeavours to procure that the Former Supplier does or does not act accordingly.

  • STUDENT OBLIGATIONS The student agrees to use the property as his or her personal residence. The student shall maintain the interior of the property in a reasonably clean and safe condition, use reasonable care in consumption of utilities and services furnished by the landlord, and avoid unreasonable noise or other disruption of the privacy and peaceful enjoyment of the premises by the landlord and other students. The student shall be responsible for any damage to the property beyond reasonable wear and tear by the student, members of the student's family, or persons invited on the property by the student. The student shall not make, or cause to be made, any alterations to the property or its contents without first obtaining the written consent of the landlord. The student agrees to notify the landlord in writing about any needed repairs or violations of the Honor Code or Residential Living Standards involving other students or residents. *The BYU Student agrees to update their residential address on myBYU each semester/term, failure to do so will result in non-compliance fees of up to $175 and housing holds affecting their ability to register.

  • NO GOVERNMENT OBLIGATION TO THIRD PARTIES (1) The Department and Contractor acknowledge and agree that, notwithstanding any concurrence by the Federal Government in or approval of the solicitation or award of the underlying contract, absent the express written consent by the Federal Government, the Federal Government is not a party to this contract and shall not be subject to any obligations or liabilities to the Department, Contractor, or any other party (whether or not a party to that contract) pertaining to any matter resulting from the underlying contract.

  • Merchant Obligations (1) Merchant shall provide a valid, working administrative email address on enrolment. Any changes to Merchant’s account must be made via the administrative email address provided upon enrolment. The security of Merchant’s account is dependent in part upon Merchant maintaining the security of such administrative email address. Merchant shall be fully and solely responsible for any unauthorized changes to Merchant’s account via this email address. (2) Merchant will be given an ID code and password to allow Merchant to have access to Gateway Services. Merchant shall be fully and solely responsible for the establishment and maintenance of procedures to insure the control and confidentiality of identification codes and passwords and other access procedures (“Codes”). FAILURE TO PROTECT THE CODES MAY ALLOW UNAUTHORIZED PARTIES TO ACCESS THE GATEWAY SERVICES. Merchant is required to put in place internal procedures to limit such risk, including, but not limited to (a) changing the password at least once every 120 calendar days; (b) keeping every identification code under secure conditions; and (c) not keeping, in any form or in any place, any list of passwords. Merchant agrees to comply with any access or identification procedures and security protocols established from time to time by ISO, and if Merchant believes that any Code or security procedures has or may have become known by an unauthorized person (whether employed by Merchant or not), Merchant shall immediately notify ISO by telephone and confirm to ISO in writing such oral notification within 24 hours.

  • Interconnection Customer Obligations The Interconnection Customer shall maintain the Large Generating Facility and the Interconnection Customer’s Interconnection Facilities in a safe and reliable manner and in accordance with this LGIA.

  • Independent Obligations The Guarantor acknowledges that its obligations hereunder are independent of the obligations of the Issuer with respect to the Capital Securities and that the Guarantor shall be liable as principal and as debtor hereunder to make Guarantee Payments pursuant to the terms of this Guarantee notwithstanding the occurrence of any event referred to in subsections (a) through (g), inclusive, of Section 4.3 hereof.

  • Local Church’s Payment Obligations At Closing or otherwise prior to or on the Disaffiliation Date, Local Church shall pay to the Annual Conference, in a manner specified by Annual Conference, the following:

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