Sub-processor Obligations Clause Samples
POPULAR SAMPLE Copied 1 times
Sub-processor Obligations. Medallia shall: (i) enter into a written agreement with the Sub-processor as required by Article 28 of GDPR or UK GDPR (as applicable) (or their equivalent in other applicable 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 Medallia to breach any of its obligations under this DPA.
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.
Sub-processor Obligations. Where AWS authorises any sub-processor as described in Section 6.1:
(i) AWS will restrict the sub-processor’s access to Customer Data only to what is necessary to maintain the Services or to provide the Services to Customer and any End Users in accordance with the Documentation and AWS will prohibit the sub-processor from accessing Customer Data for any other purpose;
(ii) AWS will enter into a written agreement with the sub-processor and, to the extent that the sub-processor is performing the same data processing services that are being provided by AWS under this DPA, AWS will impose on the sub- processor the same contractual obligations that AWS has under this DPA; and
(iii) AWS will remain responsible for its compliance with the obligations of this DPA and for any acts or omissions of the sub-processors that cause AWS to breach any of AWS’s obligations under this DPA.
Sub-processor Obligations. Chargifi shall: (i) enter into a written agreement with each Sub-processor containing data protection obligations that provide at least the same level of protection for Personal Data as those in this DPA, to the extent applicable to the nature of the service provided by such Sub- processor; and (ii) remain responsible for such Sub-processor’s compliance with the obligations of this DPA and for any acts or omissions of such Sub-processor that cause Chargifi to breach any of its obligations under this DPA.
Sub-processor Obligations. MariaDB shall: (i) enter into a written agreement with each Sub- processor imposing data protection terms that require the Sub-processor to protect personal data to the standard required by applicable European Data Protection Law and this DPA; 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 MariaDB to breach any of its obligations under this DPA.
Sub-processor Obligations. To the extent required by European Data Protection Laws, Salesloft shall enter into a written agreement with each Sub-processor imposing substantively similar data protection obligations as set out in this DPA. Where Salesloft’s engagement of a Sub-processor involves a transfer of Personal Data to a Third Country, Salesloft will ensure a valid transfer mechanism is in place with each Sub-processor as may be required by European Data Protection Laws.
Sub-processor Obligations. The Data Processor shall ensure that where it engages a Sub-processor for carrying out specific processing activities on behalf of the Data Controller, it will impose the data protection obligations as set out in this Data Processing Agreement, in particular providing sufficient guarantees to implement appropriate technical and organisational measures.
Sub-processor Obligations. In the event New Relic engages a Sub-Processor to carry out specific processing activities on behalf of Customer, New Relic shall conduct appropriate due diligence and security review prior to engaging that Sub-Processor and shall place substantially similar obligations to this Addendum on such Sub-Processor. Where such additional Sub-Processor fails to fulfill its data protection obligations, New Relic shall remain fully liable to Customer for the performance of that Sub- Processor’s obligations.
Sub-processor Obligations. Where Processor authorises any sub-processor as described in Section 5.1:
(i) Processor will restrict the sub-processor’s access to Customer Data only to what is necessary to maintain the Services or to provide the Services to Customer and any End Users in accordance with the Documentation and Processor will prohibit the sub-processor from accessing Customer Data for any other purpose;
(ii) Processor will enter into a written agreement with the sub-processor and, to the extent that the sub-processor is performing the same data processing services that are being provided by Processor under this DPA, Processor will impose on the subprocessor the same contractual obligations that Processor has under this DPA; and
(iii) Processor will remain responsible for its compliance with the obligations of this DPA and for any acts or omissions of the sub-processors that cause Processor to breach any of Processor’s obligations under this DPA.
Sub-processor Obligations. SailPoint will: (i) not engage a Sub-processor unless SailPoint enters into a written agreement with the Sub-processor imposing data protection terms that require the Sub-processor to protect the Customer Personal Information to the same standard as SailPoint; and (ii) remain responsible for its compliance with the obligations of this DPA and for any failure by the Sub-processor to fulfil its data protection obligations under the applicable Data Protection Laws.