University Data Sample Clauses

University Data. “Data” means any and all electronic or other information that is collected, used, processed, stored, or generated as the result of the Services. Data may include but is not limited to, information that is: (i) identified with a specific individual (e.g., “personally identifiable information” or “PII”); (ii) subject to proprietary rights under patent, copyright, trademark, or trade secret law; (iii) privileged against disclosure in a civil lawsuit (e.g., data subject to attorney-client or doctor-patient privileges); (iv) subject to laws, regulations, rules or standards that prohibit or limit disclosure (e.g., the Family Educational Rights and Privacy Act (“FERPA”), the Export Administration Act (“EAR”), the International Traffic in Arms Regulations (“ITAR”), the Health Insurance Portability and Accountability Act (“HIPAA”), the Genetic Information Nondiscrimination Act (“XXXX”), the Xxxxx-Xxxxx-Xxxxxx Act; and the Payment Card Industry Security Standards Council requirements); or (v) ought in good faith to be treated as sensitive, proprietary, or confidential.
Sample 1Sample 2Sample 3See All (4)
University Data. University Data includes all Xxxxx owned, controlled, or collected PII and any other Xxxxx owned, controlled, or collected confidential information that is not intentionally made available by Xxxxx on public websites, including but not limited to business, administrative and financial data, intellectual property, and patient, student and personnel data. Contractor agrees to the following regarding University Data it may collect or process as part of this contract: 1. Contractor will use University Data only for the purpose of fulfilling its duties under the Contract and will not share such data with or disclose it to any third party without the prior written consent of Xxxxx, except as required by the Contract or as otherwise required by law. University Data will only be processed by Contractor to the extent necessary to fulfill its responsibilities under the Contract or as otherwise directed by Xxxxx. 2. University Data, including any back-ups, will not be accessed, stored, or transferred outside the United States without prior written consent from Xxxxx. Contractor will provide access to University Data only to its employees and subcontractors who need to access the data to fulfill Contractor’s obligations under the Contract. Contractor will ensure that employees who perform work under the Contract have read, understood, and received appropriate instruction as to how to comply with the data protection provisions of the Contract and to maintain the confidentiality of the University Data. 3. The parties agree that as between them, all rights including all intellectual property rights in and to University Data shall remain the exclusive property of Xxxxx, and Contractor has a limited, nonexclusive license to use the University Data as provided in the Contract solely for the purpose of performing its obligations under the Contract. The Contract does not give a party any rights, implied or otherwise, to the other party’s data, content, or intellectual property, except as expressly stated in the Contract.
Sample 1
University Data a) Company agrees that it may (i) create, host, maintain, store, transmit, process, access, (ii) receive from or on behalf of University and/or its students, or (iii) have access to, records or record systems containing University Data. For purposes of this Agreement, with respect to both University and its students, “University Data” means without limitation all information, data, Personal Data, sound, image, video or other files, including applications, that are provided to, uploaded to, stored or otherwise accessible by, Company pursuant to or in connection with the Agreement. “Personal Data” includes, but is not limited to, personally identifiable information about University’s employees, other personnel, agents, students, prospective students, contractors, managers, suppliers, and/or other natural persons, and any of the above of or associated therewith including family members of the foregoing, such as name, address, phone number, date of birth, Social Security Number, and student or personnel identification number; FERPA Data (as that term is defined below); Cardholder Data (as that term is defined below); IP address; driver’s license number; other state- or federal-identification numbers such as passport, visa or state identity card numbers; account number or credit or debit card number, or an account number or credit card number in combination with any required security code, access code or password that would permit access to an individual’s financial account; biometric information; a user name or e-mail address in combination with a password or security question; “non-public information” as defined by the Xxxxx-Xxxxx-Xxxxxx Act; health information as defined in applicable statutes, laws, and regulations; and such other data and information as may be protected under Applicable Privacy and Data Security Laws. “Applicable Privacy and Data Security Laws’ means (X) all privacy, security, data protection and communications laws, rules and regulations of any applicable jurisdiction (including, without limitation, each jurisdiction where a data subject resides) that apply to Company, to University or to the Personal Data, (Y) the applicable data security and privacy policies of Company, and (Z) the applicable data security and privacy policies of University that are provided by University to Company (including this Addendum). In the event of a conflict between subsection (Y) or (Z) of the preceding sentence, subsection (Z) shall control. Additionally, a...
Sample 1
University Data. University shall retain ownership of all data inputted by or for University. Contractor shall not obtain any ownership rights in such Data and may use such data only in performance of Contractor’s duties and obligations under this Agreement. [OPTION 2 – SaaS]
Sample 1
University Data 
Sample 1Sample 2Sample 3See All (16)

