Customer Data and Statistical Data
Customer Data and Statistical Data Sample Clauses
Related to Customer Data and Statistical Data
Customer Data 5.1 The Customer shall own all right, 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.
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.
Market Data Zero Hash may make certain information and research data, including historical market information available to you through the Platform or Zero Hash System, as applicable (“Market Data”). Market Data may be provided through third-party providers and may be updated at different time intervals, and accordingly, quotes, news, research data, market information and the various trade status reports, including intraday updates of balances and positions information and may differ due to the different Market Data and sources and their update intervals. Any such Market Data is provided as-is and for informational purposes only. Zero Hash makes no representation as to the accuracy or completeness of any Market Data. Further, Market Data may represent aggregated data from across multiple third-party trading venues and does not necessarily represent the prices of any asset as made available by Zero Hash or ZH Liquidity. Your reliance on any Market Data is at your sole discretion. The provision of Market Data relating to any asset shall not be considered Zero Hash’s, or its affiliates, endorsement of any such asset. You understand and agree that past performance of any asset is not indicative of future performance. You shall not decompile or redistribute any Market Data.
Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, NTBS 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.
User Data In addition to any disclosures authorized by Section 24, You and Your Authorised Users consent and agree that the RIM Group of Companies may access, preserve, and disclose Your or Your Authorised Users' data, including personal information, contents of your communication or information about the use of Your BlackBerry Solution functionality and the services or software and hardware utilized in conjunction with Your BlackBerry Solution where available to RIM ("User Data"), to third parties, including foreign or domestic government entities, without providing notice to You or Your Authorized Users under the laws of countries where the RIM Group of Companies and its service providers, other partners and affiliates are located in order to: (i) comply with legal process or enforceable governmental request, or as otherwise required by law; (ii) cooperate with third parties in investigating acts in violation of this Agreement; or (iii) cooperate with system administrators at Internet service providers, networks or computing facilities in order to enforce this Agreement. You warrant that You have obtained all consents necessary under applicable law from Your Authorised Users to disclose User Data to the RIM Group of Companies and for the RIM Group of Companies to collect, use, process, transmit, and/or disclose such User Data as described above.
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 B.
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.
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.
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.
