Opportunity to Object to Subprocessor Changes Clause Samples
POPULAR SAMPLE Copied 6 times
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. 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 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) 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. 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 ▇▇▇▇-▇▇▇▇@▇▇▇▇▇▇.▇▇▇ 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. When ▇▇▇▇▇▇▇▇ engages any new Third Party Subprocessor after the effective date of the Agreement, ▇▇▇▇▇▇▇▇ will notify Client of the engagement (including the name and location of the relevant Subprocessor and the activities it will perform) by updating the Subprocessor Site or by other written means. If Client objects to such engagement in a written notice to Dashlane within 15 days after being informed of the engagement on reasonable grounds relating to the protection of Personal Data, Client and ▇▇▇▇▇▇▇▇ will work 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, Client may, as its sole and exclusive remedy, terminate the Agreement and cancel the Services by providing written notice to ▇▇▇▇▇▇▇▇ and pay Dashlane for all amounts due and owing under the Agreement as of the date of such termination.
Opportunity to Object to Subprocessor Changes. (a) When any new Third Party Subprocessor is engaged during the Term, Kitefaster 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) 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 Agreement immediately upon written notice to Kitefaster, 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. When any New Subprocessor is engaged during the Term, Company will inform the 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. Customer may object to any New Subprocessor by terminating for convenience immediately upon written notice to Company, on the condition that Customer provides such notice within 90 days of being informed of the engagement of the New Subprocessor as described in Section 11.1. This termination right is Customer’s sole and exclusive remedy if Customer objects to any new Third Party Subprocessor. CONTACTING COMPANY; PROCESSING RECORDS. Contacting Company. Customer may contact Company in relation to the exercise of its rights under these Data Processing Terms via email to ▇▇▇@▇▇▇▇▇▇.▇▇▇ or via such other means as may be provided by Company from time to time. Company will provide prompt and reasonable assistance with Customer queries Company receives via such means, and that relate to the processing of Customer Personal Data under the Agreement. Processing Records. Company will keep appropriate documentation of its processing activities as required by the GDPR. Customer acknowledges that Company is required under the GDPR to: (a) collect and maintain records of certain information, including: (i) the name and contact details of each processor and/or controller on behalf of which Company is acting and (if applicable) of such processor’s or controller's local representative and data protection officer, and (ii) if applicable under the Customer SCCs, Customer’s Supervisory Authority; and (b) make such information available to any Supervisory Authority. Accordingly, Customer will, where requested and as applicable to Customer, provide such information to Company upon request by Company and/or to Google Subprocessors upon request by Google Subprocessors via the user interface of the Services or via such other means as notified by Google Subprocessors, and will use such user interface or other means to ensure that all information provided is kept accurate and up-to-date. Controller Requests. If Company receives a request or instruction via the methods described in Section 12.1 (or any other method) from a third party purporting to be a controller of Customer Personal Data, Company will advise the third party to contact Customer. LIABILITY.
Opportunity to Object to Subprocessor Changes.
11.4.1. When any New Subprocessor is engaged during the Term, Acceleration will at least 14 days before the New Subprocessor processes any Client Personal Data, inform Client 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.
11.4.2. Client may object to any New Subprocessor by terminating the Agreement immediately upon written notice to Acceleration, on condition that Client provides such notice within 90 days of being informed of the engagement of the New Subprocessor as described in Section 11.4.1.