Client Obligations Client shall fulfill its obligations and responsibilities as set forth in this Agreement and the SOW so that Spirent can perform the Services efficiently and effectively. Client is responsible for the operation and security of its applications and the information technology environment in which the Services are to be performed. Client agrees that it shall have the sole responsibility for protecting and backing up its systems, networks, applications, content, and data used in connection with the Services. Client shall secure and provide to Spirent any rights and licenses necessary to allow Spirent to perform the Services. Client shall ensure the cooperation and performance of its employees and contractors as well as the accuracy and completeness of data and information provided to Spirent that are necessary to perform the Services. Client shall make and be responsible for all decisions and actions based or related to advice and recommendations provided by Spirent in connection with the performance of the Services hereunder. Client shall be liable for all Spirent owned equipment while in Client’s possession or control and, if lost or. damaged or not returned to Spirent upon expiration of the engagement, Client agrees to pay for such equipment upon receipt of an invoice referencing this Agreement. Equipment received by Spirent from Client more than five (5) calendar days after the end of engagement shall be subject to a fifteen (15%) per month late fee based on the list price of the equipment.
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.
Joint Obligations A. The University and the student share the responsibility for ensuring the quality of life within the residence halls, their maintenance, furnishings and facilities, and for a physical environment secure from fire and other hazards. The University will work with students to promote effective security of persons and property in the residence halls.
Sub-processor Obligations MailChimp shall: (i) enter into a written agreement with the Sub-processor imposing data protection terms that require the Sub-processor to protect the Customer Data to the standard required by Data Protection Laws; and (ii) remain responsible for its compliance with the obligations of this DPA and for any acts or omissions of the Sub-processor that cause MailChimp to breach any of its obligations under this DPA.
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.
