Additional Permitted Uses In addition to those purposes set forth in the Agreement, Business Associate may use PHI for the following additional purposes:
Permitted Uses Tenant may use the Property only for the Permitted Uses set forth in Section 1.06 above.
Permitted Use Tenant shall use the Premises solely for the Permitted Use set forth in Section 7 of the Summary and Tenant shall not use or permit the Premises or the Project to be used for any other purpose or purposes whatsoever without the prior written consent of Landlord, which may be withheld in Landlord’s sole discretion.
Permitted Users Client may access and use only the Course Materials to which Client has subscribed, and such access and use is limited to the number of users identified in the Order Form and any subsequent Orders placed under an Order Form, and for the Contract Term. Orders for additional Subscriptions may be agreed by the parties from time to time under a particular Order Form, and shall set forth the number of additional Subscriptions, the total Subscription Fees payable therefore, and any other terms and conditions relating to such Order (each, an “Order”). Each Order Form and each Order, upon execution by both parties, shall form a part of this Agreement, and shall be subject to all of the terms and conditions hereof. An Order may take the form of a supplementary document signed by each party or acknowledged by each party electronically (whether by facsimile transmission, email or by other similar reliable means evidencing the intent of the parties). Each Order shall be subject to the terms of this Agreement and shall be incorporated herein by reference. A Subscription is limited to use by one individual user and may not be transferred to another user.
Permitted License Uses and Restrictions (a) This Order Form Supplement allows you, as an authorized User under the Master Subscription Agreement, to use the Software on any Supported Device and on no other devices.
PERMITTED USES AND DISCLOSURES BY CONTRACTOR Except as otherwise limited in this Schedule, Contractor may use or disclose Protected Health Information to perform functions, activities, or services for, or on behalf of, County as specified in the Agreement; provided that such use or disclosure would not violate the Privacy Rule if done by County.
Restricted Use 5.1 Recipient shall maintain and use Material in compliance with all applicable laws, regulations and rules. Material may only be used for internal academic non-profit research. In no circumstances shall Material be used (i) in or for clinical trials; (ii) for diagnostic or therapeutic purposes involving human subjects or animals; (iii) for prophylactic use; or (iv) for production. Recipient shall be solely liable for any modifications to any Product that it makes, directs or permits, including but not limited to any potential infringement upon third-party intellectual property rights. Recipient shall defend, indemnify and hold CTK harmless from and against any claims of third parties based on any claim arising out of Recipient’s use of .
Restricted Use by Licensee Except as expressly authorized by the terms of license, Licensee shall not:
Access and Use 1. Each Party shall ensure that enterprises of the other Party have access to and use of any public telecommunications network or service, including leased circuits, offered in its territory or across its borders on a timely basis and on terms and conditions that are reasonable and non-discriminatory such as those set out in paragraphs 2 to 6.
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
