Data Incidents Sample Clauses

Data Incidents. If Apple becomes aware that Personal Data has been altered, deleted, or lost as a result of any unauthorized access to the Service (a “Data Incident”), Apple will notify Institution without undue delay if required by law, and Apple will take reasonable steps to minimize harm and secure the data. Notification of, or response to, a Data Incident by Apple will not be construed as an acknowledgment by Apple of any responsibility or liability with respect to a Data Incident. Institution is responsible for complying with applicable incident notification laws and fulfilling any third-party obligations related to Data Incident(s). Apple will not access the contents of Personal Data in order to identify information subject to any specific legal requirements.

Data Incidents. Apple will (i) notify Institution, without undue delay and as required by law, if Apple becomes aware that there has been a breach of security of the Service leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Institution’s Personal Data (“a Data Incident”); and (ii) take reasonable steps to minimize harm and secure Institution’s Personal Data. You are responsible for providing Apple with Institution’s updated contact information for such notification purposes. Apple will also assist Institution to the extent it involves Personal Data that Apple has access to in connection with the Service, to ensure Institution complies with its obligations to provide notice of Data

Data Incidents. Manager agrees to immediately notify Walmart’s Emergency Operations Center by phone (479.277.1001) of any reasonably suspected or actual loss of data or breach or compromise of its Security Program which has or may result in the loss or unauthorized access, disclosure, use or acquisition of Walmart Information (including hard copy records) or otherwise presents a potential threat to any Walmart systems (“Data Incident”). While the initial phone notice may be in summary form, a comprehensive written notice should be given within 48 hours to Walmart’s Chief Privacy Officer, 702 SW 8th Street, Bentonville, AR and its Chief Information Security Officer, 805 Moberly Lane, Bentonville, AR. The notice shall summarize in reasonable detail the nature and scope of the Data Incident known to Manager at the time of the notice (including each data element type that relates to a customer or Walmart employee, if any) and the corrective action already taken or to be taken by Manager. The notice shall be timely supplemented in the detail reasonably requested by Walmart, inclusive of relevant forensic reports to the extent not privileged (in the event of privileged reports, Manager shall provide a reasonably detailed summary of findings relevant to the Data Incident). Manager shall promptly take all necessary and advisable corrective actions, and shall cooperate fully with Walmart in all reasonable efforts to mitigate the adverse affects of Data Incident and to prevent its recurrence. Manager acknowledges that it is solely responsible for the confidentiality and security of Walmart Information in its possession, custody or control, or for which Manager is otherwise responsible under the Agreement, and shall hold Walmart harmless from any suspected or actual breach or other compromise of Walmart Information caused by or attributable to Manager. The parties will collaborate on whether any notice of breach is required to be given to any person, and if so, the content of that notice. Walmart will designate signatory to the notice. Manager will bear all costs of the notice of breaches caused by or attributable to Manager. If Walmart reasonably determines that the Data Incident is likely to have substantial adverse impact on Walmart’s relationship with its customers or associates or otherwise substantially harm its reputation, Walmart may suspend the Services provided by Manager under this Agreement or any other contract.

Data Incidents. 15.1 In the event of any loss or corruption of, or damage to, any Data, the Supplier shall (without prejudice to any other remedies that may be available to CEWA under this Agreement or otherwise) promptly: (a) notify CEWA; (b) after the incident causing the loss, corruption or other damage (Data Incident), restore or procure the restoration of that Data to the last available backup (or other copy) of that Data; and (c) take all further available steps to restore or procure the restoration of the Data to its former state immediately prior to the Data incident (or, if requested by CEWA, have a third party nominated by CEWA do so at the cost of the Supplier). 15.2 The Supplier must take such steps as are necessary to ensure that it can comply with clause 15.1 in the event of a Data Incident. 15.3 To the extent that the Supplier is unable to restore any lost, corrupt, or damaged Data in accordance with clause 15.1, CEWA may recover from the Supplier any costs and expenses that CEWA reasonably incurs in taking its own action (including engaging third parties) to restore that Data.

