Property Records Subrecipient shall maintain real property inventory records, which clearly identify properties purchased, improved, or sold. Properties retained shall continue to meet eligibility criteria, rental limitations, health, safety and building codes, etc., and shall conform to federal and State regulations.
Client Records 26.2.1 CONTRACTOR shall prepare and maintain accurate and complete records of clients served and dates and type of services provided under the terms of this Contract in a form acceptable to ADMINISTRATOR.
Patient Records Upon termination of this Agreement, the New PC shall retain all patient dental records maintained by the New PC or the MSO in the name of the New PC. During the term of this Agreement, and thereafter, the New PC or its designee shall have reasonable access during normal business hours to the New PC's and the MSO's records, including, but not limited to, records of collections, expenses and disbursements as kept by the MSO in performing the MSO's obligations under this Agreement, and the New PC may copy any or all such records.
Third Party Material (a) The Supplier must provide Third Party Material necessary or appropriate to supply the Services.
Student Records The School shall maintain student records for current and former students in accordance with the requirements of State and federal law, including the Family Education Rights and Privacy Act, 20 U.S.C. § 1232g, as may be amended from time to time.
Third Party Materials The Application may display, include, or make available third-party content (including data, information, applications, and other products, services, and/or materials) or provide links to third-party websites or services, including through third- party advertising ("Third-Party Materials"). You acknowledge and agree that Company is not responsible for Third-Party Materials, including their accuracy, completeness, timeliness, validity, copyright compliance, legality, decency, quality, or any other aspect thereof. Company does not assume and will not have any liability or responsibility to you or any other person or entity for any Third-Party Materials. Third-Party Materials and links thereto are provided solely as a convenience to you, and you access and use them entirely at your own risk and subject to such third parties' terms and conditions.
Third Party Information I understand, in addition, that the Company has received and in the future will receive from third parties confidential or proprietary information (“Third Party Information”) subject to a duty on the Company’s part to maintain the confidentiality of such information and to use it only for certain limited purposes. During the term of my employment and thereafter, I will hold Third Party Information in the strictest confidence and will not disclose to anyone (other than Company personnel who need to know such information in connection with their work for the Company) or use, except in connection with my work for the Company, Third Party Information unless expressly authorized by an officer of the Company in writing.
Health Records Provider agrees to cooperate with Subcontractor and/or Health Plan to maintain and share a health record of all services provided to a Covered Person, as appropriate and in accordance with applicable laws, regulations and professional standards.
Third Party Proprietary Data The Disclosing Party's Third Party Proprietary Data, if any, will be identified in a separate technical document.
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.
