De-Identification of Data Sample Clauses

De-Identification of Data. We reserve the right to remove those elements of data that might be used to associate data with You or any other individual, or to “de-identify” the data We collect, and to use and share such de-identified data for furthering Our mission. Aggregated, de-identified data may also be used for health trend analysis, disease control, in assessing the effectiveness of various health programs, research, and for other data analytics and purposes. Depending on the circumstances, We may or may not charge third parties for this de-identified data. By using the Services, You grant Us the right to accept payment or other remuneration for such aggregated, de-identified data. We require parties with whom We share aggregated, de-identified data to agree that they will not try to make this information personally identifiable.
AutoNDA by SimpleDocs
De-Identification of Data. MP Organisations disclosing data to other MP Organisations in a de-identified format must satisfy themselves that the data is appropriately de-identified to meet their legislative obligations3, 9. MP Organisations will work together to facilitate this decision making through agreed understanding of circumstances where data has been effectively de-identified so as not to be reasonably6 re-Identifiable, noting that this is a dynamic environment. While not binding on some MP Organisation’s, the Australian National Data Service (ANDS) have published a De-identification Guide10, which may be used to assist in that shared understanding of the concept of de-identification. The resources listed below also provide guidance for choosing and documenting effective de-identification processes prior to submission to a HREC for the necessary approval. 3 Office of the Australian Information Commissioner 2018, De-identification and the Privacy Act, Australian Government, Accessed 24 August 2020, <xxxxx://xxx.xxxx.xxx.xx/xxxxxxxx-xxx- organisations/guides/de-identification-and-the-privacy-act> 6The State of Victoria Department of Environment, Land, Water and Planning 2015, Guide to Privacy Terms. Privacy and Data Protection Act 2014, Accessed 02 September 2020, <xxxxx://xxx0.xxxxx.xxx.xxx.xx/ data/assets/pdf_file/0029/46838/Guide-to-Privacy-terms-March- 2017.pdf> 9 Office of the Australian Information Commissioner 2017, De-Identification Decision-Making Framework, Australian Government, Accessed 24 August 2020, <xxxxx://xxxxxxxxxxxx.xxxxx.xx/xxx/xxxxxxxx?xxx=xxxxx:XX000000&dsid=DS3> 10 Australian National Data Service 2018, ANDS De-identification guide, National Collaborative Research Infrastructure Strategy, Accessed 24 August 2020, <xxxxx://xxx.xxxx.xxx.xx/ data/assets/pdf_file/0003/737211/De-identification.pdf>
De-Identification of Data. District hereby grants to Vendor a license to (i) use data collected or accessed by Vendor under this agreement if, and only if, Vendor de-identifies the data so that the is no longer connected or capable of being connected to an identifiable individual student or person.; and (ii) and analyze such de-identified data to improve Vendor’s educational products and services, including to create aggregated or statistical insights and baseline reports that are not identifiable to individuals or institutions for use in Vendor’s other educational products and services. The rights granted in this provision shall survive the expiration or termination of this Agreement and override any deletion/destruction/return obligations herein. ACCEPTED AND AGREED Vendor: Bedford, Xxxxxxx & Worth Publishing Group LLC Signature: _ _ Date: 2/28/2022 Printed Name: Xxxxx Xxxxx Title: VP of Operations email : xxxxxxxxx@xxxxxx.xxx District: Park Hill School District Signature: _ _ Date: _ Printed Name: Title: _ email : Vendor agrees to provide the following products and services (please check all that apply):
De-Identification of Data. The Participant acknowledges and agrees that the Participant Data stored in the Registry will only include de-identified data, in accordance with the de-identification standards included in the Health Information Portability and Accountability Act of 1996, as codified at 42 U.S.C. §1320d (“HIPAA”) and its corresponding regulations. Certain patient identifiers provided by Participants are combined in a one-way hash by Vendor in an automated process resulting in an encrypted Registry database entry key which cannot be used to reproduce the original patient identifiers (the “Patient Identification Number”). Participant is solely responsible for maintaining and ensuring the confidentiality of the Patient Identification Number, and any direct patient identifiers utilized in the production of such number by the Vendor, in accordance with all applicable laws, including, but not limited to, HIPAA.

