Engagement of subprocessors Sample Clauses
POPULAR SAMPLE Copied 1 times
Engagement of subprocessors. When engaging any new Subprocessor, SmartBear will enter into a written agreement with each Subprocessor containing data protection obligations no less protective than those in this Data Processing Addendum or as may otherwise be required by applicable Data Protection Laws and Regulations. SmartBear shall remain fully liable to Company for the performance of any Subprocessor’s data protection obligations in relation to the Services or Software. For the avoidance of doubt, SmartBear may continue to use those Subprocessors already engaged by SmartBear as at the date of this Agreement.
Engagement of subprocessors. 4.1. The Host grants Lento permission to outsource the processing of personal data to third parties (‘Subprocessors’), including the Subprocessors listed in Table A.
4.2. If Lento wishes to engage a new or different Subprocessor, it will inform the Host of this in writing. The Host will then have two weeks to object to the engagement of the new Subprocessor. This objection should be submitted to Lento in writing and supported by arguments. If the Host does not object within the above-mentioned period of two weeks, it will be deemed to have agreed to the engagement of the new or different Subprocessor(s).
4.3. If the Host objects to the engagement of a Subprocessor, Lento may not (or no longer) be able to perform (or continue to perform) the Agreement in full. In such a case, the parties will consult each other in order to reach an appropriate solution. Lento will not be liable for any damage or loss resulting from the fact that it is not (or no longer) able to perform (or continue to perform) the Agreement in full in the event of an objection as referred to in this Article 4.2.
4.4. Lento will impose obligations arising from the Data Processing Agreement or obligations comparable thereto on the Subprocessor(s) it engages, insofar as this can reasonably be required.
Engagement of subprocessors. In accordance with GDPR Article 28(2), Processor shall not engage any Subprocessor without prior specific or general written authorization of Controller. In the case of a general written authorization, Processor shall inform the Controller of any intended changes concerning the addition or replacement of other Subprocessors and give Controller the opportunity to object to such changes. Processor shall also comply with the requirements for subprocessing as set forth in Article 28(4), namely that the data protection obligations set forth therein shall be imposed upon the Subprocessor, so that Processor’s contract with the Subprocessor contains sufficient guarantees that the processing to be performed by such Subprocessor will meet the requirements of the GDPR.
Engagement of subprocessors. 4.1. Lento-User grants Lento permission to outsource the processing of personal data to third parties (‘Subprocessors’), including the Subprocessors listed in Table A.
4.2. If ▇▇▇▇▇ wishes to engage a new or different Subprocessor, it will inform ▇▇▇▇▇-User of this in writing. Lento-User will then have two weeks to object to the engagement of the new Subprocessor. This objection should be submitted to ▇▇▇▇▇ in writing and supported by arguments. If Lento-User does not object within the above-mentioned period of two weeks, it will be deemed to have agreed to the engagement of the new or different Subprocessor(s).
4.3. If Lento-User objects to the engagement of a Subprocessor, Lento may not (or no longer) be able to perform (or continue to perform) the Agreement in full. In such a case, the parties will consult each other in order to reach an appropriate solution. Lento will not be liable for any damage or loss resulting from the fact that it is not (or no longer) able to perform (or continue to perform) the Agreement in full in the event of an objection as referred to in this Article 4.2.
4.4. Lento will impose obligations arising from the Data Processing Agreement or obligations comparable thereto on the Subprocessor(s) it engages, insofar as this can reasonably be required.
Engagement of subprocessors. In case of any subprocessing (including by affiliates of Provider), Provider shall: (i) notify HERE of the planned subprocessing, (ii) enter into a written contract with its subprocessor which imposes the same or at least equivalent obligations on the subprocessor as are imposed on Provider under this Agreement; such contract shall also include a description of the subcontracted data processing services, the right for HERE to exercise audit rights with the subprocessor and the technical and organizational measures the subprocessor has to implement in such a manner that the processing will meet the requirements of applicable law; (iiI) adequately and regularly audit the subprocessor with respect to compliance with these requirements and document the results of such audits; and (iv) ensure an adequate level of data protection within the meaning of applicable data protection law for the subprocessor engaged by Provider, if such adequate level of data protection is not already ensured by applicable law. Provider shall remain fully liable to HERE for the performance of the subprocessor´s obligations.
Engagement of subprocessors. 5.1 The Processor has the right to engage third parties as Subprocessors for the Processing without the prior written permission of the Controller.
5.2 The Processor will ensure that the third party (parties) concerned enter(s) into an agreement based on which this/these party/parties must observe at least the same legal obligations as the Processor.
5.3 The Processor will inform the Controller of the Subprocessors it engages. The Controller may object to additions or substitutions with respect to the Processor's Subprocessors.
5.4 In any event, the Controller hereby grants permission for the engagement of the Subprocessors and/or categories of Subprocessors listed in Annexe 2.
Engagement of subprocessors. 5.1 At the time of signature of this Data Processing Agreement, the EPO has expressly authorised the Data Processor’s subcontractors or affiliates ("subprocessors”) indicated in Schedule 3 to carry out the processing of EPO data.
5.2 Should the Data Processor wish to engage a new subprocessor, the Data Processor must, in good time but no later than thirty days before the processing of personal data by the new subprocessor is scheduled to start, notify the EPO in writing of the name and address of the subprocessor and a description of the processing to be performed by them, and request the EPO's written authorisation. The subprocessor must be competent, capable and reliable. At the EPO's request, the Data Processor must produce appropriate evidence of these qualities.
5.3 Should the EPO authorise the Data Processor to engage a new subprocessor, the terms of the Data Processor's agreement with the subprocessor must be such as to ensure that the subprocessor's processing of personal data meets the requirements laid down in this Data Processing Agreement. In particular, the Data Processor must conclude with the subprocessor an agreement no less stringent than this Data Processing Agreement and present it to the EPO upon request. The appropriate safeguards with each subprocessor must be described in Schedule 3 of this Data Processing Agreement. The Data Processor shall remain fully liable towards the EPO for ensuring the subprocessor's compliance with the Data Processor's obligations under this Data Processing Agreement. The Data Processor shall notify the EPO of any failure by the subprocessor to fulfil its obligations under the agreement between the Data Processor and their subprocessors.
5.4 The Data Processor must verify that their subprocessors have taken appropriate IT security, technical and organisational measures within the meaning of Article 4.1 and that these measures are implemented in such a way that the processing of EPO data is carried out in accordance with this Data Processing Agreement.
5.5 The EPO must be granted direct rights to request evidence from and audit any subprocessor in accordance with Article 8.
Engagement of subprocessors. The Data Processor may engage subprocessors to process Personal Data on behalf of the Data Controller. Subprocessors shall be bound by written agreements ensuring the same level of data protection as provided in this Agreement and in compliance with GDPR.
Engagement of subprocessors. 7.1. The Processor will not outsource its activities, in so far as consisting of or requiring the processing of Personal Data, to a Subprocessor without the prior written permission of the Controller. The foregoing does not apply to the Subprocessors listed in appendix 1.
7.2. In so far as the Controller consents to the engagement of a Subprocessor, the Processor will impose on this Subprocessor the same or stricter obligations as arise for itself from this Processing Agreement and the law. The Processor will record these agreements in writing and monitor compliance with them by the Subprocessor. On request, the Processor will provide the Controller with a copy of the agreement(s) concluded with the Subprocessor.
7.3. Notwithstanding the Controller's permission for engaging a Subprocessor to (partially) process data on behalf of the Processor, the Processor will remain fully liable to the Controller for the consequences of outsourcing work to a Subprocessor. The Controller's permission for outsourcing work to a Subprocessor does not alter the fact that the engagement of Subprocessors in a country outside the European Economic Area requires permission in accordance with article 3.7 of this Processing Agreement.
Engagement of subprocessors. The Processor is permitted to outsource to a Third Party (hereafter: the ‘Subprocessor’) the work it performs on behalf of the Controller in accordance with the provisions. By signing this Processing Agreement, the Controller also grants written permission for the outsourcing of its activities to the Subprocessor.