Privacy Incidents Sample Clauses

Privacy Incidents. If Xxxxxx XX becomes aware of any accidental, unauthorized or unlawful destruction, loss, alteration, or disclosure of, or access to the personal data that Travis CI processes in the course of providing the Services (a "Security Breach"), Xxxxxx XX will notify Customer without undue delay after having become aware of it and: i. provide Customer with a detailed description of the Security Breach; the type of data that was the subject of the Security Breach; and the identity of each affected person, as soon as such information can be collected or otherwise becomes available (as well as periodic updates to this information and any other information Customer may reasonably request relating to the Security Breach); ii. take action immediately, at Xxxxxx CI's own expense, to investigate the Security Breach and to identify, prevent and mitigate the effects of the Security Breach and to carry out any recovery or other action necessary to remedy the Security Breach; and iii. not release or publish any filing, communication, notice, press release, or report concerning the Security Breach without Customer's prior written approval except where Xxxxxx XX is required by Applicable Law to make such disclosure prior to obtaining Customer’s written consent.
Sample 1
AutoNDA by SimpleDocs
Privacy Incidents. IP.1 Networks AB shall notify the DC without unnecessary delay after having been informed of a personal data incident. The notification shall describe the nature of the personal data incident, including, if possible, the categories of and the approximate number of registered people involved, as well as the categories and the approximate number of personal data items concerned. If, and to the extent, that it is not possible to provide the information simultaneously, the information may be provided in parts, without unnecessary further delay. IP.1 Networks AB shall assist the DC and provide documentation of all personal data incidents, including the circumstances surrounding the personal data incident, its effects and the corrective actions taken.
Sample 1Sample 2
Privacy Incidents. If Gurock becomes aware of any accidental, unauthorised or unlawful destruction, loss, alteration, or disclosure of, or access to the personal data that Gurock processes in the course of providing the Services (a "Security Breach"), Gurock will notify Customer without undue delay after having become aware of it and: (i. provide Customer (as soon as possible) with a detailed description of the Security Breach; the type of data that was the subject of the Security Breach; and the identity of each affected person, as soon as such information can be collected or otherwise becomes available (as well as periodic updates to this information and any other information Customer may reasonably request relating to the Security Breach); (ii. take action immediately, at Gurock's own expense, to investigate the Security Breach and to identify, prevent and mitigate the effects of the Security Breach and to carry out any recovery or other action necessary to remedy the Security Breach; and (iii. not release or publish any filing, communication, notice, press release, or report concerning the Security Breach without Customer's prior written approval except where Gurock is required by Applicable Law to make such disclosure prior to obtaining Customer’s written consent.
Sample 1
Privacy Incidents. Without limiting any other term of this Agreement, if a Privacy Incident occurs, then the Participant must: immediately notify the Department; and do all things required by the Department in relation to that Privacy Incident.
Sample 1
Privacy Incidents. If CopperEgg becomes aware of any accidental, unauthorised or unlawful destruction, loss, alteration, or disclosure of, or access to the personal data that CopperEgg processes in the course of providing the Services (a "Security Breach"), CopperEgg will notify Customer without undue delay after having become aware of it and: i. provide Customer (as soon as possible) with a detailed description of the Security Breach; the type of data that was the subject of the Security Breach; and the identity of each affected person, as soon as such information can be collected or otherwise becomes available (as well as periodic updates to this information and any other information Customer may reasonably request relating to the Security Breach); ii. take action immediately, at CopperEgg's own expense, to investigate the Security Breach and to identify, prevent and mitigate the effects of the Security Breach and to carry out any recovery or other action necessary to remedy the Security Breach; and iii. not release or publish any filing, communication, notice, press release, or report concerning the Security Breach without Customer's prior written approval except where CopperEgg is required by Applicable Law to make such disclosure prior to obtaining Customer’s written consent.
Sample 1
Privacy Incidents. 5.1 Counterparty shall train all of Counterparty's Representatives that Process Personal Information to recognize and respond to Privacy Incidents. In the event of a Privacy Incident, Counterparty shall comply with all obligations in the information Security Schedule related to Incidents except that Counterparty shall also provide notice to Company promptly by electronic mail at xxxxxxx@xxxxx.xxx, and xxxx@xxxxx.xxx but in no event later than 24 hours, after Counterparty or its Representatives discovered or became aware of a Privacy Incident. All other terms and conditions in the Information Security Schedule related to Incidents shall apply mutatis mutandis to Privacy Incidents. Without limiting the foregoing, Counterparty shall reasonably cooperate and coordinate with Company concerning Company's investigation, enforcement, monitoring, document preparation, notification requirements and reporting concerning Privacy Incidents, which may include facilitating the delivery of notice of any Privacy Incidents (in a manner and format specified by Company) on Company's behalf and at Company's discretion to: (i) individuals whose Personal Information was or may have reasonably been exposed,
Sample 1
Privacy Incidents. 5.1. Provider shall train all of Provider’s Representatives that Process Personal Information to recognize and respond to Privacy Incidents. In the event of a Privacy Incident, Provider shall comply with all obligations in the information Security Schedule related to Incidents except that Provider shall also provide notice to Company promptly by electronic mail at xxxxxxx@xxxxx.xxx, and xxxx@xxxx.xxx but in no event later than twenty-four (24) hours, after Provider or its Representatives discovered or became aware of a Privacy Incident. All other terms and conditions in the Information Security Schedule related to Incidents shall apply mutatis mutandis to Privacy Incidents. Without limiting the foregoing, Provider shall reasonably cooperate and coordinate with Company concerning Company’s investigation, enforcement, monitoring, document preparation, notification requirements and reporting concerning Privacy Incidents, which may include facilitating the delivery of notice of any Privacy Incidents (in a manner and format specified by Company) on Company's behalf and at Company's discretion to: (i) individuals whose Personal Information was or may have reasonably been exposed, (ii) governmental authorities, and/or (iii) the media.
Sample 1
AutoNDA by SimpleDocs
Privacy Incidents. If Baltsoft becomes aware of any accidental, unauthorised or unlawful destruction, loss, alteration, or disclosure of, or access to the personal data that Baltsoft processes in the course of providing the Services (a "Security Breach"), Baltsoft will notify Customer without undue delay after having become aware of it and: i. provide Customer (as soon as possible) with a detailed description of the Security Breach; the type of data that was the subject of the Security Breach; and the identity of each affected person, as soon as such information can be collected or otherwise becomes available (as well as periodic updates to this information and any other information Customer may reasonably request relating to the Security Breach); ii. take action immediately, at Baltsoft's own expense, to investigate the Security Breach and to identify, prevent and mitigate the effects of the Security Breach and to carry out any recovery or other action necessary to remedy the Security Breach; and iii. not release or publish any filing, communication, notice, press release, or report concerning the Security Breach without Customer's prior written approval except where Baltsoft is required by Applicable Law to make such disclosure prior to obtaining Customer’s written consent.
Sample 1
Privacy Incidents. 5.1. Provider shall train all of Provider’s Representatives that Process Personal Information to recognize and respond to Privacy Incidents. In the event of a Privacy Incident, Provider shall:  immediately conduct a reasonable investigation of the reasons for and circumstances surrounding such Privacy Incident;  take all necessary actions to prevent, contain, and mitigate the impact of, such Privacy Incident;  without limiting Provider’s notification obligations under the Agreement, provide notice to Company promptly by electronic mail at xxxxxxxxxxxxx@xxxxx.xxx, but in no event later than twenty-four (24) hours, after Provider or its Representatives discovered or became aware of a Privacy Incident ("Incident Notice"). This Incident Notice shall contain at a minimum the following information: a) Description of the Privacy Incident, including information related to what (if any) Personal Information was the subject of or affected by the Privacy Incident; b) Actions taken by the Provider to remediate the Privacy Incident and any countermeasures implemented by Provider to prevent future Privacy Incidents; c) The name and contact information of Provider’s Representative that can act as a liaison between Company and Provider; and d) Other relevant information (including indicators of compromise), if any, that can help Company protect itself from the Privacy Incident;  collect and preserve all evidence concerning the discovery, cause, vulnerability, exploit, remedial actions and impact related to such Privacy Incident;  at Company's request, provide Company with: (i) periodic written status reports concerning mitigation and remediation activities related to each Privacy Incident and (ii) any documents and information reasonably requested by Company related to such Privacy Incident; and  reasonably cooperate and coordinate with Company concerning Company’s investigation, enforcement, monitoring, document preparation, notification requirements and reporting concerning Privacy Incidents, which may include facilitating the delivery of notice of any Privacy Incidents (in a manner and format specified by Company) on Company's behalf and at Company's discretion to: (i) individuals whose Personal Information was or may have reasonably been exposed, (ii) governmental authorities, and/or (iii) the media.
Sample 1

