Software Destruction Sample Clauses

Software Destruction. Upon request by Tintri, Recipient will provide Tintri with written certification of Recipient’s discontinued use and destruction of all Software Applications and accompanying Documentation.
AutoNDA by SimpleDocs

Related to Software Destruction

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

  • Confidential Destruction PHI COUNTY discloses to CONTRACTOR or 5 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must be disposed of 6 through confidential means, such as cross cut shredding and pulverizing.

  • E10 Malicious Software E10.1 The Contractor shall, as an enduring obligation throughout the Contract Period, use the latest versions of anti-virus definitions available from an industry accepted anti-virus software vendor to check for and delete Malicious Software from the ICT Environment.

  • Complete Destruction In the event the Premises are completely destroyed by fire, explosion, the elements, a public enemy, Act of God, or other casualty or are so damaged as to render the entire Premises untenable, and the Premises cannot be repaired within 120 days, Company will give Authority immediate notice thereof, and Authority will be under no obligation to repair, replace, and reconstruct said Premises. In the event Authority elects not to repair, replace, and reconstruct said Premises, Authority will not be required to grant alternative premises and this Agreement and the obligations of the Parties hereunder will terminate.

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

  • Software Use Case Red Hat Enterprise Virtualization Supported on physical hardware solely to support virtual quests. Red Hat Enterprise Virtualization is designed to run and manage virtual instances and does not support user-space applications. Red Hat Enterprise Virtualization may be used as a virtual desktop infrastructure solution, however, the Subscription does not come with any software or support for the desktop operating system. You must purchase the operating system for each instance of a desktop or server separately.

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Malicious Software 12.1 The Supplier shall, as an enduring obligation throughout the Term, use the latest versions of anti-virus definitions available [from an industry accepted anti-virus software vendor] to check for and delete Malicious Software from the ICT Environment.

  • Embedded Software To the extent any goods contain Embedded Software (defined below) that is not Buyer’s Property, no title to such Embedded Software shall pass to Buyer, and Supplier shall grant Buyer, its customers and all other users a non-exclusive worldwide, irrevocable, perpetual, royalty-free right to use, load, install, execute, demonstrate, market, test, resell, sublicense and distribute such Embedded Software as an integral part of such goods or for servicing the goods (the “Buyer-Required License”). If such Embedded Software or any part thereof is owned by a third party, prior to delivery, Supplier shall obtain the Buyer-Required License from such third-party owner. “Embedded Software” means software necessary for operation of goods and embedded in and delivered as an integral part of goods.

Time is Money Join Law Insider Premium to draft better contracts faster.