S ubprocessors Sample Clauses

S ubprocessors. Provider shall enter into written agreements with all Subprocessors performing functions pursuant to this DPA, whereby the Subprocessors agree to protect Student Data in manner consistent with the terms of this DPA.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
S ubprocessors. 11.1 C onsent to Subprocessor Engagement. Customer specifically authorizes the engagement as Subprocessors of: (a) those entities listed as of the Amendment Effective Date at the URL specified in Section 11.2 (Information about Subprocessors); and (b) all other Google Affiliates from time to time. In addition, without prejudice to Section 11.4 (Opportunity to Object to Subprocessor Changes), Customer generally authorizes the engagement as Subprocessors of any other third parties (“New Third Party Subprocessors”). If Customer has entered into Model Contract Clauses as described in Section 10.2 (Transfers of Data), the above authorizations constitute Customer’s prior written consent to the subcontracting by Google LLC of the processing of Customer Data. 11.2 I nformation about Subprocessors. Information about Subprocessors, including their functions and locations, is available at xxxxx://xxxxxx.xxxxxx.xxx/intl/en/terms/subprocessors.html (as may be updated by Google from time to time in accordance with this Data Processing Amendment).
Sample 1Sample 2Sample 3
S ubprocessors. 11.1 C onsent to Subprocessor Engagement. Customer specifically authorizes the engagement as Subprocessors of: (a) those entities listed as of the Amendment Effective Date at the URL specified in Section 11.2 (Information about Subprocessors); and (b) all other Google Affiliates from time to time. In addition, without prejudice to Section 11.4 (Opportunity to Object to Subprocessor Changes), Customer generally authorizes the engagement as Subprocessors of any other third parties (“New Third Party Subprocessors”). If Customer has entered into Model Contract Clauses as described in Section 10.2 (Transfers of Data), the above authorizations constitute Customer’s prior written consent to the subcontracting by Google LLC of the processing of Customer Data. 11.2 Information about Subprocessors. Information about Subprocessors, including their functions and locations, is available at xxxxx://xxxxxx.xxxxxx.xxx/intl/en/terms/subprocessors.html (as may be updated by Google from time to time in accordance with this Data Processing Amendment). 11.3 R equirements 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 Agreement (including this Data Processing Amendment) and the Model Contract Clauses or Alternative Transfer Solution, as applicable under Section 10.2 (Transfers of Data); and ii. if the GDPR applies to the processing of Customer Personal Data, the data protection obligations described in Article 28(3) of the GDPR, as described in this Data Processing Amendment, are imposed on the Subprocessor; and b. remain fully liable for all obligations subcontracted to, and all acts and omissions of, the Subprocessor. 11.4 O pportunity to Object to Subprocessor Changes.
Sample 1
S ubprocessors. Contractor shall enter into written agreements with all Subprocessors performing functions pursuant to the Service Agreement, whereby the Subprocessors agree to protect Student Data in a manner consistent with the terms of this DPA. Contractor shall provide the LEA with a description of the subprocessors or types of subprocessors who have access to the LEA's student data and shall update the list as new subprocessors are added.
Sample 1
S ubprocessors. 11.1 C onsent to Subprocessor Engagement. Customer specifically authorizes the engagement as Subprocessors of: (a) those entities listed as of the Amendment Effective Date at the URL specified in Section 11.2 (Information about Subprocessors); and (b) all other Google Affiliates from time to time. In addition, without prejudice to Section 11.4 (Opportunity to Object to Subprocessor Changes), Customer generally authorizes the engagement as Subprocessors of any other third parties (“New Third Party Subprocessors”). If Customer has entered into Model Contract Clauses as described in Section 10.2 (Transfers of Data), the above authorizations constitute Customer’s prior written consent to the subcontracting by Google LLC of the processing of Customer Data.
Sample 1

