Program Use of Match Information Sample Clauses

Program Use of Match Information. Programs may use the R3 system and the information contained therein solely for the purpose of their participation in the Match and/or SOAP. Programs may only share Match information from or maintained in the R3 system, including but not limited to, information from the List of Unfilled Programs, and/or Regional Match Statistics by Specialty internally with program leadership, program faculty, and program staff as required to participate in the Match and/or SOAP. Programs may not copy, distribute, post, or make publicly available in any other way, any Match information from or maintained in the R3 system, including information from the List of Unfilled Programs, and/or Regional Match Statistics by Specialty. URLs that link to information from the R3 system or PDFs that have been created, copied, or downloaded from the R3 system shall not be made public or redistributed in any form, even if the information already is in the public domain. Unauthorized disclosure of Match information by programs and program staff is considered a violation of this Agreement and may result in sanctions to the program.
Sample 1Sample 2Sample 3See All (11)
AutoNDA by SimpleDocs
Program Use of Match Information. Programs may use the R3 system and the information contained therein solely for the purpose of their participation in the Match. Programs may only share Match information from or maintained in the R3 system, including but not limited to, information from the List of Unfilled Programs internally with program leadership, program faculty, and program staff as required to participate in the Match. Programs may not copy, distribute, post, or make publicly available in any other way, any Match information from or maintained in the R3 system, including information from the List of Unfilled Programs. URLs that link to information from the R3 system or PDFs that have been created, copied, or downloaded from the R3 system shall not be made public or redistributed in any form, even if the information already is in the public domain. Unauthorized disclosure of Match information by programs and program staff is considered a violation of this Agreement and may result in sanctions to the program.
Sample 1Sample 2

Related to Program Use of Match Information

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

  • Disclosure of Account Information to Third Parties We will disclose information to third parties about your account or the transfers you make:

  • Account Information Disclosure We will disclose information to third parties about your account or the transfers you make:

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • User Information Any user or usage data or information collected via Station’s digital properties or related to Station’s digital properties, or any information collected from websites operated by Station’s affiliates under this Agreement, shall be the property of Station and/or such affiliates. Advertiser shall have no rights in such information by virtue of this Agreement.

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

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

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

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

  • Disclosure Updates Promptly and in no event later than 5 Business Days after obtaining knowledge thereof, notify Agent if any written information, exhibit, or report furnished to the Lender Group contained, at the time it was furnished, any untrue statement of a material fact or omitted to state any material fact necessary to make the statements contained therein not misleading in light of the circumstances in which made. The foregoing to the contrary notwithstanding, any notification pursuant to the foregoing provision will not cure or remedy the effect of the prior untrue statement of a material fact or omission of any material fact nor shall any such notification have the effect of amending or modifying this Agreement or any of the Schedules hereto.

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