Breach Notifications. A breach is, generally, an impermissible use or disclosure under the Privacy Rule that compromises the security or privacy of the protected health information. Following a breach of unsecured protected health information, Fidelis will provide notification of the breach to affected individuals, the Secretary of the Department of Health and Human Services, and, in certain circumstances, to the media, as required by law or regulations. Fidelis will provide this notice in written form without unreasonable delay and no later than 60 days following the discovery of the breach. Fidelis will provide a description of the types of information that were involved in the breach, the steps affected individuals should take to protect themselves from potential harm, a brief description of what Fidelis is doing to investigate the breach, mitigate the harm, and prevent further breaches, as well as contact information for Fidelis. If you believe your privacy rights have been violated, you may file a complaint with Fidelis or the Secretary of the U.S. Department of Health and Human Services. You may file a complaint with Fidelis by writing to 00-00 Xxxxxx Xxxxxxxxx, Xxxx Xxxx, New York 11374.
Breach Notifications. If any of your personal data is stolen, lost or illegally accessed - known as a personal data breach - we would inform you as well as the respective data protection agencies as to such accidents without undue delay. We would also inform you directly if there are serious risks related to your personal data or privacy due to the personal data breach. We will do our best to minimize any possible risks related to personal data breach.
Breach Notifications. In the event of a Security Breach, Databricks shall provide written notice to Customer without undue delay and in no event later than seventy-two (72) hours after becoming aware of the Security Breach and will provide updates to Customer, including the type of data affected and the identity of affected person(s) as soon as such information becomes known to Databricks. Databricks will reasonably cooperate with Customer as required to fulfill Customer’s obligations under Applicable Data Protection Laws. Databricks shall take measures and actions appropriate and reasonable to remedy or mitigate the effects of the Security Breach.
Breach Notifications. Covered Entity shall be responsible for making notifications to individuals affected by any Breach of which Business Associate provides notice to Covered Entity.
Breach Notifications. In respect of any personal data breach involving the Client Personal Data, Com Laude shall, without undue delay, notify Client of the breach and provide Client with details of the breach. Com Laude will take all reasonable steps necessary to mitigate the effects and minimise any damage resulting from such personal data breach.
Breach Notifications. TCP will promptly report to Client any unauthorized access to Client Data within TCP’s or its Subprocessors’ systems upon discovery and in accordance with applicable data breach notification laws. TCP will use diligent efforts to promptly remedy any breach of security that permitted such unauthorized access. TCP’s notification of or response to any security incident under this Section 3.2 shall not be construed as an acknowledgment by TCP of any fault or liability with respect to such security incident.
Breach Notifications. 7.1 Plecto maintains security incident management policies and procedures and shall, notify Subscriber without undue delay after becoming aware of the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Subscriber Data, including Personal Data, transmitted, stored or otherwise Processed by Plecto or its Sub-processors of which Plecto becomes aware (a “Customer Data Incident”).
7.2 Plecto shall make reasonable efforts to identify the cause of such Customer Data Incident and take those steps as Plecto deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within Xxxxxx’s reasonable control. The obligations herein shall not apply to incidents that are caused by Subscriber or Subscriber’s Users.
7.3 Plecto are obligated, to provide the Subscriber with information about such breaches as described in 8.1, within 48 hours of the breach, so that the Subscriber can inform the supervisory authority within 72 hours, as required by Article 33 (1).
Breach Notifications. 9.1. The Parties agree to accord assistance and necessary support in case of any data breach.
9.2. The Party who becomes aware of the data breach shall notify the other Parties as soon as possible, but no later than 24 hours from the indication of the data breach. Such Party provides other Parties with all of the details of the breach.
9.3. The Party who becomes aware of the data breach shall determine whether the supervisory authority needs to be notified. The Party who becomes aware of the data breach may involve other Parties to assist in the risk assessment process and jointly determine whether the supervisory authority needs to be notified, if it is necessary.
9.4. The notification of the data breach to the supervisory authority shall be made in accordance with procedure established by the Article 33 of the GDPR and include the following, namely:
a. a description of the nature of the personal data breach including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;
b. the name and contact details of the data protection officer and other contact point where more information can be obtained;
c. a description of the likely consequences of the personal data breach;
d. a description of the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects. Such notification shall be submitted by the Party within 72 hours from the identification of the data breach.
9.5. In case where the Party may not provide the whole aforementioned information at once due to the carrying out the complicated investigation, it shall notify thereof the supervisory authority. This does not prevent the Party from providing further information, if it becomes aware of additional relevant details of the data breach in question.
9.6. The Party who becomes aware of the data breach shall determine whether the data subjects need to be notified. The Party who becomes aware of the data breach may involve other Parties to assist in the risk assessment process and jointly determine whether the data subjects need to be notified, if it is needed.
9.7. The Party who becomes aware of the data breach shall communicate without undue delay to the data subjects concerned. Such notification shall be made by the Party within 72 hours from the identification of the data breach. In the eve...
Breach Notifications. A party must notify the disclosing party in writing, giving full details known to it immediately, when it becomes aware of any actual, suspected, likely or threatened:
(a) breach by any person of any obligation in relation to the Confidential Information; or
(b) theft, loss, damage or unauthorised access, use or disclosure of or to any Confidential Information.
Breach Notifications. 7.1 Fenerum maintains security incident management policies and procedures and shall, notify Subscriber without undue delay after becoming aware of the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Subscriber Data, including Personal Data, transmitted, stored or otherwise Processed by Fenerum or its Sub-processors of which Fenerum becomes aware (a “Customer Data Incident”).
7.2 Fenerum shall make reasonable efforts to identify the cause of such Customer Data Incident and take those steps as Fenerum deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within Fenerum’s reasonable control. The obligations herein shall not apply to incidents that are caused by Subscriber or Subscriber’s Users.
7.3 Fenerum isobligated, to provide the Subscriber with information about such breaches as described in 8.1, within 48 hours of the breach, so that the Subscriber can inform the supervisory authority within 72 hours, as required by Article 33 (1).
