Procurement Sensitive Information Sample Clauses

Procurement Sensitive Information. Contractor further agrees that it will not cause or encourage any employee to disclose, publish, divulge, release, or make known in any manner or to any extent, to any individual, other than an authorized Government employee, any procurement-sensitive information gained while in connection with fulfilling the employee’s responsibilities at the CDC. For purposes of this agreement, procurement-sensitive information includes, but is not limited to, all information in Statements of Work (SOW), Requests for Contract (RFC), and Requests for Proposal (RFP); Responses to RFPs, including questions from potential offerors; non-public information regarding procurements; all documents, conversations, discussions, data, correspondence, electronic mail (e-mail), presentations, or any other written or verbal communications relating to, concerning, or affecting proposed or pending solicitations or awards; procurement data; contract information plans; strategies; source selection information and documentation; offerors’ identities; technical and cost data; the identity of government personal involved in the solicitation; the schedule of key technical and procurement events in the award determination process; and any other information that may provide an unfair competitive advantage to a contractor or potential contractor if improperly disclosed to them, or any of their employees. Contractor understands and agrees that employee access to any procurement-sensitive information may create a conflict of interest which will preclude contractor from becoming a competitor for any acquisition(s) resulting from this information. Therefore, if an employee participates in any discussions relating to procurement-sensitive information, assists in developing any procurement-sensitive information, or otherwise obtains any procurement- sensitive information during the course of performing duties at the CDC, contractor understands and agrees that contractor are be excluded from competing for any acquisition(s) resulting from this information.
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs
Procurement Sensitive Information. Neither the Company, any of its Subsidiaries nor any of their respective Company Persons is in unauthorized receipt or possession of any competitor or government proprietary or procurement sensitive information under circumstances where there is reason to believe that such receipt or possession thereof would violate applicable Law. Neither the Company or any of its Subsidiaries has hired or retained any employee of any Governmental Entity under circumstances where there is reason to believe that such hiring or retention would violate applicable Law. None of the Company, any of its Subsidiaries or any of their respective Company Persons has engaged in communications for the purpose of hiring or retaining any employee of any Governmental Entity under circumstances where there is reason to believe that such hiring or retention would violate applicable Law (it being understood and agreed that, in the case of the Subsidiaries of the Company, for periods prior to their acquisition by the Company, the Company is making the representation and warranty set forth in this sentence only to the Company’s Knowledge).
Sample 1Sample 2Sample 3
Procurement Sensitive Information. I further agree that unless I have prior written permission from the USDA and 2M, I will not disclose, publish, divulge, release, or make known in any manner or to any extent, to any individual other than an authorized Government employee, any procurement-sensitive information gained in connection with the performance of my responsibilities to the USDA and 2M Research. I specifically agree not to disclose any non-public, procurement-sensitive information to employees of my company or any other organization unless so authorized in writing by the USDA and 2M. For purposes of this agreement, procurement-sensitive information includes, but is not limited to, all information in Statements of Work (SOW), Requests for Contract (RFC), and Requests for Proposal (RFP); Responses to RFPs, including questions from potential offerors; non-public information regarding procurements; all documents, conversations, discussions, data, correspondence, electronic mail (e-mail), presentations, or any other written or verbal communications relating to, concerning, or affecting proposed or pending solicitations or awards; procurement data; contract information plans; strategies; source selection information and documentation; offerors’ identities; technical and cost data; the identity of government personal involved in the acquisition; the schedule of key technical and procurement events in the award determination process; and any other information that may provide an unfair competitive advantage to a contractor or potential contractor if improperly disclosed to them, or any of their employees.
Sample 1