Related to University Data

  • Licensee Data Licensee acknowledges and agrees that Licensee will be solely responsible for backing-up, and taking all appropriate measures to protect and secure, Licensee Data. Licensee acknowledges that Nuix may make, store and maintain back up copies of Licensee Data, but is not obliged to do so. Nuix will not be liable for any loss or corruption of Licensee Data.

  • University Any notice may be served upon the University by delivering it, in writing, to the University at the address set forth on the last page of this Agreement, by depositing it in a United States Postal Service deposit box with the postage fully prepaid and with the notice addressed to the University at the aforementioned address, or by sending a facsimile of it to the University facsimile number set forth on the last page of this Agreement.

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • Product Data Illustrations, standard schedules, performance charts, instructions, brochures, diagrams, and other information furnished by Developer to illustrate a material, product, or system for some portion of the Work.

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

  • Licensed Technology (a) LICENSOR is not aware of any interference, infringement, misappropriation, or other conflict with any intellectual property rights of third parties, and LICENSOR has never received any charge, complaint, claim, demand, or notice alleging any such interference, infringement, misappropriation, or violation (including any claim that LICENSOR must license or refrain from using any intellectual property rights of any third party). To the knowledge of LICENSOR, no third party has interfered with, infringed upon, misappropriated, or otherwise come into conflict with any of the LICENSED TECHNOLOGY. (b) Exhibit A identifies each patent or registration which has been issued to LICENSOR with respect to any of the LICENSED TECHNOLOGY and identifies each pending patent application or application for registration which LICENSOR has made with respect to any of the LICENSED TECHNOLOGY. LICENSEE acknowledges that LICENSOR has previously made available to LICENSEE correct and complete copies of all such patents, registrations and applications (as amended to-date) in LICENSOR’s possession and has made available to LICENSEE correct and complete copies of all other written documentation in LICENSOR’s possession evidencing ownership and prosecution (if applicable) of each such item. (c) Exhibit A identifies each item of LICENSED TECHNOLOGY that is assigned to LICENSOR or that LICENSOR uses pursuant to license, sublicense, agreement, or permission. LICENSOR has made available to LICENSEE correct and complete copies of all such licenses, sublicenses, agreements, patent prosecution files and permissions (as amended to-date) in LICENSOR’s possession. With respect to each item of LICENSED TECHNOLOGY required to be identified in Exhibit A and to the knowledge of LICENSOR: (i) the license, sublicense, agreement, or permission covering the item is legal, valid, binding, enforceable, and in full force and effect; (ii) the license, sublicense, agreement, or permission will continue to be legal, valid, binding, enforceable, and in full force and effect on identical terms following the consummation of the transactions contemplated hereby; (iii) no Party to the license, sublicense, agreement, or permission is in breach or default, and no event has occurred which with notice or lapse of time would constitute a breach or default or permit termination, modification, or acceleration thereunder; (iv) no party to the license, sublicense, agreement, or permission has repudiated any provision thereof; (v) the underlying item of LICENSED TECHNOLOGY is not subject to any outstanding lien or encumbrance, injunction, judgment, order, decree, ruling, or charge; (vi) no action, suit, proceeding, hearing, investigation, charge, complaint, claim, or demand is pending or is threatened which challenges the legality, validity, or enforceability of the underlying item of LICENSED TECHNOLOGY; and (vii) except as provided in Exhibit A, LICENSOR has not granted any license or similar right to the LICENSED TECHNOLOGY within the GENERAL FIELD or PARTHENOGENESIS FIELD.

  • Technical Information The Employer agrees to provide to the Union such information that is available relating to employees in the bargaining unit, as may be required by the Union for collective bargaining purposes.

  • Third Party Data Any statistical, industry-related and market-related data, which are included in the Disclosure Package and the Prospectus, is based on or derived from sources that the Company reasonably and in good faith believes to be reliable and accurate, and such data agrees with the sources from which it is derived, and the Company has obtained the written consent for the use of such data from such sources to the extent required.

  • Contractor Licensing, etc. Notwithstanding Section 14.c, District may terminate this Contract immediately by written notice to Contractor upon denial, suspension, revocation, or non-renewal of any license, permit, or certificate that Contractor must hold to provide services under this Contract.

  • Licensee “Licensee” means the individual or company that has entered into an Agreement with the Embassy. “Offer” means a response to a solicitation that, if accepted, would bind the offeror to perform the resultant Agreement.