CONTRACTOR OBLIGATION Contractor shall identify and mark the precise portion(s) of the relevant page(s) of any records provided to Enterprise Services that Contractor believes are statutorily exempt from disclosure and identify the precise statutory basis for exemption from disclosure. In addition, if, in Contractor’s judgment, certain portions of such records are not statutorily exempt from disclosure but are sensitive because particular portions of Contractor’s records (NOT including pricing) include highly confidential, proprietary, or trade secret information (or the equivalent) that Contractor protects through the regular use of confidentiality or similar agreements and routine enforcements through court enforcement actions, Contractor shall identify and mark the precise portion(s) of the relevant page(s) of any records that include such sensitive information.
Security Rule Obligations The following provisions of this section apply to the extent that Business Associate creates, receives, maintains or transmits Electronic PHI on behalf of Covered Entity.
Contractor Obligations The Contractor is responsible for fully meeting all Contract obligations set forth in the OGS Centralized Contract and for providing services in accordance with the Contract and any Authorized User Agreement, Statement of Work or Purchase Order.
Processor Obligations 4.1 The Processor may collect, process or use Personal Data only within the scope of this DPA.
Client Obligations 3.1 The Client shall:
Customer Obligations Customer shall:
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.
On-Site Obligations If Red Hat personnel are working on Client’s premises (a) Client will provide a safe and secure working environment for Red Hat personnel, and (b) Red Hat will comply with all reasonable workplace safety and security standards and policies, applicable to Client’s employees, of which Red Hat is notified in writing by Client in advance.
Supplier Obligations At all times during the Term, the Supplier is required to:
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.
