Service Provider’s consent to disclosure. (a) The Service Provider consents to the School Council disclosing or publishing any information of or about this Agreement as follows:
Service Provider’s consent to disclosure Sample Clauses
Related to Service Provider’s consent to disclosure
Privacy Consent; Consent to Publication of Agreement Contributor consents to the OpenID Privacy Policy and also agrees that OIDF may publish a copy of this Agreement as signed by Contributor via posting on the OIDF publicly-accessible website, and Contributor consents to such publication. If Contributor is a Legal Entity Contributor, it also represents that it has obtained appropriate consent under applicable law from all individuals listed in this Agreement to the publication of this Agreement and their personal information listed herein. The parties have formed this Agreement as of the Effective Date. OPENID FOUNDATION (“CONTRIBUTOR”) By: (Sign) Xxxx Xxxxxx By: (Sign) Xxxxxx Xxxxxxxxx Name: (Print) Title: Program Manager 7/21/2022 Name: (Print) Title: Xxxxxx Xxxxxxxxx 7/18/2022
SOFTWARE LICENSE GRANT Where Product is acquired on a licensed basis the following shall constitute the license grant:
Modification of Licensed Materials The Participating Institutions or the Authorized Users shall not modify or manipulate the Licensed Materials without the prior written permission of the Licensor.
SOFTWARE LICENSE GRANT Where Product is acquired on a licensed basis the following shall constitute the license grant:
Notification of Modifications of Licensed Materials From time to time Publisher may add, change, or modify portions of the Licensed Materials, or migrate the Licensed Materials to other formats. When such changes, modifications, or migrations occur, the Licensor shall give notice of any such changes to Licensee as soon as is practicable, but in no event less than sixty (60) days in advance of modification. Such a notice may also be given directly by the Publisher to the Licensee. If any of the changes, modifications, or migrations renders the Licensed Materials substantially less useful to the Licensee, the Participating Institutions or their Authorized Users, the Licensee may seek to terminate this Agreement for breach pursuant to the termination provisions of this Agreement in Section XI, below.
Restricted Use By Third Parties Third parties retained by Licensee shall have the right to use the Product to maintain Licensee’s business operations, including data processing, for the time period that they are engaged in such activities, provided that: (i) Licensee gives notice to Contractor of such third party, Site of intended use of the Product, and means of access; and (ii) such third party has executed, or agrees to execute, the Product manufacturer’s standard nondisclosure or restricted use agreement, which executed agreement shall be accepted by the Contractor (“Non-Disclosure Agreement”); and (iii) such third party maintains a logical or physical partition within its computer system so as to restrict use and access to the program to that portion solely dedicated to beneficial use for Licensee. In no event shall Licensee assume any liability for third party’s compliance with the terms of the Non-Disclosure Agreement, nor shall the Non- Disclosure Agreement create or impose any liabilities on the State or Licensee.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.
Access to Personal Information by Subcontractors Supplier agrees to require any subcontractors or agents to which it discloses Personal Information under this Agreement or under any SOW to provide reasonable assurance, evidenced by written contract, that they will comply with the same or substantially similar confidentiality, privacy and security obligations with respect to such Personal Information as apply to Supplier under this Agreement or any SOW. Supplier shall confirm in writing to DXC that such contract is in place as a condition to DXC’s approval of use of a subcontractor in connection with any SOW. Upon request of DXC, Supplier will provide to DXC a copy of the subcontract or an extract of the relevant clauses. Supplier shall ensure that any failure on the part of any subcontractor or agent to comply with the Supplier obligations under this Agreement or any SOW shall be grounds to promptly terminate such subcontractor or agent. If during the term of this Agreement or any SOW, DXC determines, in its exclusive discretion, that any Supplier subcontractor or agent cannot comply with the Supplier obligations under this Agreement or with any SOW, then DXC may terminate this Agreement in whole or in part (with respect to any SOW for which such subcontractor or agent is providing services), if not cured by Supplier within the time prescribed in the notice of such deficiency.
Permitted Uses and Disclosure by Business Associate (1) General Use and Disclosure Provisions Except as otherwise limited in this Section of the Contract, Business Associate may use or disclose PHI to perform functions, activities, or services for, or on behalf of, Covered Entity as specified in this Contract, provided that such use or disclosure would not violate the HIPAA Standards if done by Covered Entity or the minimum necessary policies and procedures of the Covered Entity.