Data Incidents. (i) If the Supplier becomes aware or suspects that: (A) it or a subcontractor (or any of their respective Personnel) is using or disclosing, or has used or disclosed, Personal Information in contravention of this clause 19 (Data Contravention); (B) there has been a Data Breach; or (C) CFS Data or Personal Information has been lost in circumstances where unauthorised access to, or unauthorised disclosure of, that CFS Data or Personal Information may occur (Loss of Data), (each, a Data Incident), then the Supplier must: (D) immediately (but in any case, within 24 hours of it first becoming aware of such a Data Incident or beginning to suspect that such Data Incident has occurred) notify CFS as soon as it becomes so aware or has reason to suspect the Data Incident; (E) without delay, provide CFS with full details of, and assist CFS in investigating, such actual or suspected Data Incident (including all relevant information about the processes, procedures, protocols, and security practices and procedures used in the provision of the Goods and/or Services); (F) at CFS’s request, conduct an expeditious assessment of any actual or suspected Data Breach; (G) co-operate with CFS in any investigation in relation to, and the circumstances surrounding, such actual or suspected Data Incident; (H) provide CFS with access to and copies of relevant records and information, as requested by CFS; (I) use all reasonable efforts to prevent a recurrence of any actual Data Breach; and (J) comply with any direction from CFS with respect to mitigating and remedying any actual Data Incident or any of the matters set out in this clause 19(g). (ii) The Supplier must not do, or fail to do, anything which amounts to or causes a Data Incident.

Data Incidents. If Google becomes aware of a Data Incident, Google will promptly notify Customer of the Data Incident, and take reasonable steps to minimize harm and secure Customer Data. Notification(s) of any Data Incident(s) will be delivered to the Notification Email Address provided by Customer in connection with the Agreement or, at Google’s discretion, by direct communication (e.g., by phone call or an in-person meeting). Customer acknowledges that it is solely responsible for ensuring the contact information given for purposes of the Notification Email Address is current and valid, and for fulfilling any third party notification obligations. Customer agrees that “Data Incidents” do not include: (i) unsuccessful access attempts or similar events that do not compromise the security or privacy of Customer Data, including pings, port scans, denial of service attacks and other network attacks on firewalls or networked systems; or (ii) accidental loss or disclosure of Customer Data caused by Customer’s use of the Services or Customer’s loss of account authentication credentials. Google’s obligation to report or respond to a Data Incident under this Section will not be construed as an acknowledgement by Google of any fault or liability with respect to the Data Incident.

Data Incidents. Upon becoming aware of a Data Incident, we will notify you promptly and without undue delay, and will take reasonable steps to minimize harm and secure Personal Data. Any notifications that we send you pursuant to this Section 4.2 will be sent to your Notification Email Address and will describe, to the extent possible and/or known to Upscope, the details of the Data Incident, the steps we have taken to mitigate the potential risks, and any suggestions we have for you to minimize the impact of the Data Incident. We will not assess the contents of any Personal Data in order to identify information that may be subject to specific legal requirements. You are solely responsible for complying with any incident notification laws that may apply to you, and to fulfilling any third-party notification obligations related to any Data Incident(s). Our notification of or response to a Data Incident under this Section will not constitute an acknowledgement of fault or liability with respect to the Data Incident.

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. Caphyon will make reasonable efforts to implement and enhance an appropriate security program as well as organizational measures, ensuring the security and confidentiality of Personal Data subject to this DPA. As the Processor, should we become aware of a Data Incident with an impact on Personal Data Processing, we will notify the Controller regarding the incident in a timely manner, no later than 72 hours, as required by the Data Protection Legislation in force. As the Controller, it is your responsibility to provide information reasonably sufficient and up to date to allow ▇▇▇▇▇▇▇ to contact you, such as an email address or telephone number.