Related to Procurement Sensitive Information

  • Sensitive Information Information that requires special precautions to protect from unauthorized use, access, disclosure, modification, loss, or deletion. Sensitive Information may be either Public Information or Confidential Information. It is information that requires a higher than normal assurance of accuracy and completeness. Thus, the key factor for Sensitive Information is that of integrity. Typically, Sensitive Information includes records of agency financial transactions and regulatory actions.

  • Handling Sensitive Personal Information and Breach Notification A. As part of its contract with HHSC Contractor may receive or create sensitive personal information, as section 521.002 of the Business and Commerce Code defines that phrase. Contractor must use appropriate safeguards to protect this sensitive personal information. These safeguards must include maintaining the sensitive personal information in a form that is unusable, unreadable, or indecipherable to unauthorized persons. Contractor may consult the “Guidance to Render Unsecured Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals” issued by the U.S. Department of Health and Human Services to determine ways to meet this standard. B. Contractor must notify HHSC of any confirmed or suspected unauthorized acquisition, access, use or disclosure of sensitive personal information related to this Contract, including any breach of system security, as section 521.053 of the Business and Commerce Code defines that phrase. Contractor must submit a written report to HHSC as soon as possible but no later than 10 business days after discovering the unauthorized acquisition, access, use or disclosure. The written report must identify everyone whose sensitive personal information has been or is reasonably believed to have been compromised. C. Contractor must either disclose the unauthorized acquisition, access, use or disclosure to everyone whose sensitive personal information has been or is reasonably believed to have been compromised or pay the expenses associated with HHSC doing the disclosure if: 1. Contractor experiences a breach of system security involving information owned by HHSC for which disclosure or notification is required under section 521.053 of the Business and Commerce Code; or 2. Contractor experiences a breach of unsecured protected health information, as 45 C.F.R. §164.402 defines that phrase, and HHSC becomes responsible for doing the notification required by 45 C.F.R. §164.404. HHSC may, at its discretion, waive Contractor's payment of expenses associated with HHSC doing the disclosure.

  • Sensitive data Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.

  • Market Information Exchange and Xxxxxxxxxx brochures and research are often provided as trading tools. In addition, a CTS Platform may also contain certain market information. Customer acknowledges that: (a) any information Xxxxxxxxxx’x research department may communicate to Customer does not constitute an offer to sell or a solicitation of any offer to buy any Contract; (b) such recommendations and information, although based upon information obtained from sources believed by Xxxxxxxxxx to be reliable, are incidental to Xxxxxxxxxx’x business as a futures commission merchant, may be incomplete and not subject to verification, and will not serve as the primary basis for any decision by Customer; (c) Xxxxxxxxxx makes no representation, warranty, or guarantee as to, and shall not be responsible for, the accuracy or completeness of any information or trading recommendation furnished to Customer; (d) recommendations to Customer as to any particular transaction at any given time may differ among Xxxxxxxxxx’x personnel due to diversity in analysis of fundamental and technical factors and may vary from any standard recommendation made by Xxxxxxxxxx in its market letters or otherwise; and (e) Xxxxxxxxxx has no obligation or responsibility to update any market recommendations or information it communicates to Customer. Customer understands that Xxxxxxxxxx and its officers, directors, affiliates, stockholders, representatives, or associated persons may have positions in and may intend to buy or sell Contracts which are the subject of market recommendations furnished to Customer, and that the market positions of Xxxxxxxxxx or any such officer, director, affiliate, stockholder, representative, or associated person may or may not be consistent with the recommendations furnished to Customer by Xxxxxxxxxx.

  • Client Information Protected Health Information in any form including without limitation, Electronic Protected Health Information or Unsecured Protected Health Information (herein “PHI”);

  • Verizon OSS Information 8.5.1 Subject to the provisions of this Section 8 and Applicable Law, Verizon grants to Reconex a non-exclusive license to use Verizon OSS Information. 8.5.2 All Verizon OSS Information shall at all times remain the property of Verizon. Except as expressly stated in this Section 8, Reconex shall acquire no rights in or to any Verizon OSS Information. 8.5.2.1 The provisions of this Section 8.5.2 shall apply to all Verizon OSS Information, except (a) Reconex Usage Information, (b) CPNI of Reconex, and (c) CPNI of a Verizon Customer or a Reconex Customer, to the extent the Customer has authorized Reconex to use the Customer Information. 8.5.2.2 Verizon OSS Information may be accessed and used by Reconex only to provide Telecommunications Services to Reconex Customers. 8.5.2.3 Reconex shall treat Verizon OSS Information that is designated by Verizon, through written or electronic notice (including, but not limited to, through the Verizon OSS Services), as “Confidential” or “Proprietary” as Confidential Information of Verizon pursuant to Section 10 of the Agreement. 8.5.2.4 Except as expressly stated in this Section 8, this Agreement does not grant to Reconex any right or license to grant sublicenses to other persons, or permission to other persons (except Reconex’s employees, agents or contractors, in accordance with Section 8.5.2.5 below, to access, use or disclose Verizon OSS Information. 8.5.2.5 Reconex’s employees, agents and contractors may access, use and disclose Verizon OSS Information only to the extent necessary for Reconex’s access to, and use and disclosure of, Verizon OSS Information permitted by this Section 8. Any access to, or use or disclosure of, Verizon OSS Information by Reconex’s employees, agents or contractors, shall be subject to the provisions of this Agreement, including, but not limited to, Section 10 of the Agreement and Section 8.5.2.3 above. 8.5.2.6 Reconex’s license to use Verizon OSS Information shall expire upon the earliest of: (a) the time when the Verizon OSS Information is no longer needed by Reconex to provide Telecommunications Services to Reconex Customers; (b) termination of the license in accordance with this Section 8; or (c) expiration or termination of the Agreement. 8.5.2.7 All Verizon OSS Information received by Reconex shall be destroyed or returned by Reconex to Verizon, upon expiration, suspension or termination of the license to use such Verizon OSS Information. 8.5.3 Unless sooner terminated or suspended in accordance with the Agreement or this Section 8 (including, but not limited to, Section 2.2 of the Agreement and Section 8.6.1 below), Reconex’s access to Verizon OSS Information through Verizon OSS Services shall terminate upon the expiration or termination of the Agreement. 8.5.3.1 Verizon shall have the right (but not the obligation) to audit Reconex to ascertain whether Reconex is complying with the requirements of Applicable Law and this Agreement with regard to Reconex’s access to, and use and disclosure of, Verizon OSS Information. 8.5.3.2 Without in any way limiting any other rights Verizon may have under the Agreement or Applicable Law, Verizon shall have the right (but not the obligation) to monitor Reconex’s access to and use of Verizon OSS Information which is made available by Verizon to Reconex pursuant to this Agreement, to ascertain whether Reconex is complying with the requirements of Applicable Law and this Agreement, with regard to Reconex’s access to, and use and disclosure of, such Verizon OSS Information. The foregoing right shall include, but not be limited to, the right (but not the obligation) to electronically monitor Reconex’s access to and use of Verizon OSS Information which is made available by Verizon to Reconex through Verizon OSS Facilities. 8.5.3.3 Information obtained by Verizon pursuant to this Section 8.5.3.3 shall be treated by Verizon as Confidential Information of Reconex pursuant to Section 10 of the Agreement; provided that, Verizon shall have the right (but not the obligation) to use and disclose information obtained by Verizon pursuant to this Section 8.5.3.3 to enforce Verizon’s rights under the Agreement or Applicable Law.

  • Patient Information Each Party agrees to abide by all laws, rules, regulations, and orders of all applicable supranational, national, federal, state, provincial, and local governmental entities concerning the confidentiality or protection of patient identifiable information and/or patients’ protected health information, as defined by any other applicable legislation in the course of their performance under this Agreement.

  • Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.

  • Alert Information As Alerts delivered via SMS, email and push notifications are not encrypted, we will never include your passcode or full account number. You acknowledge and agree that Alerts may not be encrypted and may include your name and some information about your accounts, and anyone with access to your Alerts will be able to view the contents of these messages.

  • Regulatory Information (a) All the notaries at De Pinna LLP are regulated through the Faculty Office of the Archbishop of Canterbury. Its address is The Faculty Office, 0 Xxx Xxxxxxxxx, Xxxxxxxxxxx, Xxxxxx XX0X 0XX, its telephone: 000 0000 0000, and it can be reached by email at xxxxxxx.xxxxxx@0xxxxxxxxxxxx.xxx. It also has a website at xxx.xxxxxxxxxxxxx.xxx.xx. (b) We are required to comply with the rules of professional conduct and other regulatory arrangements of the Master of the Faculties, the sole regulator of notarial activities under the Legal Services Act 2007. Information about those rules and regulations may be found at xxxx://xxx.xxxxxxxxxxxxx.xxx.xx/notary/i-am-a-notary/notaries-rules-regulations/. (c) We comply with the Code of Practice published by the Master of the Faculties: xxxx://xxx.xxxxxxxxxxxxx.xxx.xx/notary/code-of-practice.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!