Data Removal Clause Samples

Data Removal. 10.1 PATIENT REQUEST FOR WITHDRAWAL FROM THE MSBASE/MGBASE OBSERVATIONAL STUDY If a patient chooses to withdraw from the Study, they must notify the PI or the Centre Authority at the Centre where they were consented. The PI must then unenroll the patient record within their local data-entry software, which will stop prospective data collection. Previously uploaded data in relation to the patient will remain in the database.

Data Removal. Notwithstanding IBM's policy for the return or removal of Content, IBM shall not be required to remove any Client Provided Data from the Cloud Service to the extent such data has been made part of a transaction on the Cloud Service blockchain.

Data Removal. 10.1 PATIENT REQUEST FOR WITHDRAWAL FROM THE MSBASE/MGBASE OBSERVATIONAL STUDY If a patient chooses to withdraw from the Study, they must notify the PI or the Centre Authority at the Centre where they were consented. The PI must then unenroll the patient record within their local data-entry software, which will stop prospective data collection. Previously uploaded data in relation to the patient will remain in the database. 10.2 PATIENT REQUEST FOR COMPLETE REMOVAL OF DATA FROM THE MSBASE/MGBASE REGISTRY If a patient wishes to completely remove their data from either Registry, they must notify the Centre PI at the Centre where they were consented. The PI must inform the MSBase Operations Team in writing (including the patient’s MSBase ID) to ▇▇▇▇@▇▇▇▇▇▇.▇▇▇. The MSBase Operations Team will action the removal of the patient’s entire record, including all data relating to the patient, within 60 days and will notify the Centre PI when the action has been completed.

Data Removal. The Assuming Institution shall, prior to returning any Leased Data Management Equipment, and unless otherwise requested by the Receiver, (i) remove all data from the Leased Data Management Equipment and (ii) provide a written statement to the Receiver that all data has been removed in a manner that renders it unrecoverable. Module 1 – Whole Bank w/ Optional Shared Loss Agreements 24 Blue Ridge Savings Bank, Inc. Version 3.2 – Purchase and Assumption Agreement Asheville, North Carolina July 15, 2011

Data Removal. The Assuming Institution shall, prior to returning any automated teller machine to Receiver and unless otherwise requested by the Receiver, (i) remove all data from that automated teller machine and (ii) provide a written statement to the Receiver that all data has been removed in a manner that renders it unrecoverable.

Data Removal. If Seller or Purchaser is required to return any automated teller machine under the Primary P&A Agreement, Purchaser will return such automated teller machine directly to the Receiver or, if not possible, to Seller in the manner contemplated in Section 4.6(k) of the Primary P&A Agreement. Prior to returning any automated teller machine to Seller or the Receiver, and unless otherwise requested by Seller or the Receiver, Purchaser shall (1) remove all data from that automated teller machine and (2) provide a written statement to Seller and the Receiver that all data has been removed in a manner that renders it unrecoverable.

Data Removal. Beekeeper may, in its sole discretion, and upon its reasonable belief (a) remove any Customer Data, Third Party Application data, or Third Party Feature data that (i) contains a Virus; (ii) poses a threat to the security or stability of the Frontline Success System; (iii) is Inappropriate Content; or (iv) is in breach of the End User Terms; and (b) remove access of any Authorized End User which account has been associated to any of the aforementioned cases set-out in (a). Beekeeper will notify Customer of any data it has removed under this clause 7.5 (Data Removal). Customer will have the opportunity to contest the removal of the data at which time Beekeeper will consult with Customer, review the matter, and thereafter Beekeeper will make a final decision.

Data Removal. Without limiting Your other obligations in the XaaS Agreement or applicable law, You must ensure that, prior to removal by or return to Hitachi for any reason, all data is removed from such Product or Infrastructure. Hitachi takes no responsibility for data remaining on any Product or Infrastructure that is removed by or returned to Hitachi. You must defend, indemnify and hold Hitachi, its Affiliates and their respective Personnel harmless from and against any and all Losses that is caused directly or indirectly by Your failure to comply with this Section.

Data Removal. Upon request of a Respondent or Organization to delete or remove any Data, QA shall immediately provide the Company with written notice and comply with all required procedures. The Company shall not be required to delete or remove Data that (i) is not technically feasible;