PROCESSOR SPECIFIC OBLIGATIONS Clause Samples

PROCESSOR SPECIFIC OBLIGATIONS. 3.1 Where IPSX processes Protected Data on behalf of the Counterparty, IPSX shall: 3.1.1. (and shall ensure that any person acting under its authority who has access to Protected Data) process the Protected Data only in accordance with IPSX’s Privacy Notice, the Agreement and this Appendix and Annex 1 (Data Processing Details) (which may be updated from time to time by written agreement of the parties), (“Processing Instructions”); and 3.1.2. immediately inform the Counterparty of any requirement under applicable law that would require IPSX to process the Protected Data other than only on the Processing Instructions, or if any Counterparty instruction does not comply with DP Laws.
PROCESSOR SPECIFIC OBLIGATIONS. 3.1 Where IPSX processes Protected Data on behalf of the Counterparty, IPSX shall: 3.1.1. (and shall ensure that any person acting under its authority who has access to Protected Data) process the Protected Data only in accordance with IPSX’s Privacy Notice, the Agreement and this Appendix and Annex 1 (Data Processing Details) (which may be updated from time to time by written agreement of the parties), (“Processing Instructions”); and 3.1.2. immediately inform the Counterparty of any requirement under applicable law that would require IPSX to process the Protected Data other than only on the Processing Instructions, or if any Counterparty instruction does not comply with DP Laws. 3.2 IPSX shall implement and maintain appropriate technical and organisational measures for the processing of Protected Data by or on behalf of IPSX: 3.2.1. to meet or exceed the requirements of DP Laws and protect the rights of Data Subjects; and 3.2.2. to ensure a level of security in respect of Protected Data appropriate to the risks of the processing, in particular to protect against accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Protected Data. 3.3 Without affecting the effectiveness of paragraph 3.2.2, IPSX shall, in respect of all Protected Data comply with the requirements regarding security set out in DP Laws, and in this Agreement. 3.4 If IPSX is to process Protected Data with a Sub-Processor, then IPSX shall appoint the Sub- Processor under a binding written contract (“Processor Contract”) which imposes the same data protection obligations as are contained in this Agreement on the Sub-Processor, including under paragraph 3.2, and this paragraph 3.4 for engaging another Processor. 3.5 IPSX shall: 3.5.1. promptly on request by the Counterparty give details of any Processor Contract to the Counterparty; and 3.5.2. where a Sub-Processor does not comply with its data protection obligations in accordance with the Processor Contract, remain fully liable to the Counterparty for that Sub-Processor’s obligations. 3.6 IPSX shall: 3.6.1. ensure that IPSX Personnel processing Protected Data have signed agreements requiring them to keep Protected Data confidential; 3.6.2. take all reasonable steps to ensure the reliability of IPSX Personnel processing Protected Data; and 3.6.3. ensure that IPSX Personnel receive adequate training on compliance with this Schedule and DP Laws. 3.7 IPSX shall put in place and maintain appropriate technica...

