Product Usage Data Sample Clauses

Product Usage Data. Elastic may collect and use Product Usage Data (defined below) for security, support, product and operations management, and research and development. “Product Usage Data” is information other than Customer content that may be automatically collected and reported by the Product. Detailed information on Product Usage Data is provided in Elastic’s Privacy Statement at xxxxx://xxx.xxxxxxx.xx/legal/privacy-statement.
Sample 1Sample 2Sample 3See All (15)
AutoNDA by SimpleDocs
Product Usage Data. Elastic may collect and use Product Usage Data (defined below) for security, support, product and operations management, and research and development. “Product Usage Data” is information other than MSP or MSP Customer content that may be automatically collected and reported by a Cloud Service. Detailed information on Product Usage Data is provided in Elastic’s Privacy Statement at xxxxx://xxx.xxxxxxx.xx/legal/product-privacy- statement. Product Usage Data will not be shared with third parties in a manner attributable to an individual, an MSP Customer or MSP.
Sample 1Sample 2Sample 3
Product Usage Data. The Product(s) may provide Product Usage Data (defined below) to Elastic. Product Usage Data does not include any Customer personal data or any Content that Customer processes or stores in connection with Customer’s use of the Product. In addition, Customer may disable Product Usage Data in the Software at any time. Product Usage Data is processed in accordance with Elastic’s Product Privacy Statement at xxxxx://xxx.xxxxxxx.xx/legal/product-privacy-statement. Elastic uses Product Usage Data for security, support, product and operations management, and research and development. Elastic does not share Product Usage Data with third parties. “Product Usage Data” is statistical and other information about Customer’s configuration and use of the Product(s), such as type and version, operating systems and environment, cluster statistics (e.g., node type and counts), performance (e.g., uptime and response times) and feature usage.
Sample 1Sample 2Sample 3
Product Usage Data. The Cloud Service may provide Product Usage Data (defined below) to Elastic. Product Usage Data does not include any MSP or MSP Customer personal data or any content that MSP processes or stores in the Cloud Service in connection with use by MSP of the Cloud Service. Product Usage Data is processed in accordance with Elastic’s Product Privacy Statement at xxxxx://xxx.xxxxxxx.xx/legal/product-privacy-statement. Elastic uses Product Usage Data for security, support, product and operations management, and research and development. Elastic does not share Product Usage Data with third parties. “Product Usage Data” is statistical and other information about MSP’s configuration and use of the Cloud Service, such as type and version, operating systems and environment, cluster statistics (e.g., node type and counts), performance (e.g., uptime and response times) and feature usage.
Sample 1Sample 2
Product Usage Data. Customer agrees that Sisense may use and disclose certain data, including Customer Data, derived from Customer’s use of the Product and Services to create aggregated data and statistics about the Product and its features, which Sisense may provide to others, including Sisense’s customers, potential customers and the general public, provided that such aggregated data and statistics do not contain any Personal Data or identify any living individual, Customer, Customer’s clients, or any of their respective products or brands. Customer further agrees, that Sisense may use such data for marketing purposes and to conduct analysis in order to improve Customer’s use of and experience with the Product.
Sample 1Sample 2
Product Usage Data. Elastic may collect and use Product Usage Data (defined below) for security, support, product and operations management, and research and development. “Product Usage Data” is information other than content ingested into the Commercial Software that may be automatically collected and reported by the Commercial Software. Detailed information on Product Usage Data is provided in Elastic’s Privacy Statement at xxxxx://xxx.xxxxxxx.xx/legal/privacy-statement. OEM shall make such disclosures to, and/or obtain such consents from, End Users as may be necessary to secure Elastic’s right to collect and use Product Usage Data from End Users pursuant to this Section.
Sample 1Sample 2
Product Usage Data. Absolute may collect and use Product Usage Data for security, support, product and operations management, and research and development purposes. “Product Usage Data” is information other than Customer Data that is automatically collected and reported by the Products about how the Products are used by Absolute’s customers. Product Usage Data will not be shared with third parties in a manner attributable to Customer or any individual.
Sample 1Sample 2
AutoNDA by SimpleDocs
Product Usage Data. In connection with the operation of LEMUR, Critigen collects and receives data with regard to usage of LEMUR and may use such data in accordance with Critigen’s Privacy Policy, which includes, but is not limited to, (i) using such data for Critigen’s internal business purposes, (ii) disclosing such data to third parties in connection with the operation of LEMUR, (iii) disclosing such data as required by law or legal process, (iv) using and disclosing such data when it is not specifically identifiable to Customer, and (v) monitoring Customer’s compliance with the terms of this Agreement. CUSTOMER UNDERSTANDS AND AGREES THAT THE PRODUCT MAY CONNECT TO THE INTERNET AND CRITIGEN’S SYSTEMS TO REPORT INFORMATION TO CRITIGEN THAT ENABLES CRITIGEN TO CONFIRM COMPLIANCE WITH THIS AGREEMENT AND COLLECT PRODUCT USAGE DATA AS SET FORTH IN THIS AGREEMENT AND THE CRITIGEN PRIVACY POLICY.
Sample 1
Product Usage Data. The Product(s) may provide Product Usage Data (defined below) to Elastic. Product Usage Data does not include any Customer personal data or any Content that Customer processes or stores in connection with Customer’s use of the Product. Product Usage Data is processed in accordance with Elastic’s Product Privacy Statement at xxxxx://xxx.xxxxxxx.xx/legal/product-privacy- statement. Elastic uses Product Usage Data for security, support, product and operations management, and research and development. Elastic does not share Product Usage Data with third parties. “Product Usage Data” is statistical and other information about Customer’s configuration and use of the Product(s), such as type and version, operating systems and environment, cluster statistics (e.g., node type and counts), performance (e.g., uptime and response times) and feature usage.
Sample 1

