Changes to Sub-processors Sample Clauses

Changes to Sub-processors. 10.1 MailChimp shall (i) provide an up-to-date list of the Sub-processors it has appointed upon written request from Customer; and (ii) notify Customer (for which email shall suffice) if it adds or removes Sub-processors at least 10 days prior to any such changes.
AutoNDA by SimpleDocs
Changes to Sub-processors. 10.1. MailerLite shall provide a list of the Sub-Processors upon written request from Customer and notify Customer via email if it adds or removes Sub-Processors at least 10 days prior to any such changes.
Changes to Sub-processors in the event of a modification of the list of its sub- processors, Sendinblue will notify the User by email or by notification through the customer account, and the User will have the possibility to terminate the Agreement in the event of an objection. It is specified that this notification will include any information relating to possible transfers of Personal Data the EEA.
Changes to Sub-processors. Processor shall maintain and make available in the Cognito Forms Privacy Policy an up-to- date list of the Sub-processors it has appointed, and will notify Controller (for which email shall suffice) if it adds or removes Sub-processors at least 10 days prior to any such changes. If the Controller objects to the changes in Sub-processors, the Controller' sole remedy will be to terminate their Account, thus terminating this DPA and the Terms of Service agreement and ending further Processing of Personal Data on their behalf.
Changes to Sub-processors. Customer may reasonably object to Tripwire’s use of a new Sub-Processor (e.g., if making Personal Data available to the Sub-Processor may violate Applicable Data Protection Law or weaken the protections for such Personal Data) by notifying the Tripwire Data Privacy Contact within ten (10) business days after receipt of Tripwire’s notice in accordance with the notification mechanism described in Section 4.1 above. Such notice must explain the reasonable grounds for the objection. If Customer objects to a new Sub-Processor as permitted in this Section 4.2, Tripwire will use commercially reasonable efforts to make available to Customer a change in the Services or recommend a commercially reasonable change to Customer’s configuration or use of the Services to avoid Processing of Personal Data by the objected-to new Sub-Processor without unreasonably burdening Customer. If Tripwire is unable to make available such change within a reasonable period of time (not exceeding thirty (30) days), Customer may terminate without penalty the Agreement with respect only to those Services that cannot be provided by Tripwire without the use of the objected- to new Sub-Processor by providing written notice to the Tripwire Data Privacy Contact. Tripwire will refund any fees that were prepaid to Tripwire covering the remainder of the term of such Agreement following the effective date of termination with respect to the terminated Services.
Changes to Sub-processors. If Customer subscribes to Sub-processor notifications, Atlassian will provide a notice to Customer of any new Sub-processors as soon as reasonably practicable, however at least fourteen (14) days’ prior to allowing such Sub-processor to process Customer Personal Data (the “Notice Period”). Customer may object in writing to Atlassian’s appointment of a new Sub-processor during the Notice Period, provided that such objection is based on reasonable grounds relating to data protection. In such an event, the parties will discuss such concerns in good faith with a view to achieving resolution. If the parties are not able to achieve resolution within the Notice Period, Customer, as its sole and exclusive remedy, may terminate the applicable Order(s) or parts of the Service provided by the Sub-processor in question for convenience. If the Customer does not object during the Notice Period, Atlassian will deem Customer to have authorized the new Sub-processor.
Changes to Sub-processors. Provided that Customer signs up for notifications at xxxxx://xxxxxxxx.xxx/NR-legal-signup-datasubprocessors, New Relic shall provide prior notice of any new third-party Sub-Processors. After being notified, Customer will have ten (10) business days to notify New Relic in writing of any reasonable objection it has to the new third-party Sub-Processor(s). Failure to notify New Relic within this time frame will be deemed approval of the new third-party Sub- Processor(s). In the event Customer provides reasonable objection, New Relic will use reasonable efforts to make a change in the service or Customer’s configuration available to avoid processing of Personal Data by such third-party Sub-Processor. If New Relic is unable to make available such change within a reasonable period of time, which shall not exceed sixty (60) days, Customer may terminate the applicable order with respect to the affected service that cannot be provided without use of the rejected third-party Sub-Processor.
AutoNDA by SimpleDocs
Changes to Sub-processors. (a) In relation to the list of Sub-processors on SailPoint’s website at xxxxx://xxx.xxxxxxxxx.xxx/legal/sub-processors, SailPoint shall notify and request Customer’s approval of any: (a) new Sub-processor it intends to grant permission; or (b) existing Sub-processor it intends to withdraw permission, in either (a) and (b), to Process Customer Personal Information (“Request”) at least thirty (30) days prior to such grant or withdrawal, as the case may be (such notice period, the “Review Period”).
Changes to Sub-processors. RingCentral may, by giving reasonable notice to the Customer, add or make changes to the Sub-processors. If the Customer objects to the appointment of an additional Sub-processor within 30 calendar days of such notice on reasonable grounds relating to the protection of the Personal Data, then the parties will discuss such concerns in with a view to achieving resolution. If such resolution cannot be reached, then RingCentral will either not appoint the Sub-processor or, if this is not possible, Customer will be entitled to suspend or terminate the affected RingCentral Service in accordance with the termination provisions of the Agreement. Notwithstanding the foregoing, in the event of an unforeseeable force majeure (such as a Sub-processor failure) that can provoke a degradation or interruption of the Service, RingCentral reserves the right to immediately change the failing Sub-processor in order to maintain or restore the standard conditions of Service. In this situation, the notification of Sub-processor change may be exceptionally sent after the change.
Changes to Sub-processors. HES shall provide Customer reasonable advance notice (for which email shall suffice) if it adds or removes Sub-processors.
Time is Money Join Law Insider Premium to draft better contracts faster.