Related to PROCESSOR SPECIFIC OBLIGATIONS

  • Specific Obligations The HSP: will provide to the Funder, or to such other entity as the Funder may direct, in the form and within the time specified by the Funder, the Reports, other than personal health information as defined in the Enabling Legislation, that the Funder requires for the purposes of exercising its powers and duties under this Agreement, the Accountability Agreement, the Enabling Legislation or for the purposes that are prescribed under any Applicable Law; will fulfil the specific reporting requirements set out in Schedule B; will ensure that every Report is complete, accurate, signed on behalf of the HSP by an authorized signing officer where required and provided in a timely manner and in a form satisfactory to the Funder; agrees that every Report submitted to the Funder by or on behalf of the HSP, will be deemed to have been authorized by the HSP for submission. For certainty, nothing in this section 8.1 or in this Agreement restricts or otherwise limits the Funder’s right to access or to require access to personal health information as defined in the Enabling Legislation, in accordance with Applicable Law for purposes of carrying out the Funder’s statutory objects to achieve the purposes of the Enabling Legislation.

  • Processor Obligations 4.1 The Processor may collect, process or use Personal Data only within the scope of this DPA. 4.2 The Processor confirms that it shall process Personal Data on behalf of the Controller and shall take steps to ensure that any natural person acting under the authority of the Processor who has access to Personal Data shall only process the Personal Data on the documented instructions of the Controller. 4.3 The Processor shall promptly inform the Controller, if in the Processor’s opinion, any of the instructions regarding the processing of Personal Data provided by the Controller, breach any Data Protection Law. 4.4 The Processor shall ensure that all employees, agents, officers and contractors involved in the handling of Personal Data: (i) are aware of the confidential nature of the Personal Data and are contractually bound to keep the Personal Data confidential; (ii) have received appropriate training on their responsibilities as a data processor; and (iii) are bound by the terms of this DPA. 4.5 The Processor shall implement appropriate technical and organisational procedures to protect Personal Data, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons. 4.6 The Processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate: (i) the pseudonymisation and encryption of Personal Data; (ii) the ability to ensure the on-going confidentiality, integrity, availability and resilience of processing systems and services; (iii) the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; (iv) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. In accessing the appropriate level of security, account shall be taken in particular of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed. 4.7 The technical and organisational measures detailed in Exhibit B shall be at all times adhered to as a minimum security standard. The Controller accepts and agrees that the technical and organisational measures are subject to development and review and that the Processor may use alternative suitable measures to those detailed in the attachments to this DPA. 4.8 The Controller acknowledges and agrees that, in the course of providing the Services to the Controller, it may be necessary for the Processor to access the Personal Data to respond to any technical problems or Controller queries and to ensure the proper working of the Services. All such access by the Processor will be limited to those purposes.

  • Liability for Specific Obligations The Administrator will be liable only for its specific obligations under this Agreement. All other liability is expressly waived and released as a condition of, and consideration for, the execution of this Agreement by the Administrator. The Administrator will be liable for its willful misconduct, bad faith or negligence in performing its obligations under this Agreement.

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

  • Client Obligations 3.1 The Client warrants and represents that: 3.1.1 it shall co-operate with Centaur as required for the proper performance of the Services; 3.1.2 it shall provide, for Centaur, its agents, subcontractors, consultants and employees, in a timely manner and at no charge, access to the Client's premises during normal office hours (being Monday – Friday 8am – 6pm), office accommodation, data and other facilities as is reasonably required by Centaur or any of them for the proper performance of the Services; 3.1.3 all information it has provided to Centaur in relation to the Services as at the date of the Order Form is accurate, complete and is not misleading and it shall provide, in a timely manner, such further information and Client Material as Centaur may require for the proper performance of the Services, and ensure that such information and Client Material is accurate, complete and not misleading; 3.1.4 it shall be responsible (at its own cost) for preparing and maintaining the relevant premises for the supply of the Services; 3.1.5 it shall inform Centaur of all health and safety rules and regulations and any other reasonable security requirements that apply at any of the Client's premises; 3.1.6 it shall only use the Services for internal business purposes and, without prejudice to the foregoing, shall not use the Services, the Deliverables or any Centaur Materials to develop a product or service that competes with any of the products or services provided by Centaur; 3.1.7 the Client Materials shall not infringe any third party rights, including any third party Intellectual Property Rights; and 3.1.8 it shall obtain and maintain all necessary licences and consents and comply with all relevant legislation in relation to the Services, before the date on which the Services are to start. 3.2 If Centaur's performance of its obligations under this Agreement is prevented or delayed by any act or omission of the Client, its agents, subcontractors, consultants or employees, Centaur shall not be liable for any costs, charges or losses sustained or incurred by the Client that arise directly or indirectly from such prevention or delay.