Opportunity to Object to Subprocessor Changes Sample Clauses

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.
AutoNDA by SimpleDocs
Opportunity to Object to Subprocessor Changes.  (a) When any New Third Party Subprocessor is engaged during the applicable Term, Google 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 applicable 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 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.
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 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).
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. Part B
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.
AutoNDA by SimpleDocs
Opportunity to Object to Subprocessor Changes a. When any New Third Party Subprocessor is engaged during the Term, Enonic 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.
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.
Opportunity to Object to Subprocessor Changes. When any new Third Party Subprocessor is engaged during the Term, Blinkfire Analytics will, at least 30 days before the new Third Party Subprocessor processes any Customer Personal Data, notify Customer of the engagement (including the name and location of the relevant Subprocessor and the activities it will perform). Customer may object to any new Third Party Subprocessor by providing written notice to Blinkfire Analytics within ten (10) business days of being informed of the engagement of the Third Party Subprocessor as described above. In the event Customer objects to a new Third Party Subprocessor, Customer and Blinkfire Analytics 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 Blinkfire Analytics.
Time is Money Join Law Insider Premium to draft better contracts faster.