Common use of CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION Clause in Contracts

CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION. MIRAGE maintains security incident management policies and procedures specified in the schedule 2 - Technical and Organizational Measures and shall, notify Customer without undue delay after becoming aware of the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data, including Personal Data, transmitted, stored or otherwise Processed by MIRAGE or its Sub- processors of which MIRAGE becomes aware (a “Customer Data Incident”). MIRAGE shall make reasonable efforts to identify the cause of such Customer Data Incident and take those steps as MIRAGE deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within MIRAGE’s reasonable control. The obligations herein shall not apply to incidents that are caused by Customer or Customer’s Users.

CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION. MIRAGE Enverus maintains security incident management policies and procedures specified in the schedule 2 - Technical Security Documentation and Organizational Measures and shall, shall notify Customer without undue delay after becoming aware of the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data, including Personal Data, transmitted, stored or otherwise Processed by MIRAGE Enverus or its Sub- Sub-processors of which MIRAGE Enverus becomes aware (a “Customer Data Incident”). MIRAGE Enverus shall make reasonable efforts to identify the cause of such Customer Data Incident and take those such steps as MIRAGE Enverus deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within MIRAGEEnverus’s reasonable control. The obligations herein shall not apply to incidents that are caused by Customer or Customer’s Users.

CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION. MIRAGE Instatus maintains security incident management policies and procedures specified in the schedule 2 - Technical Security, Privacy and Organizational Measures Architecture Documentation and the Agreement. Instatus shall, ,notify Customer without undue delay delay, and in compliance with applicable laws, after becoming aware of the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data, including Personal Data, transmitted, stored or otherwise Processed by MIRAGE Instatus or its Sub- Sub-processors of which MIRAGE Instatus becomes aware (a “Customer Data Incident”). MIRAGE Instatus shall make reasonable efforts to identify the cause of such Customer Data Incident and take those steps as MIRAGE Instatus deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to Incidentto the extent the remediation is within MIRAGEInstatus’s reasonable control. The obligations herein shall not apply to incidents that are caused by Customer or Customer’s Invited Users.

CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION. MIRAGE Appiphony maintains security incident management policies and procedures specified in the schedule 2 - Technical and Organizational Measures and shall, shall notify Customer without undue delay after becoming aware of the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data, including Personal Data, transmitted, stored or otherwise Processed by MIRAGE Appiphony or its Sub- Sub-processors of which MIRAGE Appiphony becomes aware (a “Customer Data Incident”). MIRAGE Appiphony shall make reasonable efforts to identify the cause of such Customer Data Incident and take those such steps as MIRAGE Appiphony deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within MIRAGEAppiphony’s reasonable control. The obligations herein shall not apply to incidents that are caused by Customer or Customer’s Users.