Customer Data; Aggregated Anonymous Statistical Data Sample Clauses

Customer Data; Aggregated Anonymous Statistical Data. Customer Data shall be deemed the Confidential Information of Customer and MobileIron agrees that it shall maintain appropriate administrative, physical, and technical safeguards for protection of the security, confidentiality and integrity of Customer Data. MobileIron shall not transfer, disclose or access Customer Data, except (i) as compelled by law or (ii) as expressly permitted herein or by Customer or (iii) to implement and deliver the features and services associated with the normal use of the Cloud Services and/or to perform its obligations hereunder, including support, or (iv) to help Customer prevent or address service or technical problems. MobileIron (and/or its contractors) may collect aggregated, anonymous, statistical data and information about devices and usage activity provided such data and information does NOT contain any information specifically identifiable to any individual or Customer (“Aggregated Anonymous Data”), and MobileIron (and/or its contractors) may use, store, analyze, and disclose such Aggregate Anonymous Data. For clarity, Aggregate Anonymous Data shall only include aggregated data or information which is specifically NOT identifiable to any individual or Customer. Aggregate Anonymous Data shall be owned by MobileIron.
AutoNDA by SimpleDocs

Related to Customer Data; Aggregated Anonymous Statistical Data

  • Statistical Data The statistical, industry-related and market-related data included in the Registration Statement, the Sale Preliminary Prospectus, and/or the Prospectus are based on or derived from sources that the Company reasonably and in good faith believes are reliable and accurate, and such data materially agree with the sources from which they are derived.

  • Statistical, Demographic or Market-Related Data All statistical, demographic or market-related data included in the Registration Statement, the Disclosure Package or the Prospectus are based on or derived from sources that the Company believes to be reliable and accurate and all such data included in the Registration Statement, the Disclosure Package or the Prospectus accurately reflects the materials upon which it is based or from which it was derived.

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

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS 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.

  • Statistical Information Any third-party statistical and market-related data included in the Registration Statement, the Time of Sale Disclosure Package and the Prospectus are based on or derived from sources that the Company believes to be reliable and accurate in all material respects.

  • Customer Data 5.1 The Customer shall own all rights, title and interest in and to all of the Customer Data and shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data. 5.2 The Supplier shall follow its archiving procedures for Customer Data as set out in its Back-Up Policy available at XxxxxXXX.xxx or such other website address as may be notified to the Customer as such document may be amended by the Supplier in its sole discretion from time to time the current version of which is set out at Schedule 3 of this Agreement. In the event of any loss or damage to Customer Data, the Customer's sole and exclusive remedy shall be for the Supplier to use reasonable commercial endeavours to restore the lost or damaged Customer Data from the latest back-up of such Customer Data maintained by the Supplier in accordance with the archiving procedure described in its Back-Up Policy. The Supplier shall not be responsible for any loss, destruction, alteration or disclosure of Customer Data caused by any third party (except those third parties sub-contracted by the Supplier to perform services related to Customer Data maintenance and back-up). 5.3 The Supplier shall, in providing the Services, comply with its Privacy and Security Policy as such document may be amended from time to time by the Supplier in its sole discretion. 5.4 If the Supplier processes any personal data on the Customer’s behalf when performing its obligations under this agreement, the parties record their intention that the Customer shall be the data controller and the Supplier shall be a data processor and in any such case: (a) the Customer shall ensure that the Customer is entitled to transfer the relevant personal data to the Supplier so that the Supplier may lawfully use, process and transfer the personal data in accordance with this agreement on the Customer's behalf; (b) the Customer 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 legislation; (c) the Supplier shall process the personal data only in accordance with the terms of this agreement and any lawful instructions reasonably given by the Customer from time to time; and (d) 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. 5.5 The Supplier and the Customer shall comply with their respective obligations as set out in Schedule 4 of this Agreement

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

  • Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.‌ b. A description or identification of the statistical sampling software package used by the IRO.‌

  • Financial Statements Statistical Data 2.6.1. The financial statements, including the notes thereto and supporting schedules included in the Registration Statement and the Prospectus, fairly present the financial position and the results of operations of the Company at the dates and for the periods to which they apply. Such financial statements have been prepared in conformity with generally accepted accounting principles of the United States, consistently applied throughout the periods involved, and the supporting schedules included in the Registration Statement present fairly the information required to be stated therein. No other financial statements or supporting schedules are required to be included in the Registration Statement. The Registration Statement discloses all material off-balance sheet transactions, arrangements, obligations (including contingent obligations), and other relationships of the Company with unconsolidated entities or other persons that may have a material current or future effect on the Company's financial condition, changes in financial condition, results of operations, liquidity, capital expenditures, capital resources, or significant components of revenues or expenses. There are no pro forma or as adjusted financial statements which are required to be included in the Registration Statement and the Prospectus in accordance with Regulation S-X which have not been included as so required. 2.6.2. The statistical, industry-related and market-related data included in the Registration Statement and the Prospectus are based on or derived from sources which the Company reasonably and in good faith believes are reliable and accurate, and such data agree with the sources from which they are derived.

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

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