Common use of New Subprocessors Clause in Contracts

New Subprocessors. Docker’s use of Subprocessors is at its discretion, provided that: (a) Docker will notify Customer in advance (by email or such other means which Docker makes available to its customers) of any changes to the list of Subprocessors in place on the Effective Date (except for Emergency Replacements or deletions of Subprocessors without replacement). (b) If Customer has a legitimate reason that relates to the Subprocessors’ processing of Personal Data, Customer may object to Docker’s use of a Subprocessor, by notifying Docker in writing within thirty days after receipt of Docker’s notice. If Customer objects to the use of the Subprocessor, the parties will come together in good faith to discuss a resolution. Docker may choose to: (i) not use the Subprocessor or (ii) take the corrective steps requested by Customer in its objection and use the Subprocessor. If none of these options are reasonably possible and Customer continues to object for a legitimate reason, either party may terminate the Agreement on thirty days’ written notice. If Customer does not object within thirty days of receipt of the notice, Customer is deemed to have accepted the new Subprocessor. (c) If Customer’s objection remains unresolved sixty days after it was raised, and Docker has not received any notice of termination, Customer is deemed to accept the Subprocessor. (d) The list of Subprocessors current as of the Effective Date shall be set forth in Appendix 1.

New Subprocessors. Docker’s use of Subprocessors is at its discretion, provided that: (a) Docker will notify Customer in advance (by email or such other means which Docker makes available to its customers) of any changes to the list of Subprocessors in place on the Effective Date (except for Emergency Replacements or deletions of Subprocessors without replacement). (b) If Customer has a legitimate reason that relates to the Subprocessors’ processing of Personal Data, Customer may object to Docker’s use of a Subprocessor, by notifying Docker in writing within thirty days after receipt of Docker’s notice. If Customer objects to the use of the Subprocessor, the parties will come together in good faith to discuss a resolution. Docker may choose to: (i) not use the Subprocessor or (ii) take the corrective steps requested by Customer in its objection and use the Subprocessor. If none of these options are reasonably possible and Customer continues to object for a legitimate reason, either party may terminate the Agreement on thirty days’ written notice. If Customer does not object within thirty days of receipt of the notice, Customer is deemed to have accepted the new Subprocessor. (c) If Customer’s objection remains unresolved sixty days after it was raised, and Docker has not received any notice of termination, Customer is deemed to accept the Subprocessor. (d) The list of Subprocessors current as of the Effective Date shall be set forth in Appendix 1.

New Subprocessors. DockerHRMantra’s use of Subprocessors is at its discretion, provided that: (a) Docker HRMantra will notify Customer in advance (by email or such other means which Docker makes available to its customersby posting on xxx.XXXxxxxx.xxx) of any changes to the list of Subprocessors in place on the Effective Date (except for Emergency Replacements or deletions of Subprocessors without replacement). (b) If Customer has a legitimate reason that relates to the Subprocessors’ processing of Personal Data, Customer may object to DockerHRMantra’s use of a Subprocessor, by notifying Docker HRMantra in writing within thirty days after receipt of DockerHRMantra’s notice. If Customer objects to the use of the Subprocessor, the parties will come together in good faith to discuss a resolution. Docker HRMantra may choose to: (i) not use the Subprocessor or (ii) take the corrective steps requested by Customer in its objection and use the Subprocessor. If none of these options are reasonably possible and Customer continues to object for a legitimate reason, either party may terminate the Agreement on thirty days’ written notice. If Customer does not object within thirty days of receipt of the notice, Customer is deemed to have accepted the new Subprocessor. (c) If Customer’s objection remains unresolved sixty days after it was raised, and Docker HRMantra has not received any notice of termination, Customer is deemed to accept the Subprocessor. (d) The list of Subprocessors current as of the Effective Date shall be set forth in Appendix 1.

New Subprocessors. DockerCORESYSTEMS’s use of Subprocessors is at its discretion, provided that: (a) Docker CORESYSTEMS will notify Customer in advance (by email or such other means which Docker makes available to its customersby posting on the Support Portal) of any changes to the list of Subprocessors in place on the Effective Date (except for Emergency Replacements or deletions of Subprocessors without replacement). (b) If Customer has a legitimate reason that relates to the Subprocessors’ Subprocessors processing of Personal Data, Customer may object to DockerCORESYSTEMS’s use of a Subprocessor, by notifying Docker CORESYSTEMS in writing within thirty days after receipt of DockerCORESYSTEMS’s notice. If Customer objects to the use of the Subprocessor, the parties will come together in good faith to discuss a resolution. Docker CORESYSTEMS may choose to: (i) not use the Subprocessor or (ii) take the corrective steps requested by Customer in its objection and use the Subprocessor. If none of these options are reasonably possible and Customer continues to object for a legitimate reason, either party may terminate the Agreement on thirty days’ written notice. If Customer does not object within thirty days of receipt of the notice, Customer is deemed to have accepted the new Subprocessor. (c) If Customer’s objection remains unresolved sixty days after it was raised, and Docker CORESYSTEMS has not received any notice of termination, Customer is deemed to accept the Subprocessor. (d) The list of Subprocessors current as of the Effective Date shall be set forth in Appendix 1.