Data De-Identification Sample Clauses

Data De-Identification. Service Provider may have permission via any underlying agreement to provide goods or services to use de-identified CDI for purposes as identified in the agreement. De-identified CDI will have all direct and indirect personal identifiers removed. This includes, but is not limited to, name, identification numbers, date of birth, demographic information, location information and school identification numbers. Service Provider agrees not to attempt to re-identify de-identified CDI and agrees not to transfer de-identified CDI to any party without permission. Any receiving party shall agree in writing not to attempt re- identification and shall agree to be bound by the terms of this Data Agreement.
Sample 1Sample 2Sample 3See All (15)
AutoNDA by SimpleDocs
Data De-Identification. VENDOR may use de- identified Data for product development, research, or other internal purposes. De-identified Data will have all direct and indirect personal identifiers removed. This includes, but is not limited to, name, ID numbers, date of birth, demographic information, location information, and school ID. Furthermore, VENDOR agrees not to attempt to re-identify de- identified Data.
Sample 1Sample 2Sample 3See All (9)
Data De-Identification. A. Provider may use de-identified Data for product development, research, or other purposes. De-identified Data will have all direct and indirect personal identifiers removed. This includes, but is not limited to, name, identification numbers, dates of birth, demographic information, location information, and school identification. Further, Provider agrees not to attempt to re-identify de-identified Data and not to transfer de-identified Data to any party authorized to receive such Data pursuant to this Agreement unless that party agrees not to attempt re-identification.
Sample 1Sample 2See All (4)
Data De-Identification. De-identified Confidential Data will have all direct and indirect personal identifiers removed, including any data that could be analyzed and linked to other data to identify the student or family member / guardian. This includes, at a minimum the following: student name, address, telephone numbers, email addresses, photograph, place and date of birth, attendance record, grade level, course enrollment information, physical descriptors and user ID number (or other unique personal identifier as necessary to participate in the services provided under this Agreement). Furthermore, Contractor agrees not to attempt to re-identify de-identified Confidential Data and not to transfer de-identified Confidential Data to any party unless:
Sample 1
Data De-Identification. Service Provider may have permission via any underlying agreement to provide goods or services to use de‐identified CDI for purposes as identified in the agreement. De‐identified CDI will have all direct and indirect personal identifiers removed. This includes, but is not limited to, name, identification numbers, date of birth, demographic information, location information and school identification numbers. Service Provider agrees not to attempt to re‐identify de‐identified CDI and agrees not to transfer de‐ identified CDI to any party without permission, except to fulfill its obligations under any underlying service agreement or as required by law. Any receiving party shall agree in writing not to attempt re‐identification and shall agree to be bound by the terms of this Data Agreement.
Sample 1
Data De-Identification. A. Upon approval by the District, provider may use de-identified Data for product development, research, or other purposes.
Sample 1
Data De-Identification. Contractor may use aggregated or de-identified student data only for product development, research, or other purposes expressly permitted by the Family Rights and Privacy Act (FERPA). Contractor must have approval of the MCSB to publish or market MCSB data.
Sample 1
AutoNDA by SimpleDocs
Data De-Identification. A. Provider may use de-identified Data for product development, research, or other purposes and all resulting intellectual property shall belong solely to Provider. De-identified Data will have all direct and indirect personal identifiers removed. This includes, but is not limited to, name, identification numbers, dates of birth, demographic information, location information, and school identification. Further, Provider agrees not to attempt to re-identify de-identified Data and not to transfer de-identified Data to any party authorized to receive such Data pursuant to this Agreement unless that party agrees not to attempt re-identification.
Sample 1

Related to Data De-Identification

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

  • Client identification 9.1. The Company has the right to require the Client to confirm his/her registration information specified when opening a trading account. To do so, the Company may ask the Client at its own discretion and at any time to provide a notarized electronic copy of his/her identification document, bank statement or public utilities xxxx as a proof of residence. In particular cases, the Company may ask the Client to provide a photo of him/her holding his/her ID near his/her face. The detailed client identification requirements are set out in the “AML policies” section on the Company’s official site.

  • Product Identification Before removal from Sale Area, unless Contracting Officer determines that circumstances warrant a written waiver or adjustment, Purchaser shall:

  • Customer Identification Unless Elastic has first obtained Customer's prior written consent, Elastic shall not identify Customer as a user of the Products, on its website, through a press release issued by Elastic and in other promotional materials.

  • T1 IDENTIFICATION PROCEDURES During the restoration of service after a disaster, BellSouth may be forced to aggregate traffic for delivery to a CLEC. During this process, T1 traffic may be consolidated onto DS3s and may become unidentifiable to the Carrier. Because resources will be limited, BellSouth may be forced to "package" this traffic entirely differently then normally received by the CLECs. Therefore, a method for identifying the T1 traffic on the DS3s and providing the information to the Carriers is required.

Time is Money Join Law Insider Premium to draft better contracts faster.