PRIVACY INCIDENT Sample Clauses

PRIVACY INCIDENT. “Privacy Incident” shall mean any use or disclosure of Protected Health Information that is not permitted by the Agreement or that is in violation of the Privacy Rule and shall include a breach of Protected Health Information as the term “breach” is defined in 45 CFR § 164.402.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
PRIVACY INCIDENT. A privacy incident occurs when there is a loss of control, compromise, unauthorized disclosure, unauthorized acquisition, unauthorized access, or failure to secure PII in usable form, whether physical or electronic, or when authorized users access survivor/registrant PII for an unauthorized purpose. The term encompasses both suspected and confirmed incidents involving PII which raise a reasonable risk of harm.
Sample 1Sample 2Sample 3See All (4)
PRIVACY INCIDENT. The loss of control, compromise, unauthorized disclosure, unauthorized acquisition, or any similar occurrence where (1) a person other than the authorized user accesses or potentially accesses PII or (2) an authorized user accesses or potentially accesses PII for an unauthorized purpose. The term encompasses both suspected and confirmed incidents involving PII, whether intentional or inadvertent, which raises a reasonable risk of harm.
Sample 1Sample 2Sample 3
PRIVACY INCIDENT. ‌ In the event of a Privacy Incident, the Vendor must: (a) immediately notify Newcrest (providing full details and ongoing updates as available); (b) where the Privacy Incident is or may be an Eligible Data Breach of either party, follow the relevant guidance issued by the Office of the Australian Information Commissioner in conjunction with this clause 30; (c) conduct a prompt and thorough investigation and assessment of the Privacy Incident; (d) co-operate with Newcrest’s requests in respect of investigating, responding to, reporting and remediating the Privacy Incident; and‌ (e) not make or publish any statement or communication concerning the Privacy Incident, including contacting any relevant regulatory authority, without obtaining Newcrest’s prior written consent or instruction, unless Newcrest fails to provide its consent or instruction within a reasonable time and the statement or communication is required by Law.
Sample 1
PRIVACY INCIDENT. Company shall notify Customer immediately in writing in the event that: (i) any Customer’s Personal Data is disclosed by Company or its Agents, in violation of this Agreement or applicable laws or legislation pertaining to privacy or data security, (ii) Company or its Agents discovers, is notified of, or suspects that unauthorized access, acquisition, disclosure or use of Customer’s Personal Data may have occurred (whereby, subsection (i) and/or (ii) shall be a “Privacy Incident”). Company shall cooperate fully in the investigation of the Privacy Incident, indemnify and reimburse Customer for any and all damages, losses, fees or costs incurred as a result of such incident, and remedy any harm or potential harm caused by such incident.
Sample 1
PRIVACY INCIDENT. A privacy incident occurs when there is a loss of control, compromise, unauthorized disclosure, unauthorized acquisition, unauthorized access, or failure to secure personal information in usable form, whether physical or electronic, or when authorized users access survivor personal information for an unauthorized purpose. The term encompasses both suspected and confirmed incidents involving personal information which raise a reasonable risk of harm.
Sample 1

Related to PRIVACY INCIDENT

  • 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.

  • 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.

  • 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 Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

  • 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.

  • 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.

  • Data Breach In the event of an unauthorized release, disclosure or acquisition of Student Data that compromises the security, confidentiality or integrity of the Student Data maintained by the Provider the Provider shall provide notification to LEA within seventy-two (72) hours of confirmation of the incident, unless notification within this time limit would disrupt investigation of the incident by law enforcement. In such an event, notification shall be made within a reasonable time after the incident. Provider shall follow the following process: (1) The security breach notification described above shall include, at a minimum, the following information to the extent known by the Provider and as it becomes available: i. The name and contact information of the reporting LEA subject to this section. ii. A list of the types of personal information that were or are reasonably believed to have been the subject of a breach. iii. If the information is possible to determine at the time the notice is provided, then either (1) the date of the breach, (2) the estimated date of the breach, or (3) the date range within which the breach occurred. The notification shall also include the date of the notice. iv. Whether the notification was delayed as a result of a law enforcement investigation, if that information is possible to determine at the time the notice is provided; and v. A general description of the breach incident, if that information is possible to determine at the time the notice is provided. (2) Provider agrees to adhere to all federal and state requirements with respect to a data breach related to the Student Data, including, when appropriate or required, the required responsibilities and procedures for notification and mitigation of any such data breach. (3) Provider further acknowledges and agrees to have a written incident response plan that reflects best practices and is consistent with industry standards and federal and state law for responding to a data breach, breach of security, privacy incident or unauthorized acquisition or use of Student Data or any portion thereof, including personally identifiable information and agrees to provide XXX, upon request, with a summary of said written incident response plan. (4) LEA shall provide notice and facts surrounding the breach to the affected students, parents or guardians. (5) In the event of a breach originating from XXX’s use of the Service, Provider shall cooperate with XXX to the extent necessary to expeditiously secure Student Data.

  • Data Breaches 4.1 The Data Processor does not guarantee that its security measures will be effective under all conditions. If the Data Processor discovers a data breach within the meaning of Article

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