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 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 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 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 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 thirty (30) 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.

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

  • Use of Sub-Contractors A framework of practical business provisions. Edit as you require. This ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ - ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ .

  • RETURN AND DELETION OF CUSTOMER DATA The Braze Services allow import, export, and deletion of Customer Data by authorized Dashboard Users at all times during the term of a customer’s subscription. Following termination or expiration of the Braze Services, Braze shall securely overwrite or delete Customer Data within 60 days following any such termination in Braze’s production instance, and in accordance with the Agreement, applicable laws and the Documentation.

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

Time is Money Join Law Insider Premium to draft better contracts faster.