Related to De-Identification of Data

  • Identification of Data a. All Background, Third Party Proprietary and Controlled Government Data provided by Disclosing Party shall be identified in the Annex under which it will be provided. b. NASA software and related Data provided to Partner shall be identified in the Annex under which it will be used. Notwithstanding H.4., Software and related Data will be provided to Partner under a separate Software Usage Agreement (SUA). Partner shall use and protect the related Data in accordance with this Article. Unless the SUA authorizes retention, or Partner enters into a license under 37 C.F.R. Part 404, the related Data shall be disposed of as instructed by NASA.

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

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

  • Protection of Data The Contractor agrees to store Data on one or more of the following media and protect the Data as described: a. Hard disk drives. For Data stored on local workstation hard disks, access to the Data will be restricted to Authorized User(s) by requiring logon to the local workstation using a Unique User ID and Hardened Password or other authentication mechanisms which provide equal or greater security, such as biometrics or smart cards. b. Network server disks. For Data stored on hard disks mounted on network servers and made available through shared folders, access to the Data will be restricted to Authorized Users through the use of access control lists which will grant access only after the Authorized User has authenticated to the network using a Unique User ID and Hardened Password or other authentication mechanisms which provide equal or greater security, such as biometrics or smart cards. Data on disks mounted to such servers must be located in an area which is accessible only to authorized personnel, with access controlled through use of a key, card key, combination lock, or comparable mechanism. For DSHS Confidential Information stored on these disks, deleting unneeded Data is sufficient as long as the disks remain in a Secure Area and otherwise meet the requirements listed in the above paragraph. Destruction of the Data, as outlined below in Section 8 Data Disposition, may be deferred until the disks are retired, replaced, or otherwise taken out of the Secure Area. c. Optical discs (CDs or DVDs) in local workstation optical disc drives. Data provided by DSHS on optical discs which will be used in local workstation optical disc drives and which will not be transported out of a Secure Area. When not in use for the contracted purpose, such discs must be Stored in a Secure Area. Workstations which access DSHS Data on optical discs must be located in an area which is accessible only to authorized personnel, with access controlled through use of a key, card key, combination lock, or comparable mechanism. d. Optical discs (CDs or DVDs) in drives or jukeboxes attached to servers. Data provided by DSHS on optical discs which will be attached to network servers and which will not be transported out of a Secure Area. Access to Data on these discs will be restricted to Authorized Users through the use of access control lists which will grant access only after the Authorized User has authenticated to the network using a Unique User ID and Hardened Password or other authentication mechanisms which provide equal or greater security, such as biometrics or smart cards. Data on discs attached to such servers must be located in an area which is accessible only to authorized personnel, with access controlled through use of a key, card key, combination lock, or comparable mechanism.

  • Service Information Pages Verizon shall include all CBB NXX codes associated with the geographic areas to which each directory pertains, to the extent it does so for Verizon’s own NXX codes, in any lists of such codes that are contained in the general reference portion of each directory. CBB’s NXX codes shall appear in such lists in the same manner as Verizon’s NXX information. In addition, when CBB is authorized to, and is offering, local service to Customers located within the geographic area covered by a specific directory, at CBB’s request, Verizon shall include, at no charge, in the “Customer Guide” or comparable section of the applicable alphabetical directories, CBB’s critical contact information for CBB’s installation, repair and Customer service, as provided by CBB. Such critical contact information shall appear alphabetically by local exchange carrier and in accordance with Verizon’s generally applicable policies. CBB shall be responsible for providing the necessary information to Verizon by the applicable close date for each affected directory.

  • Customer Identification Program Notice To help the U.S. government fight the funding of terrorism and money laundering activities, U.S. Federal law requires each financial institution to obtain, verify, and record certain information that identifies each person who initially opens an account with that financial institution on or after October 1, 2003. Certain of PNC’s affiliates are financial institutions, and PNC may, as a matter of policy, request (or may have already requested) the Fund’s name, address and taxpayer identification number or other government-issued identification number, and, if such party is a natural person, that party’s date of birth. PNC may also ask (and may have already asked) for additional identifying information, and PNC may take steps (and may have already taken steps) to verify the authenticity and accuracy of these data elements.

  • Partnership Formation and Identification 6 2.1 Formation............................................................................................ 6 2.2 Name, Office and Registered Agent.................................................................... 6 2.3 Partners............................................................................................. 6 2.4

  • Marking of Data Pursuant to Paragraph A above, any Data delivered under this Agreement shall be marked with the following legend: Use, duplication, or disclosure is subject to the restrictions as stated in Agreement HR0011-XX-9-XXXX between the Government and the Performer.

  • Further Identification of Collateral Each Debtor will, when and as often as requested by the Secured Party or its Representative, furnish to the Secured Party or such Representative, statements and schedules further identifying and describing the Collateral and such other reports in connection with the Collateral as the Secured Party or its Representative may reasonably request, all in reasonable detail.

  • Identification of Goods Identification of the goods shall not be deemed to have been made until both Buyer and Seller have agreed that the goods in question are to be appropriate to the performance of this Agreement.

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