Use of FIIOC’s and FSC's Name The Trust shall not use the name of FIIOC and FSC in any Prospectus, sales literature or other material relating to the Trust or any Fund of the Trust in a manner not consented to by FIIOC and FSC prior to use; provided, however, that FIIOC and FSC shall approve all uses of its name which merely refer in accurate terms to its appointments, duties or fees hereunder or which are required by the Securities and Exchange Commission ("SEC" or “Commission”) or a state securities commission; and further, provided that in no event shall such approval be unreasonably withheld.
User Data We will maintain certain data that you transmit to the Services for the purpose of managing the performance of the Services, as well as data relating to your use of the Services. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Services. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.
Use of Customer Data Verizon, Verizon Affiliates and their respective agents, may use, process and/or transfer Customer Data (including intra-group transfers and transfers to entities in countries that do not provide statutory protections for personal information) as set forth in the Privacy Policy and as necessary:
(a) in connection with provisioning of Services; (b) to incorporate Customer Data into databases controlled by Verizon, Verizon Affiliates or their respective agents for the purpose of providing Services; administration; provisioning; invoicing and reconciliation; verification of Customer identity, solvency and creditworthiness; maintenance, support and product development; fraud detection and prevention; sales, revenue and customer analysis and reporting; market and customer use analysis including in the manner described in the Privacy Policy; and (c) to communicate to Customer regarding Services.
Use of Customer Name Contractor may use County’s name without County’s prior written consent only in Contractor’s customer lists. Any other use of County’s name by Contractor must have the prior written consent of County.
Insurance and Fingerprint Requirements Information Insurance If applicable and your staff will be on TIPS member premises for delivery, training or installation etc. and/or with an automobile, you must carry automobile insurance as required by law. You may be asked to provide proof of insurance. Fingerprint It is possible that a vendor may be subject to Chapter 22 of the Texas Education Code. The Texas Education Code, Chapter 22, Section 22.0834. Statutory language may be found at: xxxx://xxx.xxxxxxxx.xxxxx.xxxxx.xx.xx/ If the vendor has staff that meet both of these criterion: (1) will have continuing duties related to the contracted services; and (2) has or will have direct contact with students Then you have ”covered” employees for purposes of completing the attached form. TIPS recommends all vendors consult their legal counsel for guidance in compliance with this law. If you have questions on how to comply, see below. If you have questions on compliance with this code section, contact the Texas Department of Public Safety Non-Criminal Justice Unit, Access and Dissemination Bureau, FAST-FACT at XXXX@xxxxx.xxxxx.xx.xx and you should send an email identifying you as a contractor to a Texas Independent School District or ESC Region 8 and TIPS. Texas DPS phone number is (000) 000-0000. See form in the next attribute to complete entitled: Texas Education Code Chapter 22 Contractor Certification for Contractor Employees
Use of Data by User Registry Operator will permit user to use the zone file for lawful purposes; provided that (a) user takes all reasonable steps to protect against unauthorized access to and use and disclosure of the data and (b) under no circumstances will Registry Operator be required or permitted to allow user to use the data to, (i) allow, enable, or otherwise support the transmission by email, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than user’s own existing customers, or (ii) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator or any ICANN-‐accredited registrar.
Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.
Publicity/Use of Names Neither Party shall use the name, trademark, trade name or logo of the other Party, its Affiliates or their respective employee(s) in any publicity, promotion, news release or disclosure relating to this Agreement or its subject matter, without the prior express written permission of the other Party, except for those disclosures expressly authorized under this Article 4. Following execution of this Agreement, either Party may issue a press release announcing the existence of this Agreement in form and substance agreed to in writing by both Parties, such agreement to not be unreasonably withheld or delayed. Each Party agrees not to issue any other press release or other public statement disclosing other information relating to this Agreement or the transactions contemplated hereby without the prior written consent of the other Party, which consent shall not be unreasonably withheld or delayed; provided that Arvinas agrees that it shall be deemed reasonable for Pfizer to withhold its consent for the disclosure of any information related to a Target or a specific Compound or the amount of any payment made or to be made under this Agreement; and provided further that any disclosure which is required by Law or the rules of a securities exchange, as reasonably advised by the disclosing Party’s counsel, may be made subject to the following. Each Party agrees to provide to the other Party a copy of any public announcement regarding this Agreement or the subject matter thereof as soon as reasonably practicable under the circumstances prior to its scheduled release. Except under extraordinary circumstances or to the extent any such advance notice or notice period is not consistent with applicable Law, each Party shall provide the other with an advance copy of any such announcement at least [**] prior to its scheduled release. Each Party shall have the right to expeditiously review and recommend changes to any such announcement and, except as otherwise required by Law, the Party whose announcement has been reviewed shall remove any information the reviewing Party reasonably deems to be inappropriate for disclosure. The contents of any announcement or similar publicity which has been reviewed and approved by the reviewing Party can be re-released by either Party without a requirement for re-approval. In addition, except to the extent required by Laws in connection with patent enforcement activities conducted in accordance with Article 7, Pfizer shall not use the name “Yale” or “Yale University,” nor any variation or adaptation thereof, nor any trademark, trade name or other designation owned by Yale University, nor the names of any of its trustees, officers, faculty, students, employees or agents, for any purpose without the prior written consent of Yale University in each instance, such consent to be granted or withheld by Yale University in its sole discretion, except that Pfizer may state that it has sublicensed from Yale University one or more of the patents or applications comprising the Yale Licensed Patents.
Publicity and Use of Trademarks or Service Marks 34.1 A Party, its Affiliates, and their respective contractors and Agents, shall not use the other Party’s trademarks, service marks, logos or other proprietary trade dress, in connection with the sale of products or services, or in any advertising, press releases, publicity matters or other promotional materials, unless the other Party has given its written consent for such use, which consent the other Party may grant or withhold in its sole discretion.
34.2 Neither Party may imply any direct or indirect affiliation with or sponsorship or endorsement of it or its services or products by the other Party.
34.3 Any violation of this Section 34 shall be considered a material breach of this Agreement.
Protection of Customer Data The Supplier shall not delete or remove any proprietary notices contained within or relating to the Customer Data. The Supplier shall not store, copy, disclose, or use the Customer Data except as necessary for the performance by the Supplier of its obligations under this Call Off Contract or as otherwise Approved by the Customer. To the extent that the Customer Data is held and/or Processed by the Supplier, the Supplier shall supply that Customer Data to the Customer as requested by the Customer and in the format (if any) specified by the Customer in the Call Off Order Form and, in any event, as specified by the Customer from time to time in writing. The Supplier shall take responsibility for preserving the integrity of Customer Data and preventing the corruption or loss of Customer Data. The Supplier shall perform secure back-ups of all Customer Data and shall ensure that up-to-date back-ups are stored off-site at an Approved location in accordance with any BCDR Plan or otherwise. The Supplier shall ensure that such back-ups are available to the Customer (or to such other person as the Customer may direct) at all times upon request and are delivered to the Customer at no less than six (6) Monthly intervals (or such other intervals as may be agreed in writing between the Parties). The Supplier shall ensure that any system on which the Supplier holds any Customer Data, including back-up data, is a secure system that complies with the Security Policy and the Security Management Plan (if any). If at any time the Supplier suspects or has reason to believe that the Customer Data is corrupted, lost or sufficiently degraded in any way for any reason, then the Supplier shall notify the Customer immediately and inform the Customer of the remedial action the Supplier proposes to take. If the Customer Data is corrupted, lost or sufficiently degraded as a result of a Default so as to be unusable, the Supplier may: require the Supplier (at the Supplier's expense) to restore or procure the restoration of Customer Data to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer, and the Supplier shall do so as soon as practicable but not later than five (5) Working Days from the date of receipt of the Customer’s notice; and/or itself restore or procure the restoration of Customer Data, and shall be repaid by the Supplier any reasonable expenses incurred in doing so to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer.
