Data Destruction Verification Sample Clauses

The Data Destruction Verification clause requires a party to confirm that all data, particularly sensitive or confidential information, has been securely deleted or destroyed upon request or at the end of a contract. This typically involves providing written certification or evidence that data has been erased from all systems, backups, and storage devices, and may include audits or third-party verification. The core purpose of this clause is to ensure that no residual data remains that could pose a security or privacy risk, thereby protecting both parties from potential data breaches or unauthorized disclosures.
Data Destruction Verification a. Upon completion of the project/work the data that has been transferred to the contracted entity will be destroyed. b. Proof that the transferred data (any metadata, compiled/calculated results, etc.) has been destroyed will be provided with a certified data destruction report from reputable digital data sanitation software. c. Person responsible for the data destruction (please list): i. Name: ii. Title: iii. Email: iv. Telephone: d. Estimated destruction date of the complete data set:
View SourceView Similar (14)

Related to Data Destruction Verification

  • Data Destruction When no longer needed, all County PHI or PI must be cleared, purged, or destroyed consistent with NIST Special Publication 800-88, Guidelines for Media Sanitization such that the PHI or PI cannot be retrieved.

  • E-VERIFICATION The Vendor represents and warrants that it will ensure its compliance with the Mississippi Employment Protection Act of 2008, and will register and participate in the status verification system for all newly hired employees. Mississippi Code Annotated §§71-11-1 et seq. The term “employee” as used herein means any person that is hired to perform work within the State of Mississippi. As used herein, “status verification system” means the Illegal Immigration Reform and Immigration Responsibility Act of 1996 that is operated by the United States Department of Homeland Security, also known as the E-Verify Program, or any other successor electronic verification system replacing the E-Verify Program. Vendor agrees to maintain records of such compliance. Upon request of the State and after approval of the Social Security Administration or Department of Homeland Security when required, Vendor agrees to provide a copy of each such verification. Vendor further represents and warrants that any person assigned to perform services hereafter meets the employment eligibility requirements of all immigration laws. The breach of this agreement may subject Vendor to the following: termination of this contract for goods or services and ineligibility for any state or public contract in Mississippi for up to three (3) years with notice of such cancellation/termination being made public; the loss of any license, permit, certification, or other document granted to Vendor by an agency, department or governmental entity for the right to do business in Mississippi for up to one (1) year; or,

  • Third Party Verification 4.8.1 The SPD shall be further required to provide entry to the site of the Power Project (from which power under this Agreement is being made available) free of all encumbrances at all times during the Term of the Agreement to SECI and a third Party nominated by any Indian Governmental Instrumentality for inspection and verification of the works being carried out by the SPD at the site of the Power Project. The SPD shall provide full support to SECI and/or the third party in this regard. 4.8.2 The third party may verify the construction works/operation of the Project being carried out by the SPD and if it is found that the construction works/operation of the Power Project is not as per the Prudent Utility Practices, it may seek clarifications from SPD or require the works to be stopped or to comply with the instructions of such third party.

  • Return/Destruction of PHI 15.1 Business Associate in connection with the expiration or termination of the contract or grant shall return or destroy, at the discretion of the Covered Entity, all PHI received from Covered Entity or created or received by Business Associate on behalf of Covered Entity pursuant to this contract or grant that Business Associate still maintains in any form or medium (including electronic) within thirty (30) days after such expiration or termination. Business Associate shall not retain any copies of the PHI. Business Associate shall certify in writing for Covered Entity (1) when all PHI has been returned or destroyed and (2) that Business Associate does not continue to maintain any PHI. Business Associate is to provide this certification during this thirty (30) day period. 15.2 Business Associate shall provide to Covered Entity notification of any conditions that Business Associate believes make the return or destruction of PHI infeasible. If Covered Entity agrees that return or destruction is infeasible, Business Associate shall extend the protections of this Agreement to such PHI and limit further uses and disclosures of such PHI to those purposes that make the return or destruction infeasible for so long as Business Associate maintains such PHI. This shall also apply to all Agents and Subcontractors of Business Associate.

  • Termination and Data Destruction Upon Project Close-out, the Requester and Approved Users agree to destroy all copies, versions, and Data Derivatives of the dataset(s) retrieved from NIH-designated controlled-access databases, on both local servers and hardware, and if cloud computing was used, delete the data and cloud images from cloud computing provider storage, virtual and physical machines, databases, and random access archives, in accord with the NIH Security Best Practices for Controlled-Access Data Subject to the NIH Genomic Data Sharing (GDS) Policy. However, the Requester may retain these data as necessary to comply with any institutional policies (e.g., scientific data retention policy), law, and scientific transparency expectations for disseminated research results, and/or journal policies. A Requester who retains data for any of these purposes continues to be a ▇▇▇▇▇▇▇ of the data and is responsible for the management of the retained data in accordance with the NIH Security Best Practices for ControlledAccess Data Subject to the NIH Genomic Data Sharing (GDS) Policy, and any institutional policies. Any retained data may only be used by the PI and Requester to support the findings (e.g., validation) resulting from the research described in the DAR that was submitted by the Requester and approved by NIH. The data may not be used to answer any additional research questions, even if they are within the scope of the approved Data Access Request, unless the Requester submits a new DAR and is approved by NIH to conduct the additional research. If a Requester retains data for any of these purposes, the relevant portions of Terms 4, 5, 6, 7, 8, and 12 remain in effect after termination of this Data Use Certification Agreement. These terms remain in effect until the data is destroyed.