Subprocessor Obligations. Where 4me authorizes any subprocessor as described in Section 5.1:
i. 4me will restrict the access of subprocessor 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, 4me will prohibit the subprocessor from accessing Customer Data for any other purpose;
ii. 4me will enter into a written agreement with the subprocessor and, to the extent that the subprocessor is performing the same data processing services that are being provided by 4me under this Addendum, 4me will impose on the subprocessor the same contractual obligations that 4me has under this Addendum; and
iii. 4me will remain responsible for its compliance with the obligations of this Addendum and for any acts or omissions of the subprocessor that cause 4me to breach any of 4me’s obligations under this Addendum.
Subprocessor Obligations. Xxxxxxxxxxx.xx shall: (i) enter into a written agreement with the Subprocessor imposing data protection terms that require the Subprocessor to protect the Subscriber Data to the standard required by Data Protection Laws; and (ii) remain
Subprocessor Obligations. 2Ring will: (a) impose data protection obligations on Subprocessors it appoints to Process Personal Data in accordance with Applicable Data Protection Law, taking into account the nature of the services provided by such Subprocessor; and (b) remain liable for each Subprocessor’s compliance with the obligations in this DPA. Upon written request, 2Ring will provide Subscriber all relevant information Subscriber reasonably requests in connection with its applicable Subprocessor agreements where required to satisfy Subscriber’s obligations under Applicable Data Protection Laws.
Subprocessor Obligations. Lattice will enter into a written agreement with each Subprocessor imposing data protection obligations no less protective of Customer Data as this DPA or the Data Protection Laws to the extent applicable to the nature of the services provided by such Subprocessor.
Subprocessor Obligations. When engaging any Subprocessor, Riverbed will: (a) ensure that any Subprocessor accesses Personal Data only as necessary to perform the Riverbed Services in accordance with the Agreement and this DPA; (b) impose contractual data protection obligations to protect Personal Data in accordance with the standard required by Applicable Data Protection Law; and (c) remain liable for any breach of this DPA that is caused by any act, error or omission of its Subprocessors.
Subprocessor Obligations. Where Xxxxxx utilizes any Subprocessor as described above (i) Xxxxxx will restrict the Subprocessor’s access to Personal Data only to what is necessary to maintain the Service or to provide the Service to Customer in accordance with the Agreement and Xxxxxx will prohibit the Subprocessor from accessing Personal Data for any other purpose; (ii) Xxxxxx will enter into a written agreement with the Subprocessor and, to the extent that the Subprocessor is performing the same data processing services that are being provided by Xxxxxx under this DPA, Xxxxxx will impose on the Subprocessor the same or similar contractual obligations that Xxxxxx has under this DPA; and (iii) Xxxxxx will remain responsible for its compliance with the obligations of this DPA and for any acts or omissions of the Subprocessor’s that cause Xxxxxx to breach any of Xxxxxx’x obligations under this DPA.
Subprocessor Obligations. Databricks shall (i) enter into a written agreement with its Subprocessors, which includes data protection and security measures no less protective of Personal Data than the Agreement and this DPA; and (ii) remain fully liable for any breach of the Agreement and this DPA that is caused by an act, error or omission of its Subprocessors to the extent that Databricks would have been liable for such act, error or omission had it been caused by Databricks.
Subprocessor Obligations. Lookout shall (i) enter into a written agreement with each Subprocessor imposing data protection terms that require the Subprocessor to protect the Customer Data to an equivalent standard under this DPA; and (ii) remain responsible for any acts or omissions of its Subprocessors that cause Lookout to breach any of its obligations under this DPA. For the purposes of Clause 9 of the Standard Contractual Clauses, Customer acknowledges that Lookout may be prevented from disclosing Subprocessor agreements to Customer due to confidentiality obligations but Lookout shall use reasonable efforts to provide Customer with all information it reasonably can in connection with Subprocessor agreements upon request.
Subprocessor Obligations. Where Temporal authorises a Subprocessor to process Customer Personal Data as described in this section 5, Temporal will enter into a written agreement with each such Subprocessor that contains provisions that are consistent to those contained in this DPA. Except as set forth in this DPA or as otherwise authorised in writing by Customer, Temporal will not permit any Subprocessors to process Customer Personal Data.
Subprocessor Obligations. Lookout shall (i) enter into a written agreement with each Subprocessor imposing data protection terms that require the Subprocessor to protect Customer Data to an equivalent standard under this DPA; and (ii) remain responsible for any acts or omissions of its Subprocessors that cause Lookout to breach any of its obligations under this DPA.
