Processor to Processor Clauses Sample Clauses

Processor to Processor Clauses. Where Customer is a Processor and a data exporter of Relevant Personal Data and Retool is a Processor and data importer in respect of that Relevant Personal Data, then the Parties shall comply with the Processor to Processor Clauses, subject to the additional terms in Schedule 2 (Additional Transfer Terms).
Sample 1Sample 2
AutoNDA by SimpleDocs
Processor to Processor Clauses. For purposes of the Processor to Processor Clauses, Xxxxxxxx agrees that it is unlikely that 37signals will know the identity of Customer's Controller(s) because 37signals does not have a direct relationship with such Controller(s). Therefore, Customer will fulfill any and all of 37signals's obligations to Customer's Controller(s) under the Processor to Processor Clauses.
Sample 1
Processor to Processor Clauses. For purposes of the Processor to Processor Clauses, Xxxxxxxx agrees that it is unlikely that Basecamp will know the identity of Customer’s Controller(s) because Basecamp does not have a direct relationship with such Controller(s). Therefore, Customer will fulfill any and all of Basecamp’s obligations to Customer’s Controller(s) under the Processor to Processor Clauses.
Sample 1
Processor to Processor Clauses. For purposes of the Processor to Processor Clauses, Xxxxxxxx agrees that it is unlikely that Xxxxxx will know the identity of Customer's Controller(s) because Canopy does not have a direct relationship with such Controller(s). Therefore, Customer will fulfill any and all of Canopy's obligations to Customer's Controller(s) under the Processor to Processor Clauses.
Sample 1
Processor to Processor Clauses. For purposes of the Processor to Processor Clauses, Xxxxxxxx agrees that it is unlikely that Instatus will know the identity of Customer’s Controller(s) because Instatus does not have a direct relationship with such Controller(s). Therefore, Customer will fulfill any and all of Instatus’s obligations to Customer’s Controller(s) under the Processor to Processor Clauses.
Sample 1

Related to Processor to Processor Clauses

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

  • Interconnection Facilities Engineering Procurement and Construction Interconnection Facilities, Network Upgrades, and Distribution Upgrades shall be studied, designed, and constructed pursuant to Good Utility Practice. Such studies, design and construction shall be based on the assumed accuracy and completeness of all technical information received by the Participating TO and the CAISO from the Interconnection Customer associated with interconnecting the Large Generating Facility.

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

  • Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at xxxx://xxx.xxxxx.xxx/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.

  • Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”). (ii) The Contractor shall, within 30 (thirty) days of the Appointed Date, submit to the Authority’s Engineer its Quality Assurance Plan which shall include the following: (a) organisation, duties and responsibilities, procedures, inspections and documentation; (b) quality control mechanism including sampling and testing of Materials, test frequencies, standards, acceptance criteria, testing facilities, reporting, recording and interpretation of test results, approvals, check list for site activities, and proforma for testing and calibration in accordance with the Specifications for Road and Bridge Works issued by MORTH, relevant IRC specifications and Good Industry Practice; and (c) internal quality audit system. The Authority’s Engineer shall convey its approval to the Contractor within a period of 21 (twenty-one) days of receipt of the QAP stating the modifications, if any, required, and the Contractor shall incorporate those in the QAP to the extent required for conforming with the provisions of this Clause 11.2. (iii) The Contractor shall procure all documents, apparatus and instruments, fuel, consumables, water, electricity, labour, Materials, samples, and qualified personnel as are necessary for examining and testing the Project Assets and workmanship in accordance with the Quality Assurance Plan. (iv) The cost of testing of Construction, Materials and workmanship under this Article 11 shall be borne by the Contractor.

  • Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract. a. The contractor shall notify all potential subcontractors and suppliers and lessors of their EEO obligations under this contract. b. The contractor will use good faith efforts to ensure subcontractor compliance with their EEO obligations.

  • Use of Sub-Contractors If the Applicant requires the use of a Sub-Contractor in order to adequately complete the Project, a collaboration letter, contract or agreement between the Applicant and the Sub-Contractor must be in place prior to the Applicant proceeding with any Milestone which requires assistance from the Sub-Contractor. Applicant shall: (a) identify the Sub-Contractor to Alberta Innovates; (b) provide a copy of such Sub- Contractor agreement to Alberta Innovates upon request, and on a strictly confidential basis; and (c) ensure that dealings with the Sub-Contractor are not prohibited under any Applicable Laws Including any Anti- Bribery, Anti-Corruption and Sanctions Laws or Export Control Laws. Alberta Innovates may request the Applicant to provide evidence that it has paid the Sub-Contractor for such services. If the Applicant is using a Sub-Contractor: (aa) nothing in this Investment Agreement creates any employment, contract, agency relationship, or other direct or indirect, relationship of any kind between Alberta Innovates and such Sub-Contractor; and (bb) the Applicant shall be solely responsible for all work, acts, claims, defaults and liabilities relating to the Sub-Contractor.

  • Accessories, Spare Parts and Tools Accessories, spare parts and tools dispatched with a piece of equipment, machine, apparatus or vehicle, which are part of the normal equipment and included in the price thereof or which are not separately invoiced, shall be regarded as one with the piece of equipment, machine, apparatus or vehicle in question.

  • Changes in Equipment, Systems, Etc USBFS reserves the right to make changes from time to time, as it deems advisable, relating to its systems, programs, rules, operating schedules and equipment, so long as such changes do not adversely affect the services provided to the Trust under this Agreement.

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