Termination and Data Destruction Sample Clauses
The 'Termination and Data Destruction' clause outlines the obligations of parties to delete or return confidential or sensitive data upon the end or termination of an agreement. Typically, this clause specifies the timeframe and method for destroying or returning data, and may require written confirmation that all copies have been removed from systems and backups. Its core function is to protect sensitive information after the business relationship ends, ensuring that data is not retained or misused, and thereby mitigating risks related to data privacy and security.
POPULAR SAMPLE Copied 2 times
Termination and Data Destruction. A Project Close-out must be completed when an approved project is completed. Upon Project Close-out, the Requester and Approved Users agree to destroy all copies, versions, and Data Derivatives of the data retrieved from NIH-designated data repositories, 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, and databases in accord with the NIH Security Best
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.
Termination and Data Destruction. (a) Upon Research Project close-out, Approved User agrees to destroy all copies, versions, and data derivatives of the dataset(s) retrieved from Accessclinicaldata@NIAID 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.
(b) Data retained 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 for the purpose of supporting the findings (e.g., validation) resulting from the research described in the DAR will be considered to be part of the approved Research Project. The NIAID DUA terms of agreement will remain effective prior to Research Project close-out, including for any time that the Data are retained for validation purposes.
Termination and Data Destruction. Upon Project Close-out, the Recipient and Recipient’s PI agree to destroy all copies, and versions, of any 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.