Right to Publish Throughout the duration of this Master Agreement, Contractor must secure from the Lead State prior approval for the release of information that pertains to the potential work or activities covered by the Master Agreement. This limitation does not preclude publication about the award of the Master Agreement or marketing activities consistent with any proposed and accepted marketing plan. The Contractor shall not make any representations of NASPO ValuePoint’s opinion or position as to the quality or effectiveness of the services that are the subject of this Master Agreement without prior written consent. Failure to adhere to this requirement may result in termination of the Master Agreement for cause.
RELEASE OF GENERAL INFORMATION TO THE PUBLIC AND MEDIA NASA or Partner may, consistent with Federal law and this Agreement, release general information regarding its own participation in this Agreement as desired. Pursuant to Section 841(d) of the NASA Transition Authorization Act of 2017, Public Law 115-10 (the "NTAA"), NASA is obligated to publicly disclose copies of all agreements conducted pursuant to NASA's 51 U.S.C. §20113(e) authority in a searchable format on the NASA website within 60 days after the agreement is signed by the Parties. The Parties acknowledge that a copy of this Agreement will be disclosed, without redactions, in accordance with the NTAA.
MPS LOGO/PUBLICITY No Contractor shall use the MPS Logo in its literature or issue a press release about the subject of this Contract without prior written notice to and written approval of MPS’s Executive Director of Communications & Outreach.
Confidential Terms and Conditions; Publicity Licensee shall not disclose the terms and conditions of this Agreement or the pricing contained herein to any third party. Neither party shall use the name of the other party in publicity, advertising, or similar activity, without the prior written consent of the other, except that Licensee agrees that SAP and its affiliated companies may use Licensee's name in customer listings or, at times mutually agreeable to the parties, as part of SAP's marketing efforts (including without limitation reference calls and stories, press testimonials, site visits, SAPPHIRE participation). SAP will make reasonable efforts to avoid having the reference activities unreasonably interfere with Licensee's business. Licensee agrees that SAP may share information on Licensee with its affiliated companies for marketing and other business purposes and that Licensee has secured permission from its employees to allow SAP to share business contact information with its affiliates.
zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Confidentiality and Publication Subject to the remaining provisions of this clause 8, each Party will treat all Confidential Information of any other Party as confidential and will not, without the consent of the other relevant Party, disclose or permit the same either to be disclosed to third parties or to be used, except solely as contemplated by this Agreement. Each Party must use all reasonable endeavours to ensure that its representatives comply with the obligations of confidentiality imposed upon it under this clause 8 as if those representatives were bound in the same way. Each Party must advise each other Party as soon as practicably possible of any breach of any confidentiality obligations under this Agreement of which it becomes aware. A Party may disclose Confidential Information if required to do so by law or to its professional advisers, subject to the relevant adviser being bound by similar obligations of confidentiality, or if necessary, entering into an appropriate confidentiality undertaking. A Party may publish the Project IP, subject to it complying with the following: prior to any publication, the Party must provide the other Party with full details of the Project IP it proposes to publish and the nature of the publication; and the other Party must notify the first Party whether permission to publish has been granted or refused within 30 days of the request (or such other period as may be set out at Item 7 of the Schedule) (Period); and if the other Party fails to notify the first Party of its decision under clause 8.5(b) within the Period shall be deemed to have consented to the proposed publication by the first Party; and any other Party may only refuse a request to publish if, in that other Party’s reasonable opinion, the publication is likely to jeopardise: the protection of Project IP (as applicable) under any statute of monopoly; or the successful commercialisation of the Project IP by the Party with such rights, or
CONFIDENTIAL INFORMATION AND PUBLICITY 11.1 If Cisco and Supplier have entered into a Non-Disclosure Agreement (“NDA”) which covers disclosure of confidential information under the Purchase Order, and if the term of the NDA expires before the expiration or termination of the Purchase Order, then the term of the NDA shall be automatically extended to match the term of the Purchase Order.
Obligation to Provide Public Access to Grant Records The Division reserves the right to unilaterally cancel this Agreement in the event that the Grantee refuses public access to all documents or other materials made or received by the Grantee that are subject to the provisions of Chapter 119, Florida Statutes, known as the Florida Public Records Act. The Grantee must immediately contact the Division's Contract Manager for assistance if it receives a public records request related to this Agreement.
Root-‐zone Information Publication ICANN’s publication of root-‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
AGREEMENT TO FOLLOW DIRECTIONS I agree to follow the rules for the Activities provided to me and to follow directions given to me by the leaders of the Activities.