Engagement of subprocessors Sample Clauses

Engagement of subprocessors. 4.1. The Host grants Lento permission to outsource the processing of personal data to third parties (‘Subprocessors’), including the Subprocessors listed in Table A. 4.2. If Lento wishes to engage a new or different Subprocessor, it will inform the Host of this in writing. The Host will then have two weeks to object to the engagement of the new Subprocessor. This objection should be submitted to Lento in writing and supported by arguments. If the Host does not object within the above-mentioned period of two weeks, it will be deemed to have agreed to the engagement of the new or different Subprocessor(s). 4.3. If the Host objects to the engagement of a Subprocessor, Lento may not (or no longer) be able to perform (or continue to perform) the Agreement in full. In such a case, the parties will consult each other in order to reach an appropriate solution. Lento will not be liable for any damage or loss resulting from the fact that it is not (or no longer) able to perform (or continue to perform) the Agreement in full in the event of an objection as referred to in this Article 4.2. 4.4. Lento will impose obligations arising from the Data Processing Agreement or obligations comparable thereto on the Subprocessor(s) it engages, insofar as this can reasonably be required.
AutoNDA by SimpleDocs
Engagement of subprocessors. 5.1 The Processor has the right to engage third parties as Subprocessors for the Processing without the prior written permission of the Controller. 5.2 The Processor will ensure that the third party (parties) concerned enter(s) into an agreement based on which this/these party/parties must observe at least the same legal obligations as the Processor. 5.3 The Processor will inform the Controller of the Subprocessors it engages. The Controller may object to additions or substitutions with respect to the Processor's Subprocessors. 5.4 In any event, the Controller hereby grants permission for the engagement of the Subprocessors and/or categories of Subprocessors listed in Annexe 2.
Engagement of subprocessors. In case of any subprocessing (including by affiliates of Provider), Provider shall: (i) notify HERE of the planned subprocessing, (ii) enter into a written contract with its subprocessor which imposes the same or at least equivalent obligations on the subprocessor as are imposed on Provider under this Agreement; such contract shall also include a description of the subcontracted data processing services, the right for HERE to exercise audit rights with the subprocessor and the technical and organizational measures the subprocessor has to implement in such a manner that the processing will meet the requirements of applicable law; (iiI) adequately and regularly audit the subprocessor with respect to compliance with these requirements and document the results of such audits; and (iv) ensure an adequate level of data protection within the meaning of applicable data protection law for the subprocessor engaged by Provider, if such adequate level of data protection is not already ensured by applicable law. Provider shall remain fully liable to HERE for the performance of the subprocessor´s obligations.
Engagement of subprocessors. The Processor is permitted to outsource to a Third Party (hereafter: the ‘Subprocessor’) the work it performs on behalf of the Controller in accordance with the provisions. By signing this Processing Agreement, the Controller also grants written permission for the outsourcing of its activities to the Subprocessor.
Engagement of subprocessors. When engaging any new Subprocessor, SmartBear will enter into a written agreement with each Subprocessor containing data protection obligations no less protective than those in this Data Processing Addendum or as may otherwise be required by applicable Data Protection Laws and Regulations. SmartBear shall remain fully liable to Company for the performance of any Subprocessor’s data protection obligations in relation to the Services or Software. For the avoidance of doubt, SmartBear may continue to use those Subprocessors already engaged by SmartBear as at the date of this Agreement.
Engagement of subprocessors. 4.1. The Employer grants Lento permission to outsource the processing of personal data to third parties (‘Subprocessors’), in cluding the Subprocessors listed in Table A. 4.2. If Xxxxx wishes to engage a new or different Subprocessor, it will inform the Employer of this in writing. The Employer will then have two weeks to object to the engagement of the new Subprocessor. This objection shou ld be submitted to Xxxxx in writing and supported by arguments. If the Employer does not object within the above-mentioned period of two weeks, it will be deemed to have agreed to the engagement of thenew or different Subprocessor(s). 4.3. If the Employer objects to the engagement of a Subprocessor, Lento may not (or no longer) be able to perform (or continue to perform) the Agreement in full. In such a case, the parties will consult each other in order to reach an appropriate solution. Lento will not be liable for any damage or loss resulting from the fact that it is not (or no longer) able to perform (or continue to perform) t he Agreement in full in the event of an objection as referred to in this Article 4.2. 4.4. Lento will impose obligations arising from the Data Processing Agreement or obligations comparable thereto on the Subprocessor(s) it engages, insofar as this can reasonably be required.
Engagement of subprocessors. 7.1. The Processor will not outsource its activities, in so far as consisting of or requiring the processing of Personal Data, to a Subprocessor without the prior written permission of the Controller. The foregoing does not apply to the Subprocessors listed in appendix 1. 7.2. In so far as the Controller consents to the engagement of a Subprocessor, the Processor will impose on this Subprocessor the same or stricter obligations as arise for itself from this Processing Agreement and the law. The Processor will record these agreements in writing and monitor compliance with them by the Subprocessor. On request, the Processor will provide the Controller with a copy of the agreement(s) concluded with the Subprocessor. 7.3. Notwithstanding the Controller's permission for engaging a Subprocessor to (partially) process data on behalf of the Processor, the Processor will remain fully liable to the Controller for the consequences of outsourcing work to a Subprocessor. The Controller's permission for outsourcing work to a Subprocessor does not alter the fact that the engagement of Subprocessors in a country outside the European Economic Area requires permission in accordance with article 3.7 of this Processing Agreement.
AutoNDA by SimpleDocs
Engagement of subprocessors. In accordance with GDPR Article 28(2), Processor shall not engage any Subprocessor without prior specific or general written authorization of Controller. In the case of a general written authorization, Processor shall inform the Controller of any intended changes concerning the addition or replacement of other Subprocessors and give Controller the opportunity to object to such changes. Processor shall also comply with the requirements for subprocessing as set forth in Article 28(4), namely that the data protection obligations set forth therein shall be imposed upon the Subprocessor, so that Processor’s contract with the Subprocessor contains sufficient guarantees that the processing to be performed by such Subprocessor will meet the requirements of the GDPR.
Engagement of subprocessors. If the Processor uses the services of a subprocessor in order to carry out specific processing activities on behalf of the Controller, the same data protection obligations as set out in this DPA or other legal act between the Controller and the Processor shall be imposed on the subprocessor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of this DPA and the applicable data protection law (in particular with regard to compliance with instructions off the Controller, compliance with technical and organisational measures, provision of information and the toleration of inspections). Furthermore, the Processor must carefully select the subprocessor, check its reliability and monitor its compliance with the requirements of this DPA and the data protection law (Art. 28 (2) and 4 GDPR).

