> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command/security/privacy-and-security-disclosure/enable-data-sharing-with-verkada.md).

# Enable Data Sharing

Learn how to share data to help Verkada improve its products

## Share camera data with Verkada

Sharing your camera footage with Verkada develops and improves the analytics features across all Verkada cameras.

{% hint style="warning" %}
This is an opt-in feature and is disabled by default. This toggle is separate from the Enable Support Access [toggle](/command/need-help/contact-verkada-support/enable-support-access.md). Opting in allows Verkada Engineering to collect, store, view, and annotate images and video, and to create derivative works, for model training. All data is collected from our Amazon Web Services (AWS) backend and not directly from your cameras. This feature **does not** allow Verkada Support to access your camera’s images and video.

**This setting only applies to sharing camera footage with Verkada for research and development, including model training of our computer vision features. It does not include other event types or system data.**
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Admin.**
{% endstep %}

{% step %}
**In the left navigation, select Data Privacy.**
{% endstep %}

{% step %}
**Toggle on Share camera data with Verkada.**
{% endstep %}

{% step %}
**When you are prompted with the User Agreement, click I Agree to confirm.**

<div align="left" data-with-frame="true"><img src="https://705858581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRq5qDDjsYNxwNzF1bcB%2Fuploads%2Fgit-blob-220d6b41512d64c442c5b37a71ef20b1f86f1960%2Fd887409f3ba95f57fce6200b1e39f133451316c8.png?alt=media" alt="" width="446"></div>
{% endstep %}
{% endstepper %}

***

## Share product data with Verkada

You can also optionally choose to share additional product data with Verkada to support the development and testing of new features. This includes device and event-specific data associated with various Verkada products, such as sensors, access events, alarms, and badge-ins.

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Admin.**
{% endstep %}

{% step %}
**In the left navigation, select Data Privacy.**
{% endstep %}

{% step %}
**Toggle on Share product data with Verkada**
{% endstep %}

{% step %}
**When you are prompted with the User Agreement, click I Agree to confirm.**

<div align="left" data-with-frame="true"><img src="https://705858581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRq5qDDjsYNxwNzF1bcB%2Fuploads%2Fgit-blob-baa354f0da9e733b463b1cacfe84f2e22c5e9f52%2F46628f531ea23d0a6d077ea6093487a0457c4621.png?alt=media" alt="" width="375"></div>
{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/command/security/privacy-and-security-disclosure/enable-data-sharing-with-verkada.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
