RESEARCH DATA USE AGREEMENT
RESEARCH DATA USE AGREEMENT
Colorado, US
Agreement date: [date]
Provider: [legal name and entity type], of [address], notice email [email] (Provider).
Recipient: [legal name and entity type], of [address], notice email [email] (Recipient).
Principal Investigator: [name and institution] (Investigator).
1. Data and research
Provider grants Recipient a limited, nonexclusive, nontransferable right during the Term to access and use the data described in Schedule 1 (Data) solely for the research protocol and questions stated there (Research). Data includes the listed files, documentation, updates and derived row-level data. It does not include direct identifiers, protected health information, substance-use-disorder records, education records, biometric identifiers or other regulated data unless Schedule 1 expressly identifies the category and the parties sign every additional agreement and authorization required by law.
Provider retains its rights in the Data. No ownership of Data, database rights, patents or trademarks transfers. Recipient owns its original analysis code and results that do not reproduce Data or permit identification, subject to Provider's underlying rights and the review rules below.
2. Permitted users and environment
Only Investigator and the named personnel in Schedule 2 (Authorized Users) may access Data. Each must be bound by confidentiality and use restrictions at least as protective as this agreement and complete the stated training. Recipient shall keep Data only in the approved environment, apply least-privilege access, multifactor authentication where supported, encryption in transit and at rest, logging, backup protection and the other safeguards in Schedule 2. Recipient shall not place Data in a public repository, personal account or unapproved artificial-intelligence or analytics service.
Recipient may not disclose Data, contact a data subject, use Data for employment, credit, insurance, advertising or another consequential decision, or use it to train a generally available model. A subcontractor or cloud provider may receive Data only with Provider's prior written approval and a binding agreement imposing the same restrictions. Recipient remains responsible for each Authorized User and subcontractor.
3. No re-identification
Recipient shall not attempt to identify or contact an individual represented in Data, link Data with another dataset for identification, or permit another person to do so. If Recipient inadvertently identifies a person or discovers a re-identification method, it shall stop the affected work, notify Provider promptly, disclose the identity to no one except as legally required, and follow Provider's reasonable containment instructions. Recipient shall maintain technical and organizational controls separating any key or information capable of identification.
4. Legal and ethics conditions
Each party shall comply with the laws applicable to its role and the Research. Before access, Recipient shall obtain and maintain every institutional review board approval, exemption determination, consent, authorization or data-governance approval identified in Schedule 1. Recipient shall not materially change the protocol, population, purpose or data linkage without Provider's written approval and any required ethics review.
The parties shall not assume that research status exempts processing from the Colorado Privacy Act. If a statutory research or health-data exemption applies, the party relying on it bears responsibility for documenting the basis and limiting processing to the exempt purpose. If Provider is a controller and Recipient processes personal data only on Provider's instructions, Schedule 3 is binding processing instructions and the parties shall comply with clause 5. If Recipient determines purposes or means beyond those instructions, Recipient acts as an independent controller for that processing and assumes the corresponding duties.
5. Colorado processor terms
When Recipient acts as Provider's processor, Recipient shall adhere to Schedule 3; process only for the stated nature, purpose, data types and duration; ensure each person with access has a confidentiality duty; assist Provider with authenticated rights requests, security obligations, breach notification and required data-protection assessments; and make compliance information available. At Provider's choice, Recipient shall return or delete personal data at the end of services unless law requires retention.
Recipient shall give Provider an opportunity to object before adding a subcontractor and shall use a written flow-down contract. Recipient shall allow and contribute to reasonable audits and inspections, or with Provider's consent arrange at least annually for a qualified independent audit using an accepted standard and provide the report on request. The parties allocate security responsibilities in Schedule 2. No term relieves either party from liability imposed by its actual role.
6. Incident response
Recipient shall notify Provider without unreasonable delay, and no later than [24] hours after discovery, of unauthorized access, acquisition, use, disclosure, loss or material compromise of Data (Incident). Recipient shall contain and investigate the Incident, preserve evidence, provide known material facts, cooperate with legally required notices and remediation, and not notify affected persons in Provider's name without approval unless law requires it. This contractual period does not extend a shorter statutory deadline.
7. Results and publication
Recipient may publish Research results only in aggregate or another form that does not disclose Data or permit reasonable identification. At least [30] days before submission or public release, Recipient shall give Provider the proposed output solely to identify Data disclosure, security risk, confidentiality breach or Provider-owned patentable subject matter. Provider may require correction of a disclosure or delay release up to [60] additional days to file a patent application, but may not suppress or alter findings because they are unfavorable. Authorship and attribution follow the standards stated in Schedule 1, not access alone.
8. Term, return and deletion
The Term begins on [date] and ends on [date]. Provider may suspend access immediately for a material security or legal risk. Either party may terminate for a material breach not cured within ten days after detailed notice, or immediately when continued use would be unlawful or an ethics approval is withdrawn. At expiration or termination, Recipient shall stop use and, at Provider's choice, return or securely delete Data and derived row-level copies, then certify completion. Recipient may retain only a copy required by law or documented research-integrity policy, isolated from further research use and protected until deletion.
9. Assurances and liability
Provider represents that it has authority to provide the Data for the stated Research and has accurately described known use restrictions. Except for that representation, Data is provided as is without a promise that it is complete, error-free or fit for a particular result. Recipient is responsible for research design, analysis and conclusions.
Each party shall be responsible for losses and third-party claims to the extent caused by its breach, negligence, willful misconduct or violation of law. No limitation excludes liability that cannot lawfully be limited. Schedule 1 states any agreed cap or insurance; if blank, no contractual cap is created.
10. General terms
Colorado law governs. This agreement and its schedules are the entire data-use arrangement. An amendment must be signed by both parties. Recipient may not assign or transfer access without Provider's written consent. Notices are effective on personal or tracked delivery or acknowledged email. Invalid language is narrowed or severed. Counterparts and electronic signatures are permitted.
SCHEDULE 1 — DATA AND RESEARCH
Dataset name, version, fields, format and volume: [details].
Data-source population and collection period: [details].
Direct identifiers removed and residual identifiability: [details].
Regulated categories and applicable exemptions or additional agreements: [details or none].
Research protocol, questions and prohibited uses: [details].
Ethics approval, exemption or consent basis: [institution, identifier and date].
Permitted outputs, attribution and publication plan: [details].
Term, liability cap if any, and required insurance: [details].
SCHEDULE 2 — USERS AND SECURITY
Authorized Users and roles: [names].
Approved systems, locations and vendors: [details].
Access, encryption, logging, backup, retention and destruction controls: [details].
Incident contacts: [details].
SCHEDULE 3 — PROCESSING INSTRUCTIONS, IF APPLICABLE
Controller and processor roles: [details].
Nature and purpose of processing: [details].
Personal-data types and data-subject categories: [details].
Processing duration: [details].
Approved subprocessors and objection process: [details].
Security and consumer-rights responsibility allocation: [details].
PROVIDER
Signature: ____________________ Date: __________
Name and title: [name and title]
RECIPIENT
Signature: ____________________ Date: __________
Name and title: [name and title]
Licensed under CC BY 4.0. Attribution is required when you publish or redistribute this Template or an adapted version to the public. Attribution is not required merely because you use or adapt the Template for your own business or legal purposes, including preparing, negotiating, signing, or exchanging an agreement with a counterparty. License details.