CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION Sample Clauses

CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION. 7.1.1 ClickDimensions maintains security incident management policies and procedures specified in Security Documentation and, to the extent required under applicable Data Protection Laws and Regulations, 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 ClickDimensions or its Sub-processors of which ClickDimensions becomes aware (a “Customer Data Incident”). ClickDimensions shall make reasonable efforts to identify the cause of such Customer Data Incident and take those steps as ClickDimensions deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within ClickDimensions’ reasonable control. The obligations herein shall not apply to incidents that are caused by Customer or Customer’s users. 7.1.2 In the event ClickDimensions becomes aware of a Customer Data Incident, ClickDimensions shall notify Customer by email, without undue delay (and in no event greater than 48 hours), after having become aware of the occurrence. ClickDimensions will ensure that such notice complies with requirements under applicable Data Protection Laws and Regulations, including with respect to the timing and substance of such notice. Notwithstanding these requirements, such notification to Customer shall include: (i) a description of the nature of the Customer Data Incident, including, the categories and approximate number of Data Subjects concerned, the affected categories and approximate number of types of Processing of Personal Data; (ii) a description of the likely consequences of the Customer Data Incident; and (iii) a description of the measures taken or proposed to remedy the Customer Data Incident and, if necessary, the measures to mitigate or limit possible negative effects thereof. To the extent it is not possible to provide the foregoing information at the same time, the information may be provided in phases without further undue delay. 7.1.3 Taking into account the nature of Processing and the information available to ClickDimensions, ClickDimensions will provide assistance to Customer to enable Customer to fulfill its notification obligations to affected Data Subjects or relevant authorities in connection with a Customer Data Incident. At the written request of Customer, ClickDimensions shall provid...
AutoNDA by SimpleDocs
CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION. AudioCodes maintains security incident management policies and procedures specified in the Security and Privacy Documentation 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 transmitted, stored or otherwise Processed by AudioCodes or its Sub-processors of which AudioCodes becomes aware (a “Customer Data Incident”). AudioCodes shall make reasonable efforts to identify the cause of such Customer Data Incident and take those steps as AudioCodes deems necessary and reasonable to remediate the cause of such a Customer Data Incident to the extent the remediation is within AudioCodes reasonable control. The obligations herein shall not apply to incidents that are caused by Customer.
CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION. SFDC maintains security incident management policies and procedures specified in the Security, Privacy and Architecture Documentation 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 SFDC or its Sub-processors of which SFDC becomes aware (a “Customer Data Incident”). SFDC shall make reasonable efforts to identify the cause of such Customer Data Incident and take those steps as SFDC deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within SFDC’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 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. Spin Technology 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 Spin Technology or its Sub-processors (a “Customer Data Incident”). Spin Technology shall make reasonable efforts to identify the cause of such Customer Data Incident and take those steps as Spin Technology deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within Spin Technology’s reasonable control. The obligations herein shall not apply to incidents that are caused by Customer or Customer’s Authorized Users.
CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION. Braze maintains security incident management policies and procedures specified in the Security, Privacy and Architecture Datasheet and shall notify Customer without undue delay after becoming aware of a Personal Data Breach. Braze shall provide information to Customer necessary to enable Customer to comply with its obligations under Data Protection Laws and Regulations. The content of such communication to Customer will (i) include the nature of Processing and the information available to Braze, and (ii) take into account that under applicable Data Protection Laws and Regulations, Customer may need to notify regulators or individuals of the following: (a) a description of the nature of the Personal Data Breach including, where possible, the categories and approximate number of individuals concerned and the categories and approximate number of Personal Data records concerned; (b) a description of the likely consequences of the Personal Data Breach; and (c) a description of the measures taken or proposed to be taken to address the Personal Data Breach, including, where appropriate, measures to mitigate its possible adverse effect. Braze shall make commercially reasonable efforts to identify the cause of such Personal Data Breach and take those steps as Braze deems necessary and reasonable in order to remediate the cause of such Personal Data Breach to the extent the remediation is within Braze’s reasonable control. The obligation to remediate the cause of a Personal Data Breach shall not apply to Personal Data Breaches that are caused by Customer or Customer’s Users.
CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION. Zadara maintains security incident management policies and procedures specified in Security Documentation and, to the extent required under applicable Data Protection Laws and Regulations, shall notify Customer without undue delay after becoming aware of the actual unauthorized disclosure of or access to Customer Data, or compromise of Zadara’s systems that Zadara determines is reasonably likely to result in such disclosure or access, caused by failure of Zadara's security measures and excluding any unauthorized disclosure or access that is caused by Customer or its users, including Customer or its End Users' failure to adequately secure equipment or accounts (a “Customer Data Incident”). Zadara shall make reasonable efforts to identify the cause of such Customer Data Incident and take those steps as Zadara deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within Zadara’s reasonable control. Zadara may limit the scope of, or refrain from delivering, any disclosures to the extent reasonably necessary to avoid compromising the integrity of Zadara's security, an ongoing investigation, or any Customer’s or end user's data.
AutoNDA by SimpleDocs
CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION. Thunderhead maintains security incident management policies and procedures specified in the Security and Privacy Documentation and shall notify Customer without undue delay after becoming aware of the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to any Personal Data comprised within the Customer Data, which is transmitted, stored or otherwise Processed by Thunderhead or its Sub-processors of which Thunderhead becomes aware (a “Customer Data Incident”). Thunderhead shall make reasonable efforts to identify the cause of such Customer Data Incident and take those steps as Thunderhead deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within Thunderhead’s reasonable control. The obligations herein shall not apply to incidents that are caused by Customer or Customer’s Users or any Third Party Application.
CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION. 7.1 Cohesity shall notify Customer without undue delay after becoming aware of the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Personal Data in Cohesity’s or its Sub-Processors’ possession of which Cohesity becomes aware (a “Customer Data Incident”). Cohesity shall make reasonable efforts to identify the cause of such Customer Data Incident and take those steps as Cohesity deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within Cohesity’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. PandaDoc shall maintain commercially reasonable security incident management policies and procedures specified in the Security Practices. PandaDoc shall notify Customer without undue delay of any breach relating to Personal Data (within the meaning of Applicable Privacy and Data Protection Laws) of which PandaDoc becomes aware and which may require a notification to be made to a Supervisory Authority or Data Subject under Applicable Privacy and Data Protection Laws or which PandaDoc is required to notify to Customer under Applicable Privacy and Data Protection Laws (a “Customer Data Incident”). Taking into account the nature of Processing and the information available to PandaDoc and in accordance with the Agreement, PandaDoc shall provide commercially reasonable cooperation and assistance in identifying the cause of such Customer Data Incident and take commercially reasonable steps to remediate the cause to the extent the remediation is within PandaDoc’s control. The obligations herein shall not apply to incidents that are caused by Customer, Customer’s authorized users and/or any non-PandaDoc products and/or services.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!