Common use of Opportunity to Object to Subprocessor Changes Clause in Contracts

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. (a) When any new Third Party Subprocessor is engaged during the applicable Term, Kitefaster IRIS Connect 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 applicable Agreement immediately upon written notice to KitefasterIRIS 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