Possession and Use of Source Code Sample Clauses

Possession and Use of Source Code. If Source Code is obtained by COUNTY under the 10 provisions of Subparagraph VIII.D.4. below, such Source Code shall remain subject to every license 11 restriction, proprietary rights protection, and other COUNTY obligations specified in this Agreement. 12 COUNTY may use Source Code for the sole purpose of supporting its use of the Licensed Software as 13 expressly permitted under this Agreement, and for no other purpose whatsoever. When Source Code 14 resides in a central processing unit, COUNTY shall limit access to its authorized employees who have a 15 need to know in order to support the Licensed Software. COUNTY shall at all times implement strict 16 access security measures in order to prevent unauthorized disclosure, use, or removal of Source Code.
Sample 1
Possession and Use of Source Code. If Source Code is obtained by COUNTY under the 4 provisions of Subparagraph VIII.G.4. below, such Source Code shall remain subject to every license 5 restriction, proprietary rights protection, and other COUNTY obligations specified in this Agreement.
Sample 1
Possession and Use of Source Code. Upon the occurrence of a Release Condition, County will be entitled to obtain a copy of such Source Code from the Escrow Agent pursuant to the terms of the Source Code Escrow Agreement. County shall be entitled to use the Source Code as needed to remedy the event of release and mitigate any damages arising from such event, provided that mitigation of damages shall not include the sale or sublicense of the Source Code. Such use will include, but is not limited to, County’s right to perform its own support and maintenance, alter or modify the Source Code and/or obtain the benefits sought under this Agreement, subject to the limitations of Paragraph 10.3.6 (Proprietary Rights) below.
Sample 1
Possession and Use of Source Code. If Source Code is obtained by COUNTY as authorized by CONTRACTOR such Source Code shall remain subject to every license restriction, proprietary rights protection, and other COUNTY obligations specified in this Agreement. COUNTY may use Source Code for the sole purpose of supporting its use of the Licensed Software as expressly permitted under this Agreement, and for no other purpose whatsoever. When Source Code resides in a central processing unit, COUNTY shall limit access to its authorized employees who have a need to know in order to support the Licensed Software. COUNTY shall at all times implement strict access security measures in order to prevent unauthorized disclosure, use, or removal of Source Code. COUNTY also agrees that all persons with access to the Source Code shall execute confidentiality agreements consistent with the obligations of COUNTY hereunder. //
Sample 1
Possession and Use of Source Code. Subject to the provisions of Subparagraph 11.3.D (License of Source Code), Source Code obtained by COUNTY under the provisions of this Agreement shall remain subject to every license restriction, proprietary rights protection, and other COUNTY obligation specified in this Agreement, provided that COUNTY may make the Source Code available to third parties as needed to assist it in making authorized use of the System. COUNTY may use the Source Code for the sole purpose of supporting its use of the System as expressly permitted under this Agreement or to obtain the benefits sought under this Agreement. In no event shall COUNTY be permitted to grant access to the Source Code to a direct competitor of CONTRACTOR. Likewise, COUNTY shall not be permitted to sell or transfer its rights in the Source Code to any other party. When Source Code is not in use, COUNTY agrees to keep such Source Code in a locked, secure place. When Source Code resides in a central processing unit, COUNTY shall limit access to its authorized employees and consultants who have a need to know in order to support the System.
Sample 1
Possession and Use of Source Code. Upon COUNTY’s request, CONTRACTOR shall place the source code of the TechCare® System in an escrow account setup and maintained by the COUNTY and its selected 3rd Party Vendor. If Source Code is obtained by COUNTY through escrow, such Source Code shall remain subject to every license restriction, proprietary rights protection, and other COUNTY obligations specified in this Agreement. COUNTY may use Source Code for the sole purpose of supporting its use of the Licensed Software as expressly permitted under this Agreement, and for no other purpose whatsoever. When Source Code resides in a central processing unit, COUNTY shall limit access to its authorized employees who have a need to know in order to support the Licensed Software. COUNTY shall at all times implement strict access security measures in order to prevent unauthorized disclosure, use, or removal of Source Code. Source code held in escrow may be tested for authenticity and reliability at designated times by COUNTY.
Sample 1
Possession and Use of Source Code. If Source Code is obtained by COUNTY under the 30 provisions of Subparagraph VIII.D.4., below, such Source Code shall remain subject to every license 31 restriction, proprietary rights protection, and other COUNTY obligations specified in this Agreement. 32 COUNTY may use Source Code for the sole purpose of supporting its use of the Licensed Software as 33 expressly permitted under this Agreement, and for no other purpose whatsoever. When Source Code 34 resides in a central processing unit, COUNTY shall limit access to its authorized employees who have a 35 need to know in order to support the Licensed Software. COUNTY shall at all times implement strict 36 access security measures in order to prevent unauthorized disclosure, use, or removal of Source Code. 37 // 1 COUNTY also agrees that all persons with access to the Source Code shall execute confidentiality 2 agreements consistent with the obligations of COUNTY hereunder.
Sample 1
Possession and Use of Source Code. If Source Code is obtained by COUNTY as authorized 15 by CONTRACTOR such Source Code shall remain subject to every license restriction, proprietary 16 rights protection, and other COUNTY obligations specified in this Agreement. COUNTY may use
Sample 1