Related to Privacy Incidents

  • Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

  • Error Incident An Error Incident is a single or series of NAV Errors that results from the same act, omission, or use of incorrect data. NAV Errors will be corrected as follows: · If an NAV Error is less than ½ of 1% of NAV and results in a Net Benefit, the fund will retain the benefit. · If an NAV Error is less than ½ of 1% of NAV and results in a Net Loss, the Net Loss will be paid to the fund by the party responsible for causing the NAV Error. · In the case of a Material NAV Error, shareholder transactions/accounts will be corrected/ reprocessed at the corrected (restated) NAV, subject to a $10 per-account correction minimum threshold; any residual Net Benefit after correction of shareholder accounts will be retained by the fund and any residual Net Loss (resulting from uncorrected accounts below the $10 minimum threshold) will be paid to the fund by the party responsible for causing the error. If an NAV error is not caused by either the fund accounting agent or TRP, both TRP and the fund accounting agent will provide all reasonable assistance to the fund in its attempt to recover all costs from the responsible third party. · Notwithstanding any contractual provisions to the contrary, to the extent a NAV Error was caused by the actions or omissions of the fund’s accounting agent, any Net Loss or residual Net Loss equal to $5,000 or less that results from the same Error Incident will be paid by the accounting agent. TRP will be responsible for summarizing and reporting to the funds’ Audit Committee or Trust Company’s Board (or designated committee), as applicable, all NAV Errors related to the funds/trusts in conjunction with other relevant error statistics on a quarterly basis. The report will include corrected NAV Errors as well as the aggregate effect of any uncorrected NAV Errors. The report will also include information about shareholder accounts that were corrected in the discretion of TRP in the case of an NAV Error that is not a Material NAV Error. The funds’ Audit Committee and the Trust Company’s Board shall have the authority to adjust these procedures with respect to the funds and trusts, respectively, to the extent necessary or desirable to address NAV Errors by providing notice thereof to TRP and the fund’s accounting agent.

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

  • Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.

  • Security Incident Reporting A security incident occurs when CDA information assets are or reasonably believed to have been accessed, modified, destroyed, or disclosed without proper authorization, or are lost, or stolen. Subrecipient must comply with CDA’s security incident reporting procedures located at xxxxx://xxx.xxxxx.xx.xxx/ProgramsProviders/#Resources.

  • Significant Incidents In addition to notifying the appropriate authorities, Grantee will submit notice to the SUD email box, XxxxxxxxxXxxxx.Xxxxxxxxx@xxxx.xxxxx.xx.xx and Substance Use Xxxxxxxx@xxxx.xxxxx.xx.xx significant incidents involving substantial disruption of Grantee’s program operation or affecting or potentially affecting the health, safety or welfare of the System Agency funded clients or participants within three (3) calendar days of discovery.

  • Breaches and Security Incidents During the term of the Agreement, CONTRACTOR 27 agrees to implement reasonable systems for the discovery of any Breach of unsecured DHCS PI and PII 28 or security incident. CONTRACTOR agrees to give notification of any beach of unsecured DHCS PI 29 and PII or security incident in accordance with subparagraph F, of the Business Associate Contract, 30 Exhibit B to the Agreement.

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

  • Behaviour No obscene or insulting language or disorderly behaviour shall be permitted. This includes any form of entertainment that may be considered lewd or inappropriate for a public place or that may offend or cause embarrassment to others.

  • Notification of personal data breach 1. In case of any personal data breach, the data processor shall, without undue delay after having become aware of it, notify the data controller of the personal data breach. 2. The data processor’s notification to the data controller shall, if possible, take place within 24 hours after the data processor has become aware of the personal data breach to enable the data controller to comply with the data controller’s obligation to notify the personal data breach to the competent supervisory authority, cf. Article 33

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!