> 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/set-a-default-or-camera-specific-location-for-image-and-video-data-storage-and-processing.md).
# Set Data Storage Location
Set your default image and video data location in Verkada Command
Verkada’s standard camera option includes enough on-camera storage capacity for 30 days of continuously recorded video footage. Verkada systems enable you to store your organization’s data in the cloud on AWS, providing backup options worldwide. Learn how Verkada [manages and processes data](https://www.verkada.com/support/dpa/).
{% hint style="danger" %}
The data processing location can only be set while creating an organization. See [Data Storage & Processing Locations](/command/security/privacy-and-security-disclosure/data-storage-processing-locations.md) for more information.
{% endhint %}
***
## Set a default org-level cloud storage location for camera image and video data
Org Admins can set the default cloud storage location of image and video data for their organization. The dropdown is grouped by region: Americas (United States, Canada), EU (Ireland/Dublin, Germany/Frankfurt), and Asia Pacific (Australia, Japan/Tokyo, Singapore, South Korea/Seoul).
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Admin.**
{% endstep %}
{% step %}
**In the left navigation, select Data Privacy > Data Residency.**
{% endstep %}
{% step %}
**Next to Default Image & Video Data Storage Location, click the dropdown and select the desired region for your camera image and video data to be stored. Available regions: United States, Canada, Ireland (Dublin), Germany (Frankfurt), Australia, Japan (Tokyo), Singapore, and South Korea (Seoul).**
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
If a storage-only region (e.g., Canada, Germany/Frankfurt, Japan/Tokyo, Singapore, South Korea) is selected, the data is stored in that region; however, data processing will still occur in the primary processing region for your org (US, EU, or AU).
**This change is not retroactive**. Only data uploaded after the selection will be stored in the new location.
**Storage of the Incident Management feature’s camera image & video data**
* If you create a zip file using the [Incident Management](/verkada-cameras/video-streaming-and-sharing/incident-management.md) feature, copies of the archived clips are stored in the region associated with their original data storage location.
* If the archived clips are stored in the US, the copies used to generate the ZIP file are also stored in the US. If the archived clips come from other regions, the copies are stored in the EU or AU, depending on their original storage location.
* In addition, Incident Management creates a persistent copy of each archived clip in the organization’s selected data storage location when the incident is created. This copy is independent of the original archive and remains available until the incident report is deleted.
{% endhint %}
***
## Set per-camera image and video data storage location
The per-camera storage setting takes precedence over the org-level default. In Verkada Command, from the **Admin** tab, Org Admins and Site Admins can choose to set the data storage location for [individual cameras](#h_c8b86a0616).
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Cameras.**
{% endstep %}
{% step %}
**Select your camera.**
{% endstep %}
{% step %}
**At the bottom right of the camera live feed, click Settings.**
{% endstep %}
{% step %}
**Under Privacy > Camera Image & Video Data Storage Location, click the dropdown and select the desired region for your data to be stored.**
**Available regions: US, Canada, Ireland (Dublin), Germany (Frankfurt), Australia, Japan (Tokyo), Singapore, and South Korea (Seoul).**
{% 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/set-a-default-or-camera-specific-location-for-image-and-video-data-storage-and-processing.md?ask=&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.
