Solar Data Sample Clauses

Solar Data. Any and all solar data with regard to the Projects, whether existing now or in the future, included, or included by reference, including without limitation the materials set forth on Schedule E attached hereto. The Solar Data includes any solar study with respect to a Project.
Sample 1Sample 2See All (5)
AutoNDA by SimpleDocs
Solar Data. Schedule 6.13 to this Agreement is a true and complete list of the Solar Data in place as of the Closing Date. Seller has delivered to Buyer true and complete copies of all Books and Records containing the Solar Data and any other information listed on Schedule 6.13 in the format identified on said Schedule 6.13. With respect to each item of Solar Data identified on Schedule 6.13 to this Agreement: 6.13.1 Seller possesses all right, title, and interest in and to each item of Solar Data and has the right, title, interest and ability to convey the same to Buyer without reservations or restrictions; 6.13.2 the item is not subject to any outstanding injunction, judgment, order, decree, ruling, or charge; and 6.13.3 Seller has not agreed to indemnify any Person for or against any interference, infringement, misappropriation, or other conflict with respect to the items.
Sample 1Sample 2
Solar Data. Seller has delivered to Buyer true, correct and complete copies of all relevant Solar Data or characteristics with respect to the Project Site and the Project, copies of which are included in Exhibit PPP.
Sample 1
Solar Data. Seller and the Company have furnished or made available to Purchaser true and correct copies of all reports, studies, analyses, tests, monitoring and assessments with respect to solar data measured or recorded at the site of the Project performed by or on behalf of Seller, the Company or their respective Affiliates in connection with the engineering, procurement, development, construction and operation of the Project or the Project Assets or which to the Knowledge of Seller ever have been produced .
Sample 1

Related to Solar Data

  • Customer Data 8.1 You, not bookinglab or JRNI, have sole responsibility for the entry, deletion, correction, accuracy, quality, integrity, legality, reliability, appropriateness, and right to use the Customer Data. bookinglab and JRNI is not responsible for any of the foregoing or for any destruction, damage, loss, or failure to store any Customer Data beyond its reasonable control or resulting from any failure in data transmission or operation of the Booking Service by you. 8.2 As of the MSA Start Date, JRNI is certified under ISO 27001 and shall maintain an information security program for the Services that complies with the ISO 27001 standards or such other standards as are substantially equivalent to ISO 27001. 8.3 If JRNI and/or bookinglab processes any Personal Data on your behalf when performing its obligations under this Agreement, the Parties acknowledge that you shall be the Data Controller and JRNI and/or bookinglab shall be a Data Processor and in any such case: (a) you shall ensure that you are entitled to transfer the relevant Customer Personal Data to JRNI and/or bookinglab so that they may lawfully use, process and transfer the Customer Personal Data in accordance with this Agreement on your behalf; (b) you shall ensure that the relevant third parties have been informed of, and have given their consent to, such use, processing, and transfer as required by all applicable Data Protection Laws; (c) each Party shall take appropriate technical and organisational measures against unauthorised or unlawful processing of the personal data or its accidental loss, destruction or damage; and (d) notwithstanding any other provision of this Agreement, but subject always to Appendix B(1) Data Protection and B(2) Data Processing Activities, nothing shall prevent JRNI or bookinglab from disclosing Customer Personal Data or Customer Data to their Group Companies, Affiliates and third party service providers as necessary to provide the Services in accordance with clause 3, and otherwise in order to comply with Applicable Law or at the request of a governmental, regulatory or supervisory authority. 8.4 From the MSA Start Date the Parties shall comply with Appendix B(1) Data Protection and Appendix B(2) Data Processing Activities 8.5 ensure that Customer Data and Personal Data deemed as a special category of Data under GDPR is not given to us in any form unless pre-agreed by us in writing 8.6 You are solely responsible and liable for any transfer of Customer Data made by you (or made by JRNI or bookinglab at your request) from the Booking Service to a third party and for ensuring that such transfer is in compliance with the Parties' obligations under the Data Protection Laws.

  • Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.

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

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

  • Usage Data 7.1. The parties shall supply data on usage of the Licensed Work that is available to them during the term of this Licence. Notwithstanding the foregoing, the parties shall neither assemble nor provide data from which an individual user could be identified.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Customer Materials Subject to Section 4(a), all right, title and interest (including all Intellectual Property Rights) in and to the Customer Materials are owned by Customer or Customer’s suppliers.

  • Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD 1.5.2 Response format:

  • Device Data We may share certain personal information and device-identifying technical data about you and your devices with third party service providers, who will compare and add device data and fraud data from and about you to a database of similar device and fraud information in order to provide fraud management and prevention services, which include but are not limited to identifying and blocking access to the applicable service or Web site by devices associated with fraudulent or abusive activity. Such information may be used by us and our third party service providers to provide similar fraud management and prevention services for services or Web sites not provided by us. We will not share with service providers any information that personally identifies the user of the applicable device.

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, MyLineToo must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!