Related to Engagement of subprocessors

  • 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.

  • Engineer Payment of Subproviders No later than ten (10) days after receiving payment from the State, the Engineer shall pay all subproviders for work performed under a subcontract authorized hereunder. The State may withhold all payments that have or may become due if the Engineer fails to comply with the ten-day payment requirement. The State may also suspend the work under this contract or any work authorization until subproviders are paid. This requirement also applies to all lower tier subproviders, and this provision must be incorporated into all subcontracts.

  • PAYMENT OF SUBCONTRACTORS Contractor shall pay any of its subcontractors not later than seven (7) days after receipt of any progress payment, unless otherwise agreed to in writing, the respective amounts allowed Contractor on account of the work performed by subcontractor(s), to the extent of each subcontractor’s interest therein, except as otherwise provided in Business and Professions Code Section 7108.5.

  • Appointment of Sub-processors Client acknowledges and agrees that (a) Data Processor’s Affiliates may be used as Sub-processors; and (b) Data Processor and/or Data Processor’s Affiliates respectively may engage third-party Sub-processors in connection with the provision of the Services.

  • Oversight of Subcontractors In the event that Vendor engages subcontractors or other authorized persons or entities to perform one or more of its obligations under the Master Agreement (including subcontracting hosting of the Protected Data to a hosting service provider), it will require those subcontractors or other authorized persons or entities to whom it will disclose the Protected Data to execute legally binding agreements acknowledging their obligation under Section 2-d of the New York Education Law to comply with all applicable data protection, privacy and security requirements required of Vendor under the Master Agreement and applicable state and federal law and regulations.

  • Appointment of Subservicer or Subcontractor (a) The Servicer may at any time appoint a subservicer to perform all or any portion of its obligations as Servicer hereunder; provided, however, that the Servicer shall remain obligated and be liable to the Issuer, the Owner Trustee, the Delaware Trustee, the Indenture Trustee, the Certificateholders and the Noteholders for the servicing and administering of the Receivables in accordance with the provisions hereof without diminution of such obligation and liability by virtue of the appointment of such subservicer and to the same extent and under the same terms and conditions as if the Servicer alone were servicing and administering the Receivables. The fees and expenses of the subservicer shall be as agreed between the Servicer and its subservicer from time to time, and none of the Issuer, the Owner Trustee, the Delaware Trustee, the Indenture Trustee, the Certificateholders or the Noteholders shall have any responsibility therefor. (b) The Servicer shall cause any Subservicer used by the Servicer (or by any Subservicer) for the benefit of the Issuer to comply with the reporting and compliance provisions of this Agreement to the same extent as if such Subservicer were the Servicer, and to provide the information required with respect to such Subservicer as is required to file all required reports with the Commission. The Servicer shall be responsible for obtaining from each Subservicer and delivering to the Issuer and the Administrator any servicer compliance statement required to be delivered by such Subservicer under Section 3.11, any assessment of compliance and attestation required to be delivered by such Subservicer under Section 3.12 and any certification required to be delivered to the Person that will be responsible for signing the Sarbanes Certification under Section 3.12(a)(iv) as and when required to be delivered. (c) The Servicer shall promptly upon request provide to the Issuer or the Administrator, acting on behalf of the Issuer, a written description (in form and substance satisfactory to the Issuer and the Administrator) of the role and function of each Subcontractor utilized by the Servicer or any Subservicer, specifying (i) the identity of each such Subcontractor, (ii) which, if any, of such Subcontractors are “participating in the servicing function” within the meaning of Item 1122 of Regulation AB, and (iii) which, if any, elements of the Servicing Criteria will be addressed in assessments of compliance provided by each Subcontractor identified pursuant to clause (ii) of this paragraph. As a condition to the utilization of any Subcontractor determined to be “participating in the servicing function” within the meaning of Item 1122 of Regulation AB, the Servicer shall cause any such Subcontractor used by the Servicer (or by any Subservicer) for the benefit of the Issuer and the Depositor to comply with the reporting and compliance provisions of Section 3.12(a) of this Agreement to the same extent as if such Subcontractor were the Servicer. The Servicer shall be responsible for obtaining from each Subcontractor and delivering to the Issuer and the Administrator any assessment of compliance and attestation required to be delivered by such Subcontractor, in each case as and when required to be delivered.

  • LIST OF SUB-PROCESSORS The controller has authorised the use of the following sub-processors:

  • 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.

  • 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.

  • Sellers Engagement of Servicer to Perform Servicing Responsibilities Section 2.01. Contract for Servicing; Possession of Servicing Files. The Seller, by execution and delivery of this Agreement, does hereby contract with the Servicer as an independent contractor, subject to the terms of this Agreement, for the servicing of the Mortgage Loans. On or before the Servicing Transfer Date the Seller shall cause the Prior Servicer to deliver to the Servicer the Servicing Files with respect to the Mortgage Loans listed on the Mortgage Loan Schedule. The Servicer shall maintain a Servicing File with respect to each Mortgage Loan in order to service such Mortgage Loans pursuant to this Agreement and each Servicing File delivered to the Servicer shall be held in trust by the Servicer for the benefit of the Trustee; provided, however, that the Servicer shall have no liability for any Servicing Files (or portions thereof) not delivered by the Seller. The Servicer’s possession of any portion of the Mortgage Loan documents shall be at the will of the Trustee for the sole purpose of facilitating servicing of the related Mortgage Loan pursuant to this Agreement, and such retention and possession by the Servicer shall be in a custodial capacity only. The ownership of each Mortgage Note, Mortgage, and the contents of the Servicing File shall be vested in the Trustee and the ownership of all records and documents with respect to the related Mortgage Loan prepared by or which come into the possession of the Servicer shall immediately vest in the Trustee and shall be retained and maintained, in trust, by the Servicer at the will of the Trustee in such custodial capacity only. The portion of each Servicing File retained by the Servicer pursuant to this Agreement shall be appropriately marked to clearly reflect the ownership of the related Mortgage Loan by the Trustee. The Servicer shall release from its custody the contents of any Servicing File retained by it only in accordance with this Agreement.

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