Related to Possession and Use of Source Code

  • Possession and Use Contractor may possess, use and reproduce Confidential Information solely for the Purpose. Contractor shall not use the Confidential Information for any other purpose.

  • Possession and Use of Collateral Subject to the provisions of the Security Documents, the Issuer and the Guarantors shall have the right to remain in possession and retain exclusive control of and to exercise all rights with respect to the Collateral (other than monies or U.S. government obligations deposited pursuant to Article VIII, and other than as set forth in the Security Documents and this Indenture), to operate, manage, develop, lease, use, consume and enjoy the Collateral (other than monies and U.S. government obligations deposited pursuant to Article VIII and other than as set forth in the Security Documents and this Indenture), to alter or repair any Collateral so long as such alterations and repairs do not impair the creation or perfection of the Lien of the Security Documents thereon, and to collect, receive, use, invest and dispose of the reversions, remainders, interest, rents, lease payments, issues, profits, revenues, proceeds and other income thereof.

  • Installation and Use Rights You may install and use any number of copies of the software on your devices.

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

  • SERVICES NOT EXCLUSIVE/USE OF NAME Your services to the Fund pursuant to this Agreement are not to be deemed to be exclusive, and it is understood that you may render investment advice, management and other services to others, including other registered investment companies, provided, however, that such other services and activities do not, during the term of this Agreement, interfere in a material manner, with your ability to meet all of your obligations with respect to rendering services to the Fund. The Company and you acknowledge that all rights to the name “RiverNorth” or any variation thereof belong to you, and that the Company is being granted a limited license to use such words in its Fund name or in any class name. In the event you cease to be the adviser to the Fund, the Company’s right to the use of the name “RiverNorth” shall automatically cease on the ninetieth day following the termination of this Agreement. The right to the name may also be withdrawn by you during the term of this Agreement upon ninety (90) days’ written notice by you to the Company. Nothing contained herein shall impair or diminish in any respect, your right to use the name “RiverNorth” in the name of, or in connection with, any other business enterprises with which you are or may become associated. There is no charge to the Company for the right to use this name.

  • Use of Software Any software that is available on the Services ("Software") is the copyrighted work of Red Hat and/or its licensors. Copying or reproducing the Software to any other server or location for further reproduction or redistribution is strictly prohibited, unless such reproduction or redistribution is permitted by a license agreement accompanying such Software. You may not create derivative works of the Software, or attempt to decompile or reverse-engineer the Software unless otherwise permitted by law. Use of the Software is subject to the license terms of any license agreement that may accompany or is provided with the Software. You may not download any Software until you have read and accepted the terms of the accompanying software license. WITHOUT LIMITING THE FOREGOING, THE SOFTWARE IS WARRANTED, IF AT ALL, ONLY ACCORDING TO THE TERMS OF THE SEPARATE LICENSE AGREEMENT ACCOMPANYING THE SOFTWARE. EXCEPT AS WARRANTED IN SUCH LICENSE AGREEMENT, RED HAT, ITS PARENT, SUBSIDIARY, AND AFFILIATE COMPANIES, AND ITS LICENSORS DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THE SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, TO THE MAXIMUM EXTENT PERMITTED BY LAW.

  • Consent to Use of Data You grant NCR Voyix a perpetual, non-exclusive, irrevocable, sub-licensable, transferrable license to use the data transmitted through the Platform: (a) to provide the NCR Voyix Product and the Platform as well as related products, software, materials and services under this Agreement or another agreement between you and NCR Voyix; (b) for product and service enhancements, as well as research and development purposes; and (c) after it has been aggregated, for analytics, commercial and benchmarking purposes.

  • Malicious Use of Orphan Glue Records Registry Operator shall take action to remove orphan glue records (as defined at xxxx://xxx.xxxxx.xxx/en/committees/security/sac048.pdf) when provided with evidence in written form that such records are present in connection with malicious conduct.

  • NON-USE OF NAMES Neither Party shall use the name of the other Party, nor any adaptation thereof, in any advertising, promotional or sales literature without prior written consent obtained from such other Party in each case (which consent shall not be unreasonably withheld or delayed).

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