Requirements for Subprocessor Engagement. When engaging any Subprocessor, Google will:
Requirements for Subprocessor Engagement. When engaging any Subprocessor, Upwork will:
Requirements for Subprocessor Engagement. When engaging any Subprocessor, Google will: ▪ (a) ensure via a written contract that: ▪ (i) the Subprocessor only accesses and uses Customer Data to the extent required to perform the obligations subcontracted to it, and does so in accordance with the applicable Agreement (including this Data Processing Amendment) and any Model Contract Clauses entered into or Alternative Transfer Solution adopted by Google as described in Section 10.2 (Transfers of Data Out of the EEA); and
Requirements for Subprocessor Engagement. When engaging any Subprocessor, Provider will enter into a written contract with such Subprocessor containing data protection obligations not less protective than those in this DPA with respect to Personal Data to the extent applicable to the nature of the services provided by such Subprocessor. Provider shall be liable for all obligations under the Agreement subcontracted to the Subprocessor and its actions and omissions related thereto.
Requirements for Subprocessor Engagement. When engaging any Subprocessor, Virsae will enter into a written contract with such Subprocessor containing data protection obligations materially consistent with those in this Addendum with respect to Personal Data to the extent applicable to the nature of the services provided by such Subprocessor. Virsae shall be liable for all obligations subcontracted to, and any Subprocessor of such obligations.
Requirements for Subprocessor Engagement. When engaging any Subprocessor, IT Farm will ensure via a written contract that: the Subprocessor only accesses and uses Customer Data to the extent required to perform the obligations subcontracted to it, and does so in accordance with the Agreement (including these Terms); If the GDPR applies to the processing of Customer Personal Data, the data protection obligations set out in Article 28(3) of the GDPR, as described in these Terms, are imposed on the Subprocessor; and remain fully liable for all obligations subcontracted to, and all acts and omissions of, the Subprocessor.
Requirements for Subprocessor Engagement. European Data Protection Law requires Google to ensure via a written contract that the data protection obligations described in this Addendum, as referred to in Article 28(3) of the GDPR, if applicable, are imposed on any Subprocessor engaged by Google. CCPA
Requirements for Subprocessor Engagement. When engaging any Subprocessor, Actifio will:
Requirements for Subprocessor Engagement. When engaging any Subprocessor, Aternity shall:
Requirements for Subprocessor Engagement. When engaging any Subprocessor, Blinkfire Analytics will enter into a written contract with such Subprocessor containing data protection obligations not less protective than those in the Agreement (including this Addendum) with respect to the protection of Customer Personal Data to the extent applicable to the nature of the Services provided by such Subprocessor. Blinkfire Analytics shall be liable for all obligations subcontracted to, and all acts and omissions of, the Subprocessor. Upon Customer’s written request, Blinkfire Analytics shall allow Customer to examine the data protection provisions of agreements between Blinkfire Analytics and its subcontractors that access Customer Personal Data, provided that such agreements shall remain Blinkfire Analytics’ Confidential Information. Customer agrees that this section 9.3 satisfies the requirements under Clause 5(j) of the Model Contract Clauses.