Related to S ubprocessors

  • Subprocessors Provider shall enter into written agreements with all Subprocessors performing functions for the Provider in order for the Provider to provide the Services pursuant to the Service Agreement, whereby the Subprocessors agree to protect Student Data in a manner no less stringent than the terms of this DPA.

  • Subprocessor For the purposes of this DPA, the term “Subprocessor” (sometimes referred to as the “Subcontractor”) means a party other than LEA or Provider, who Provider uses for data collection, analytics, storage, or other service to operate and/or improve its service, and who has access to Student Data.

  • Sub-processors 6.1 The Data Processor is given general authorisation to engage third-parties to process the Personal Data (“Sub-Processors”) without obtaining any further written, specific authorization from the Data Controller, provided that the Data Processor notifies the Data Controller in writing about the identity of a potential Sub-Processor (and its processors, if any) before any agreements are made with the relevant Sub-Processors and before the relevant Sub-Processor processes any of the Personal Data. If the Data Controller wishes to object to the relevant Sub- Processor, the Data Controller shall give notice hereof in writing within ten (10) business days from receiving the notification from the Data Processor. Absence of any objections from the Data Controller shall be deemed consent to the relevant Sub-Processor. 6.2 In the event the Data Controller objects to a new Sub-Processor and the Data Processor cannot accommodate the Data Controller’s objection, the Data Controller may terminate the Services by providing written notice to the Data Processor. 6.3 The Data Processor is accountable to the Data Controller for any Sub-Processor in the same way as for its own actions and omissions. 6.4 The Data Processor is at the time of entering into this Data Processor Agreement using the Sub- Processors listed in appendix B. If the Data Processor initiates sub-processing with a new Sub-Processor, such new Sub-Processor shall be added to the list in appendix B under paragraph 2.

  • Sub-processor For the purposes of this Agreement, the term “Sub-processor” (sometimes referred to as the “Subcontractor”) means a party other than LEA or Provider, who Provider uses for data collection, analytics, storage, or other service to operate and/or improve its software, and who has access to PII.

  • New Subprocessors SAP’s use of Subprocessors is at its discretion, provided that: (a) SAP will inform Customer in advance (by email or by posting on the support portal available through SAP Support) of any intended additions or replacements to the list of Subprocessors including name, address and role of the new Subprocessor; and (b) Customer may object to such changes as set out in Section 6.3.

  • Use of sub-processors (a) The data importer has the data exporter’s general authorisation for the engagement of sub- processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub- processors at least within ten (10) days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object. (b) Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects. The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.

  • Authorized Sub-processors Customer agrees that MailChimp may engage Sub-processors to process Customer Data on Customer's behalf. The Sub-processors currently engaged by MailChimp and authorized by Customer are listed in Annex A.

  • Hosted Services 3.1 The Provider hereby grants to the Customer a worldwide, non-exclusive licence to use the Hosted Services for the business purposes of the Customer in accordance with the Documentation during the Term. 3.2 The Provider shall create an Account for the Customer and shall provide to the Customer login details for that Account to enable the Customer to configure and administer the Hosted Services and enable registration of Customer End Users. 3.3 Except to the extent expressly permitted in this Agreement or required by law on a non- excludable basis, the licence granted by the Provider to the Customer under Clause 3.1 is subject to the following prohibitions: (a) the Customer must not sub-license its right to use the Hosted Services; (b) the Customer must not make any alteration to the Platform; and (c) the Customer must not conduct or request that any other person conduct any load testing or penetration testing on the Platform or Hosted Services without the prior written consent of the Provider. 3.5 The Customer shall use reasonable endeavours, including appropriate organisational and technical measures relating to Account access details, to ensure that no unauthorised person may gain access to the Hosted Services using an Account. 3.6 The parties acknowledge and agree that Schedule 2 (Availability SLA) shall govern the availability of the Hosted Services. 3.7 The Customer must ensure that all persons using the Hosted Services with the authority of the Customer or by means of an Account comply with the Terms Of Use. 3.8 The Customer must not use the Hosted Services in any way that causes, or may cause, damage to the Hosted Services or Platform or impairment of the availability or accessibility of the Hosted Services. 3.9 The Customer must not use the Hosted Services: (a) in any way that is unlawful, illegal, fraudulent or harmful; or (b) in connection with any unlawful, illegal, fraudulent or harmful purpose or activity. 3.10 For the avoidance of doubt, the Customer has no right to access the software code (including object code, intermediate code and source code) of the Platform, either during or after the Term. 3.11 The Provider may suspend the provision of the Hosted Services if any amount due to be paid by the Customer to AWS for the benefit of the Provider under this Agreement is overdue, and the Provider has given to the Customer at least 30 days' written notice, following the amount becoming overdue, of its intention to suspend the Hosted Services on this basis.

  • Direction to Account Debtors; Contracting Parties; etc Upon the occurrence and during the continuance of an Event of Default, if the Collateral Agent so directs any Assignor, such Assignor agrees (x) to cause all payments on account of the Receivables and Contracts to be made directly to one or more Cash Collateral Accounts (as the Collateral Agent shall so direct), (y) that the Collateral Agent may, at its option, directly notify the obligors with respect to any Receivables and/or under any Contracts to make payments with respect thereto as provided in the preceding clause (x), and (z) that the Collateral Agent may enforce collection of any such Receivables and Contracts and may adjust, settle or compromise the amount of payment thereof, in the same manner and to the same extent as such Assignor. Without notice to or assent by any Assignor, the Collateral Agent may, upon the occurrence and during the continuance of an Event of Default, apply any or all amounts then in, or thereafter deposited in, the Cash Collateral Accounts which application shall be effected in the manner provided in Section 7.4 of this Agreement. The reasonable costs and expenses (including reasonable attorneys' fees) of collection, whether incurred by an Assignor or the Collateral Agent, shall be borne by the relevant Assignor. The Collateral Agent shall deliver a copy of each notice referred to in the preceding clause (y) to the relevant Assignor, provided, that the failure by the Collateral Agent to so notify such Assignor shall not affect the effectiveness of such notice or the other rights of the Collateral Agent created by this Section 3.3.

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5. 1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!