Opportunity to Object to Subprocessor Changes. (a) When any new Third Party Subprocessor is engaged during the Term, Google will, at least 30 days before the new Third Party Subprocessor processes any Customer Personal Data, inform Customer of the engagement (including the name and location of the relevant subprocessor and the activities it will perform) by sending an email to the Notification Email Address.
(b) Customer may object to any new Third Party Subprocessor by terminating the Agreement immediately upon written notice to Google, on condition that Customer provides such notice within 90 days of being informed of the engagement of the new Third Party Subprocessor as described in Section 11.4(a). This termination right is Customer’s sole and exclusive remedy if Customer objects to any new Third Party Subprocessor.
Opportunity to Object to Subprocessor Changes. (a) When any new Third Party Subprocessor is engaged during the Term, Processor will, at least 30 days before the new Third Party Subprocessor processes any Customer Data, inform Customer of the engagement (including the name and location of the relevant subprocessor and the activities it will perform) by sending an email to the Notification Email Address.
(b) Customer may object to any new Third Party Subprocessor by terminating the Agreement immediately upon written notice to Processor, on condition that Customer provides such notice within 90 days of being informed of the engagement of the subprocessor as described in Section 11.4(a). This termination right is Customer’s sole and exclusive remedy if Customer objects to any new Third Party Subprocessor.
Opportunity to Object to Subprocessor Changes a. When any New Subprocessor is engaged during the Term, Google will, at least 30 days before the New Subprocessor starts processing any Customer Data, notify Customer of the engagement (including the name and location of the relevant subprocessor and the activities it will perform).
b. Customer may, within 90 days after being notified of the engagement of a New Subprocessor, object by immediately terminating the Agreement for convenience by notifying Google.
Opportunity to Object to Subprocessor Changes a. Upwork may add or remove Subprocessors from time to time. Upwork will inform Customer of new Subprocessors via a subscription mechanism described in the list of Subprocessors as described above. If Customer objects to a change, it will provide Upwork with notice of its objection to xxxx-xxxx@xxxxxx.xxx including reasonable detail supporting Customer’s concerns within sixty days of receiving notice of a change from Upwork or, if Customer has not subscribed to receive such notice, within sixty days of Upwork publishing the change. Upwork will then use commercially reasonable efforts to review and respond to Customer’s objection within thirty days of receipt of Customer’s objection. If Upwork does not respond to a Customer objection as described above, or cannot reasonably accommodate Customer’s objection, Customer may terminate the Agreement by providing written notice to Upwork. This termination right is Customer’s sole and exclusive remedy if Customer objects to any new Subprocessor.
Opportunity to Object to Subprocessor Changes. To the extent required by law, when any new Third Party Subprocessor is engaged during the term of the Agreement, Virsae will notify Customer of the engagement (including the name and location of the relevant Subprocessor and the activities it will perform) by updating the website listed in Section 5.2 (Information about Subprocessors). If Customer objects to such engagement in a written notice to Virsae within 15 days of being informed thereof on reasonable grounds relating to the protection of Personal Data, Customer and Virsae will work together in good faith to find a mutually acceptable resolution to address such objection. If the parties are unable to reach a mutually acceptable resolution within a reasonable timeframe using reasonable and good faith efforts, Customer may, as its sole and exclusive remedy, terminate the Agreement and cancel the Virsae Solution by providing written notice to Virsae.
Opportunity to Object to Subprocessor Changes. If within 15 days of receipt of the notice pursuant to Section 5(a) Customer notifies Provider in writing of any objections to the proposed appointment of any Subprocessor on reasonable grounds relating to the protection of Personal Data, Customer and Provider will work together in good faith to find a mutually acceptable resolution to address such objection or withholding. If the parties are unable to reach a mutually acceptable resolution within a reasonable timeframe, Customer may, as its sole and exclusive remedy, terminate the Agreement and cancel the Service by providing written notice to Provider and pay Provider for all amounts due and owing under the Agreement as of the date of such termination.
Opportunity to Object to Subprocessor Changes. If Customer objects to such engagement in a written notice to Assistiv on reasonable grounds relating to the protection of Personal Data, Customer and Assistiv will work together in good faith to find a mutually acceptable resolution to address such objection. If the parties are unable to reach a mutually acceptable resolution within a reasonable timeframe, Customer may, as its sole and exclusive remedy, terminate the Agreement by providing written notice to Assistiv.
Opportunity to Object to Subprocessor Changes. (a) When any new Third Party Subprocessor is engaged during the applicable Term, IRIS Connect will, at least 30 days before the new Third Party Subprocessor processes any Customer Data, inform Customer of the engagement (including the name and location of the relevant subprocessor and the activities it will perform) either by sending an email to the Notification Email Address or via the Admin Console.
(b) Customer may object to any new Third Party Subprocessor by terminating the applicable Agreement immediately upon written notice to IRIS Connect, on condition that Customer provides such notice within 90 days of being informed of the engagement of the subprocessor as described in Section 11.4(a). This termination right is Customer’s sole and exclusive remedy if Customer objects to any new Third Party Subprocessor. 20 Data Protection Team; Processing Records
20.1 IRIS Connect’s Data Protection Team
Opportunity to Object to Subprocessor Changes. 10.4.1 When any new Third Party Subprocessor is engaged during the Term, LearningBook will, at least 30 days before the new Third Party Subprocessor processes any Customer Data, inform Customer of the engagement (including the name and location of the relevant subprocessor and the activities it will perform) either by sending an email to the Key User Email Address.
10.4.2 In the event Customer objects to a new Third Party Subprocessor, as permitted in the preceding sentence, LearningBook will use reasonable efforts to make available to Customer a change in the Services or recommend a commercially reasonable change to
10.4.3 If LearningBook is unable to make available such change within a reasonable period of time, which shall not exceed thirty (30) days, Customer may terminate the applicable Order Form(s) with respect only to those Services which cannot be provided by LearningBook without the use of the objected-to new Sub-processor by providing written notice to LearningBook.
Opportunity to Object to Subprocessor Changes. Customer may, on reasonable and objective grounds, object to Xxxxx's use of a new Subprocessor by providing Evolv with written notice within fifteen (15) days after Xxxxx has provided notice to Customer as described herein with documentary evidence that reasonably shows that the Subprocessor does not or cannot comply with the requirements in this DPA or Data Protection Laws ("Objection"). In the event of an Objection, Customer and Evolv will work together in good faith to find a mutually acceptable resolution to address such Objection, including but not limited to reviewing additional documentation supporting the Subprocessor’s compliance with the DPA or Data Protection Laws. To the extent Customer and Evolv do not reach a mutually acceptable resolution within a reasonable timeframe, Evolv will use reasonable endeavors to make available to Customer a change in the Services or will recommend a commercially reasonable change to the Services to prevent the applicable Subprocessor from Processing Customer Personal Data. If Evolv is unable to make available such a change within a reasonable period of time, which shall not exceed thirty (30) days, Evolv and Customer shall escalate to their applicable executive or senior leadership to discuss the matter in good faith and determine an appropriate resolution and next steps.
