Confidential Document Destruction Service Sample Clauses

Confidential Document Destruction Service. If requested by Agency, Contractor shall provide confidential document destruction service at the drop off event(s). Contractor shall provide adequate equipment and staffing necessary for the event and shall ensure full destruction of confidential documents and other materials delivered by Customers at the site of the event. This service shall be provided by Contractor at no additional cost to Customers and shall not bill Agency for such services.
AutoNDA by SimpleDocs
Confidential Document Destruction Service. If requested by Agency, Contractor shall provide confidential document destruction service at the drop off event(s). Contractor willshall provide adequate equipment and staffing necessary for the event and shall ensure full destruction of confidential documents and other materials delivered by Customers at the site of the event. This service willshall be provided by Contractor at no additional cost to the Agency or Customers. 1396 5.14 WEEK-LONG AGENCY-WIDE BULKY ITEMS COLLECTION SERVICE EVENT 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406

Related to Confidential Document Destruction Service

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

  • Confidential System Information HHSC prohibits the unauthorized disclosure of Other Confidential Information. Grantee and all Grantee Agents will not disclose or use any Other Confidential Information in any manner except as is necessary for the Project or the proper discharge of obligations and securing of rights under the Contract. Grantee will have a system in effect to protect Other Confidential Information. Any disclosure or transfer of Other Confidential Information by Xxxxxxx, including information requested to do so by HHSC, will be in accordance with the Contract. If Grantee receives a request for Other Confidential Information, Xxxxxxx will immediately notify HHSC of the request, and will make reasonable efforts to protect the Other Confidential Information from disclosure until further instructed by the HHSC. Grantee will notify HHSC promptly of any unauthorized possession, use, knowledge, or attempt thereof, of any Other Confidential Information by any person or entity that may become known to Grantee. Grantee will furnish to HHSC all known details of the unauthorized possession, use, or knowledge, or attempt thereof, and use reasonable efforts to assist HHSC in investigating or preventing the reoccurrence of any unauthorized possession, use, or knowledge, or attempt thereof, of Other Confidential Information. HHSC will have the right to recover from Grantee all damages and liabilities caused by or arising from Grantee or Grantee Agents’ failure to protect HHSC’s Confidential Information as required by this section. IN COORDINATION WITH THE INDEMNITY PROVISIONS CONTAINED IN THE UTC, Xxxxxxx WILL INDEMNIFY AND HOLD HARMLESS HHSC FROM ALL DAMAGES, COSTS, LIABILITIES, AND EXPENSES (INCLUDING WITHOUT LIMITATION REASONABLE ATTORNEYS’ FEES AND COSTS) CAUSED BY OR ARISING FROM Grantee OR Grantee AGENTS FAILURE TO PROTECT OTHER CONFIDENTIAL INFORMATION. Grantee WILL FULFILL THIS PROVISION WITH COUNSEL APPROVED BY HHSC.

  • Retention or destruction of Confidential Information If Network Rail or the Train Operator, as the case may be, has not received a request to return any Confidential Information to the other party under and within the time limits specified in Clause 14.3, it may destroy or retain such Confidential Information.

  • Return or Destruction of Confidential Information If an Interconnection Party provides any Confidential Information to another Interconnection Party in the course of an audit or inspection, the providing Interconnection Party may request the other party to return or destroy such Confidential Information after the termination of the audit period and the resolution of all matters relating to that audit. Each Interconnection Party shall make Reasonable Efforts to comply with any such requests for return or destruction within ten days of receiving the request and shall certify in writing to the other Interconnection Party that it has complied with such request.

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

  • Authorized User’s Statement of Work A competitive Mini-Bid is required for every transaction under this Centralized Contract. An Authorized User must prepare a detailed Statement of Work using Appendix F, Attachment 1, Mini-Bid Template. The Authorized User must distribute the Mini-Bid to all qualified Vendors per Lot(s) (unless a Vendor has removed itself from consideration via the Appendix F, Attachment 5, Mini-Bid Participation Interest Template). Contact information, organized by Lot, will be available on the OGS website for this Contract. An Authorized User shall conduct its Mini-Bid in accordance with the requirements set forth in Appendix F, Attachment 2, How to Use this Contract. The following terms and conditions shall apply to each Mini-Bid issued by an Authorized User:  An Authorized User may require the execution of unique forms, such as Confidentiality Non- Disclosure agreements; and  An Authorized User is required to make tentative award and non-award notifications to each Contractor who submitted a response to the Mini-Bid. Additionally, the minimum time, excluding the date of release, between issuance of the Mini-Bid by the Authorized User to the Mini-Bid Opening is as follows:  Xxx 0 Xxxx-Xxxx: Xxxx (0) Xxxxxxxx Xxxx  Xxx 0 Mini-Bids: Ten (10) Business Days

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

  • CONFIDENTIAL & PROPRIETARY INFORMATION The parties may provide technical information, documentation and expertise to each other that is either (1) marked as being confidential or, (2) if delivered in oral form is summarized in writing within 10 working days and identified as being confidential (“Confidential Information”). The receiving party shall for a period of five (5) years from the date of disclosure (i) hold the disclosing party’s Confidential Information in strict confidence, and (ii), except as previously authorized in writing by the disclosing party, not publish or disclose the disclosing party’s Confidential Information to anyone other than the receiving party’s employees on a need-to-know basis, and (iii) use the disclosing party’s Confidential Information solely for performance of this Contract. The foregoing requirement shall not apply to any portion of a party’s Confidential Information which (a) becomes publicly known through no wrongful act or omission on the part of the receiving party; (b) is already known to the receiving party at the time of the disclosure without similar nondisclosure obligations; (c) is rightfully received by the receiving party from a third party without similar nondisclosure obligations; (d) is approved for release by written authorization of the disclosing party; (e) is clearly demonstrated by the receiving party to have been independently developed by the receiving party without access to the disclosing party’s Confidential Information; or (f) is required to be disclosed by order of a court or governmental body or by applicable law, provided that the party intending to make such required disclosure shall promptly notify the other party of such intended disclosure in order to allow such party to seek a protective order or other remedy.

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

  • Destruction of Confidential Information Upon the written request of the disclosing Party, the receiving Party shall cease using and arrange for the destruction of all copies of any Confidential Information then in the receiving Party’s possession or under such Party’s control. The receiving Party agrees to dispose of the Confidential Information in such a manner that the information cannot be read or reconstructed after destruction. Upon the written request of the disclosing Party, the receiving Party shall certify in writing that it has complied with the obligations set forth in this paragraph.

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