Controlled Government Data Sample Clauses

The Controlled Government Data clause defines how government-owned or government-controlled data is to be handled within the context of an agreement. It typically sets out requirements for the storage, access, processing, and protection of such data, often mandating compliance with specific laws, regulations, or security standards. For example, it may require that data be stored on servers located within the country or restrict access to authorized personnel only. The core function of this clause is to ensure that sensitive government data is managed securely and in accordance with legal and regulatory obligations, thereby mitigating risks related to unauthorized disclosure or misuse.
Controlled Government Data. The Disclosing Party's Controlled Government Data, if any, will be identified in a separate technical document.
Controlled Government Data. The Disclosing Party’s Controlled Government Data, if any, will be identified in a separate technical document. 4. The following software and related Data will be provided to Partner under a separate Software Usage Agreement: None
Controlled Government Data. None The Disclosing Party's Controlled Government Data, if any, will be identified in a separate technical document.
Controlled Government Data. The Disclosing Party’s Controlled Government Data, if any, will be identified in a separate technical document. NASA software and related Data will be provided to Partner under a separate Software Usage Agreement (SUA). Partner shall use and protect the related Data in accordance with this Article. Unless the SUA authorizes retention, or Partner enters into a license under 37 C.F.R. Part 404, the related Data shall be disposed of as NASA directs: None
Controlled Government Data. Arc jet 24-inch nozzle geometry data will be provided to Partner upon request for a period of up to two (2) years, not to exceed the duration of this Annex (expiration 4/13/2024); after which time, Partner shall certify to the Technical Point of Contact that it has destroyed or returned all copies. Additional Disclosing Party's Controlled Government Data, if any, will be identified in a separate document.
Controlled Government Data. LAR-18341-1 and LAR-18341-1-CON Tri-Rotor Aircraft Capable of Vertical Takeoff and Landing and Transitioning to Forward Flight.
Controlled Government Data. As marked.
Controlled Government Data. The Disclosing Party’s Controlled Government Data, if any, will be identified in a separate technical document. d. Notwithstanding ▇.4., NASA software and related Data will be provided to Partner under a separate Software Usage Agreement (SUA). Partner shall use and protect the related Data in accordance with this Article. Unless the SUA authorizes retention, or Partner enters into a license under 37 C.F.R. Part 404, the related Data shall be disposed of as NASA directs: None 4. For such Data identified with a restrictive notice pursuant to H.2. including such Data identified pursuant to this Article, Receiving Party shall: a. Use, disclose, or reproduce such Data only as necessary under this Agreement; b. Safeguard such Data from unauthorized use and disclosure; c. Allow access to such Data only to its employees and any Related Entity requiring access under this Agreement; d. Except as otherwise indicated in 4.c., preclude disclosure outside Receiving Party’s organization; e. Notify its employees with access about their obligations under this Article and ensure their compliance, and notify any Related Entity with access about their obligations under this Article; and f. Dispose of such Data as Disclosing Party directs. I. Oral and visual information If Partner discloses Proprietary Data orally or visually, NASA will have no duty to restrict, or liability for disclosure or use, unless Partner: 1. Orally informs NASA before initial disclosure that the Data is Proprietary Data, and 2. Reduces the Data to tangible form with a restrictive notice and gives it to NASA within ten (10) calendar days after disclosure.
Controlled Government Data. The Disclosing Party's Controlled Government Data, LEW 19711-1, LEW 19712-1, will be identified in a separate document.

Related to Controlled Government Data

  • No Government Obligor No Receivable is due from the United States or any State or from any agency, department or instrumentality of the United States or any State.

  • GOVERNMENT DATA PRACTICES Supplier and Sourcewell must comply with the Minnesota Government Data Practices Act, Minnesota Statutes Chapter 13, as it applies to all data provided by or provided to Sourcewell under this Contract and as it applies to all data created, collected, received, maintained, or disseminated by the Supplier under this Contract.

  • Performance of Government Functions Nothing contained in this contract shall be deemed or construed so as to in any way estop, limit, or impair the City from exercising or performing any regulatory, policing, legislative, governmental, or other powers or functions.

  • Government Programs The Property is subject to the government programs listed below or on the attached exhibit: