Joint Announcement, Publicity and Community Education Sample Clauses

Joint Announcement, Publicity and Community Education. (i) Joint Announcement Event. Within sixty days of the Effective Date, Lyft, NFB, Xxxxx Bien Xxxxxx & Xxxxxxxx LLP, and Disability Rights Advocates (“DRA”) shall hold a joint event announcing the policy changes to be adopted by Lyft as set forth in Section 1(a)-(d) of this Agreement, as well as their partnership to increase transportation options for the blind community through Lyft or other similar platforms (“Joint Announcement Event”). The Parties shall issue a joint press release, using language mutually agreed upon by the Parties, announcing this Agreement and describing its key terms. Lyft and Claimants’ Counsel shall post the press release on their respective websites, and Lyft shall distribute the press release to all guide dog training programs in the United States identified by Claimants. The Parties also agree to pursue publication of an Op-Ed in a major newspaper publicizing the policy changes and partnership as set forth in this Agreement.
AutoNDA by SimpleDocs

Related to Joint Announcement, Publicity and Community Education

  • INFORMATION AND APPLICATIONS POLICY LANGUAGE For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.

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

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

  • PUBLICITY AND BRANDING 24.1 Subject to Clause 25 (Marketing), the Supplier shall not make any press announcements or publicise this Framework Agreement or its contents in any way without the Authority's prior Approval.

  • Publicity, Media and Official Enquiries 22.1 Without prejudice to the Authority’s obligations under the FOIA, neither Party shall make any press announcements or publicise the Contract or any part thereof in any way, except with the written consent of the other Party.

  • Publicity and Confidentiality 12.1 Publicity. Partner will keep confidential and will not disclose, market or advertise to third parties the terms of this Agreement (including the fees paid hereunder). Partner or Red Hat may reference its relationship with the other, in the normal course of business including during earnings calls, discussions with analysts, meetings with the press, customer briefings, general marketing activities and in regulatory filings. Neither Party will issue formal press releases or other similar activities referencing the other Party without the written consent of the other Party.

  • E6 Publicity, Media and Official Enquiries E6.1 The Contractor shall not:

  • Confidentiality and Safeguarding of University Records; Press Releases; Public Information Under this Agreement, Contractor may (1) create, (2) receive from or on behalf of University, or (3) have access to, records or record systems (collectively, University Records). Among other things, University Records may contain social security numbers, credit card numbers, or data protected or made confidential or sensitive by Applicable Laws. [Option (Include if University Records are subject to FERPA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Family Educational Rights and Privacy Act, 20 United States Code (USC) §1232g (FERPA) are addressed in Section 12.41.] [Option (Include if University is a HIPAA Covered Entity and University Records are subject to HIPAA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Health Insurance Portability and Accountability Act and 45 Code of Federal Regulations (CFR) Part 160 and subparts A and E of Part 164 (collectively, HIPAA) are addressed in Section 12.26.] Contractor represents, warrants, and agrees that it will: (1) hold University Records in strict confidence and will not use or disclose University Records except as (a) permitted or required by this Agreement, (b) required by Applicable Laws, or (c) otherwise authorized by University in writing; (2) safeguard University Records according to reasonable administrative, physical and technical standards (such as standards established by the National Institute of Standards and Technology and the Center for Internet Security [Option (Include if Section 12.39 related to Payment Card Industry Data Security Standards is not include in this Agreement.):, as well as the Payment Card Industry Data Security Standards]) that are no less rigorous than the standards by which Contractor protects its own confidential information; (3) continually monitor its operations and take any action necessary to assure that University Records are safeguarded and the confidentiality of University Records is maintained in accordance with all Applicable Laws and the terms of this Agreement; and (4) comply with University Rules regarding access to and use of University’s computer systems, including UTS165 at xxxx://xxx.xxxxxxxx.xxx/board-of-regents/policy-library/policies/uts165-information-resources-use-and-security-policy. At the request of University, Contractor agrees to provide University with a written summary of the procedures Contractor uses to safeguard and maintain the confidentiality of University Records.

  • NEPOTISM DISCLOSURE A. In this section the term “relative” means:

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

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