De-Identified Data Use Sample Clauses

De-Identified Data Use. INAP and its licensors may use certain content and transaction information to create information that is de-identified, such that it cannot be identified to the Customer, and which is sometime referred to as “big data” (hereinafter “Content”). Content may be used and disclosed consistent with applicable law. Customer grants to INAP and its licensors a non-exclusive right and license to use Content including the right of aggregation with data received from other customers, suppliers and users of INAP services for the general provision of data aggregation and comparison services, statistical analysis, the creation and maintenance of comparative databases, product support and development, system analytics, and benchmarking analysis, so long as INAP does not identify Customer or any individual person associated with Customer and the data remains in an aggregated form. To the extent that the Content has been de-identified, and notwithstanding anything set forth herein to the contrary in this Agreement, INAP may retain such Content, provided that such Content shall be used or disclosed solely for such purposes provided in this Section.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
De-Identified Data Use. De-identified data may be used regardless of opt-in/out for population reporting, business intelligence, mapping, program and service evaluation, analytic and statistical purposes, and other purposes that do not require use of or would indirectly reveal patient/beneficiary identifiers.
Sample 1Sample 2
De-Identified Data Use. QIAGEN may utilize data capture, syndication and analysis tools, and other similar tools, to create, extract, compile, keep, aggregate or synthesize data, usage patterns or information which has been de-identified consistent with applicable data privacy laws and associated data protection standards resulting from Customers’ use of the Licensed Materials, which shall include but not be limited to, Customer Biological Data and Results (“De-identified Data”). QIAGEN may
Sample 1

Related to De-Identified Data Use

  • De-Identified Data Provider agrees not to attempt to re-identify de-identified Student Data. De-Identified Data may be used by the Provider for those purposes allowed under FERPA and the following purposes:

  • If Identified If the HSP is Identified it will:

  • Covered Data All instances of "Student Data" should be replaced with "LEA Data". The protections provided within this DPA extend to all data provided to or collected by the Provider.

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.

  • Categories of Data Subjects Any individual accessing and/or using the Services through the Customer's account ("Users"); and any individual: (i) whose email address is included in the Customer's Distribution List; (ii) whose information is stored on or collected via the Services, or (iii) to whom Users send emails or otherwise engage or communicate with via the Services (collectively, "Subscribers").

  • Personally Identifiable Information By submitting any of your personally identifiable information, such as your name, address, email address, phone number or fax number, to us, you consent to our privacy policy located at xxx.xxxxxxxx.xxx/xxxxx.

  • Categories of Data Subject 2.1. When using this Service, the groups of individual’s data by category • Your end users using the service that you deliver • The personal data about your employees and contractors that bookinglab collects as a Customer of ours to complete account administration and set up

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