Common use of Data Incidents Clause in Contracts

Data Incidents. 3.2.1. If ▇▇▇▇▇▇▇ becomes aware of a Data Incident, Algolia will: (a) notify Subscriber of the Data Incident without undue delay after becoming aware of the Data Incident; and (b) promptly take reasonable steps to minimize harm and secure Subscriber Data. 3.2.2. Notifications made pursuant to this section will describe, to the extent possible, details of the Data Incident, including steps taken to mitigate the potential risks and, as applicable, steps Algolia recommends Subscriber to take to address the Data Incident. 3.2.3. Notification(s) of any Data Incident(s) will be delivered to Subscriber in accordance with the “Manner of Giving Notices” Section of the Agreement or, at Algolia’s discretion, by direct communication (for example, by phone call or an in-person meeting). Subscriber is solely responsible for ensuring that any contact information, including notification email address, provided to Algolia is current and valid. 3.2.4. Algolia will not assess the contents of Subscriber Data in order to identify information subject to any specific legal requirements. Subscriber is solely responsible for complying with incident notification laws applicable to Subscriber and fulfilling any third-party notification obligations related to any Data Incident(s). 3.2.5. Algolia’s notification of or response to a Data Incident under this Section 3.2 (Data Incidents) will not be construed as an acknowledgement by ▇▇▇▇▇▇▇ of any fault or liability with respect to the Data Incident.

Data Incidents. 3.2.1. If ▇▇▇▇▇▇▇ Algolia becomes aware of a Data Incident, Algolia will: (a) notify Subscriber of the Data Incident without undue delay after becoming aware of the Data Incident; and (b) promptly take reasonable steps to minimize harm and secure Subscriber Data. 3.2.2. Notifications made pursuant to this section will describe, to the extent possible, details of the Data Incident, including steps taken to mitigate the potential risks and, as applicable, steps Algolia recommends Subscriber to take to address the Data Incident. 3.2.3. Notification(s) of any Data Incident(s) will be delivered to Subscriber in accordance with the “Manner of Giving Notices” Section of the Agreement or, at Algolia’s discretion, by direct communication (for example, by phone call or an in-person meeting). Subscriber is solely responsible for ensuring that any contact information, including notification email address, provided to Algolia is current and valid. 3.2.4. Algolia will not assess the contents of Subscriber Data in order to identify information subject to any specific legal requirements. Subscriber is solely responsible for complying with incident notification laws applicable to Subscriber and fulfilling any third-party notification obligations related to any Data Incident(s). 3.2.5. Algolia’s notification of or response to a Data Incident under this Section 3.2 (Data Incidents) will not be construed as an acknowledgement by ▇▇▇▇▇▇▇ Algolia of any fault or liability with respect to the Data Incident.