Requirements for Subprocessor Engagement Sample Clauses

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 Personal Data to the extent required to perform the obligations subcontracted to it, and does so in accordance with the Agreement (including these Data Processing Terms) and Privacy Shield; and (ii) if the GDPR applies to the processing of Customer Personal Data, the data protection obligations set out in Article 28(3) of the GDPR are imposed on the Subprocessor; and (b) remain fully liable for all obligations subcontracted to, and all acts and omissions of, the Subprocessor.

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, Upwork will: a. ensure via a written contract that: i. the Subprocessor only accesses and uses Customer Data to perform the obligations subcontracted to it, and does so in accordance with the Agreement (including this DPA) and any Model Contract Clauses entered into or Alternative Transfer Solution adopted by Upwork as described in Section 10.2 (Transfers of Data Out of the EEA); and ii. 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 this DPA, are imposed on the Subprocessor; and b. remain liable for all obligations subcontracted to, and all related acts and omissions of, the Subprocessor.

Requirements for Subprocessor Engagement. When engaging any Subprocessor, Processor 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 Agreement (including this Data Processing Agreement) and any Model Contract Clauses entered into or Alternative Transfer Solution adopted by Processor as described in Section 10.2 (Transfers of Data Out of the EEA); and (ii) 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 this Data Processing Agreement, are imposed on the Subprocessor; and (b) remain fully liable for all obligations subcontracted to, and all acts and omissions of, the Subprocessor.

Requirements for Subprocessor Engagement. When engaging any Subprocessor, IT Farm will ensure via a written contract that:

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, Google will:

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.

Requirements for Subprocessor Engagement. When engaging any Subprocessor, Cultivate will enter into a written contract with such Subprocessor containing data protection obligations not less protective than those in this Addendum with respect to Personal Data to the extent applicable to the nature of the services provided by such Subprocessor. Cultivate shall be liable for all obligations subcontracted to, and all acts and omissions of, the Subprocessor.

Requirements for Subprocessor Engagement. When engaging any Subprocessor, Aternity shall: i. ensure via a written contract: 1. the Subprocessor only accesses and uses Customer Personal Data to the extent required to perform the obligations subcontracted to it, and does so in accordance with the Agreement (including this DPA) and any Standard Contractual Clauses as described in Section 13.b; and 2. 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 this DPA, are imposed on the Subprocessor; and ii. remain fully liable for all obligations subcontracted to, and all acts and omissions of, the Subprocessor.