Bugcrowd Sub-Processors Clause Samples

Bugcrowd Sub-Processors. Customer agrees that Bugcrowd may engage sub-processors to Process Personal Data in accordance with the DPA. A list of sub-processors including their addresses is available upon request. The parties agree that copies of the sub-processor agreements that Customer may request Bugcrowd to provide pursuant to Clause 5(i) of the Model Clauses may have all the commercial clauses or clauses unrelated to data processing, removed by Bugcrowd beforehand and, that such copies will be provided by Bugcrowd, in a manner to be determined in its discretion, only upon reasonable request by Customer. When engaging sub-processors, Bugcrowd shall enter into agreements with the sub-processors to bind them to obligations which are substantially similar or more stringent than those set out in this DPA. Customer will not directly communicate with Bugcrowd’s sub-processors about the software or Services, unless agreed to by Bugcrowd in Bugcrowd’s sole discretion. Bugcrowd will notify Customer in advance of any changes to sub- processors using regular communication means such as email, websites, and portals. If Customer reasonably objects to the addition of a new sub-processors (e.g., such change causes Customer to be non-compliant with applicable with Data Protection Laws and Regulations), Customer shall notify Bugcrowd in writing of its specific objections within thirty (30) days of receiving such notification. If Customer does not object within such period, the addition of the new sub-processor and, if applicable, the accession to this DPA shall be considered accepted. If Customer does object to the addition of a new sub- processor and Bugcrowd cannot accommodate Customer’s objection, Customer may terminate the Services and software in writing within sixty (60) days of receiving Bugcrowd’s notification.
View SourceView Similar (4)

Related to Bugcrowd Sub-Processors

  • Sub-processors 7.1 bookinglab shall not subcontract any processing of the Customer Personal Data to any Sub-Processor except as authorised by the Customer in accordance with this paragraph 7. The Customer consents to bookinglab engaging Sub-Processors to process the Data provided that: (i) bookinglab provides at least 30 days' prior notice of the addition of any subcontractor (including details of the processing it performs or will perform) (“Sub-Processor Notice”); and (ii) bookinglab complies with paragraphs 7.4 and 7.5 of this Appendix. 7.2 The Customer hereby consents to bookinglab’s use of the Sub-Processors listed at ▇▇▇.▇▇▇▇▇▇▇▇▇▇.▇▇.▇▇/▇▇▇▇▇▇ which shall be maintained and updated when any Sub-Processor is added or removed in accordance with this paragraph 7. 7.3 If within 30 days of receipt of a Sub-Processor Notice the Customer notifies bookinglab in writing of its refusal to consent to bookinglab’s appointment of a Sub-Processor on reasonable grounds relating to the protection of Customer Personal Data, then either: (i) bookinglab will not appoint the Sub-Processor; or (ii) if bookinglab does appoint the Sub-Processor, the Customer may elect to terminate the Agreement without penalty or cost to either party save that any portion of the fees paid in advance in respect of Services not yet delivered as at the effective date of termination shall be refunded to the Customer. If after 30 days from receipt of the Sub-Processor Notice the Customer has not indicated its refusal of the appointment of a Sub-Processor in accordance with this paragraph, then the Customer is deemed to have given its consent and bookinglab shall be entitled to appoint the relevant Sub-Processor with immediate effect. 7.4 If bookinglab appoints a Sub-Processor, bookinglab shall ensure that: (a) such Sub-Processor shall only process Customer Personal Data in order to perform one or more of bookinglab's obligations under this Agreement; and (b) it enters into a written agreement or other legally enforceable terms with that Sub-Processor prior to any processing by the Sub-Processor, requiring the Sub-Processor to: (i) process Customer Personal Data only in accordance with the written instructions of bookinglab or the Customer; and (ii) comply with data protection obligations equivalent in all material respects to those imposed on bookinglab under this Appendix. 7.5 Notwithstanding the appointment of a Sub-Processor, bookinglab is responsible and liable to the Customer for any processing by the Sub-Processor in breach of this Appendix.

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

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

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

  • Use of sub-processors 1. The data processor shall meet the requirements specified in Article 28(2) and (4) GDPR in order to engage another processor (a sub-processor). 2. The data processor shall therefore not engage another processor (sub-processor) for the fulfilment of the Clauses without the prior general notification of the data controller. 3. The data processor has the data controller’s general authorisation for the engagement of sub-proces- sors. The data processor shall inform the data controller of any intended changes concerning the addi- tion or replacement of sub-processors at least 14 days in advance, thereby giving the data controller the opportunity to object to such changes prior to the engagement of the concerned sub-processor(s). Longer time periods of prior notice for specific sub-processing services can be provided in Appendix B. The list of sub-processors already authorised by the data controller can be found in Appendix B. 4. Where the data processor engages a sub-processor for carrying out specific processing activities on behalf of the data controller, the same data protection obligations as set out in the Clauses shall be imposed on that sub-processor by way of a contract or other legal act under EU 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 the Clauses and the GDPR. The data processor shall therefore be responsible for requiring that the sub-processor at least complies with the obligations to which the data processor is subject pursuant to the Clauses and the GDPR. 5. A copy of such a sub-processor agreement and subsequent amendments shall – at the data controller’s request – be submitted to the data controller, thereby giving the data controller the opportunity to ensure that the same data protection obligations as set out in the Clauses are imposed on the sub-processor. Clauses on business related issues that do not affect the legal data protection content of the sub-pro- cessor agreement, shall not require submission to the data controller. 6. The data processor shall agree a third-party beneficiary clause with the sub-processor where – in the event of bankruptcy of the data processor – the data controller shall be a third-party beneficiary to the sub-processor agreement and shall have the right to enforce the agreement against the sub-processor engaged by the data processor, e.g., enabling the data controller to instruct the sub-processor to delete or return the personal data. 7. If the sub-processor does not fulfil his data protection obligations, the data processor shall remain fully liable to the data controller as regards the fulfilment of the obligations of the sub-processor. This does not affect the rights of the data subjects under the GDPR – in particular those foreseen in Articles 79 and 82 GDPR – against the data controller and the data processor, including the sub-processor.