Subprocessor Obligations. Where 4me authorizes any subprocessor as described in Section 5.1:
Subprocessor Obligations. Xxxxxxxx.xx shall: (i) enter into a written agreement with the Subprocessor imposing data protection terms that require the Subprocessor to protect the Company 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 Subprocessor that cause Xxxxxxxx.xx to breach any of its obligations under this DPA.
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. 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. 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. 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 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.
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. Where insightsoftware authorizes any Subprocessor:
Subprocessor Obligations. Upstash will impose on each Subprocessor the same data protection obligations as are imposed on us under this DPA. We will be liable to you for the performance of the Subprocessors' obligations to the extent required by Data Protection Law.
