> For the complete documentation index, see [llms.txt](https://contacttracingplaybook.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://contacttracingplaybook.org/how-to-do-contact-tracing/data-management-systems/negotiating-data-rights-with-vendors.md).

# Negotiating data rights with vendors

Software vendors may attempt to contract their ownership over data in an attempt to lock in customers. Programs must avoid this by specifying in the vendor contract that vendors do not own any data via a “data rights” clause such as:

“Consistent with [FAR 52.227-14](https://www.acquisition.gov/content/52227-14-rights-data-general), which applies to this agreement, the State intends that data stored within the software provided by the Contractor will be owned by the State.”

Programs must also specify in the vendor contract that the vendor agrees to export records in a machine-readable format (defined as “data in a format that can be easily processed by a computer without human intervention while ensuring no semantic meaning is lost”), and the software must likewise be demonstrated to provide such functionality.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://contacttracingplaybook.org/how-to-do-contact-tracing/data-management-systems/negotiating-data-rights-with-vendors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.