Related to Product Usage Data

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

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

  • AUDIT OF LICENSED PRODUCT USAGE Contractor shall have the right to periodically audit, no more than annually, at Contractor’s expense, use of licensed Product at any site where a copy of the Product resides provided that: (i) Contractor gives Licensee(s) at least thirty (30) days advance written notice, (ii) such audit is conducted during such party’s normal business hours, (iii) the audit is conducted by an independent auditor chosen on mutual agreement of the parties. Contractor shall recommend a minimum of three (3) auditing/accounting firms from which the Licensee will select one (1). In no case shall the Business Software Alliance (BSA), Software Publishers Association (SPA), Software and Industry Information Association (SIIA) or Federation Against Software Theft (FAST) be used directly or indirectly to conduct audits, or be recommended by Contractor; (iv) Contractor and Licensee are each entitled to designate a representative who shall be entitled to participate, and who shall mutually agree on audit format, and simultaneously review all information obtained by the audit. Such representatives also shall be entitled to copies of all reports, data or information obtained from the audit; and (v) if the audit shows that such party is not in compliance, Licensee shall be required to purchase additional licenses or capacities necessary to bring it into compliance and shall pay for the unlicensed capacity at the NYS Net Price in effect at time of audit, or if none, then at the Contractor’s U.S. Commercial list price. Once such additional licenses or capacities are purchased, Licensee shall be deemed to have been in compliance retroactively, and Licensee shall have no further liability of any kind for the unauthorized use of the software.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.

  • Return of Customer Data Okta shall return Customer Data to Customer and, to the extent allowed by applicable law, delete Customer Data in accordance with the procedures and time periods specified in the Trust & Compliance Documentation, unless the retention of the data is requested from Okta according to mandatory statutory laws.

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

  • PRODUCT MANUFACTURER'S SUPPLIERS Only those dealers/distributors listed by the manufacturer will be considered authorized to act on behalf of the Product Manufacturer.

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

  • PRICE LISTS AND PRODUCT INFORMATION Contractors should provide an electronic version of the proposed price list in an Excel format or pdf on a jump drive. Also provide a dealer list, if applicable in an Excel format with "read and write" capabilities on the same jump drive. No costs or expenses associated with providing this information in the required format shall be charged to the State of Arkansas. At the time of contract renewal contractor will furnish OSP with an updated dealer list and published price list.

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