Verkada systems store all of their data in the cloud, leveraging Backblaze for the storage of some cloud backups in the United States (US) and European Union (EU), and otherwise using AWS cloud services for backup worldwide. Learn how Verkada manages and processes data.
When you first created your organization, if you selected Europe as your data processing location, then the option to set a default data location is not available. All data types will default to Europe.
Set a default location for image and video data
In Verkada Command, Org Admins can set the default image and video data location for their organization as follows:
In Verkada Command, go to All Products > Admin.
In the left navigation, select Privacy & Security > Data Residency.
Next to Default Image & Video Data Location, click the dropdown and select the desired region for your data to be hosted and processed during org creation: US, European Union (EU), Canada (CA), Australia (AU), and South Korea (KR).
This change is not retroactive, so only data uploaded after the selection will be stored in the new location.
Set a specific location for camera image and video data
In Verkada Command, from the Admin tab, Org Admins and Site Admins can set individual cameras to different data storage locations, if desired.
At the top left, click All Products > Cameras .
On the Cameras page, select the desired camera.
At the bottom right of the camera live feed, click Settings .
Only video and image data is stored in the selected data storage location. Camera configurations, authentication, updates, analytics, and so on are processed or stored in the data processing location for your organization (US, EU, AU, or KR) rather than in the camera’s selected data storage location. Also, note that when remote video playback is used, image and video data is proxied through our AWS infrastructure in your organization’s chosen data processing location (US, EU, AU, KR), even if you have selected a different data storage location. See this Data Residency & Processing page for more information.
In addition, if you create a zip file using the Incident Management feature and have chosen only archive clips with a storage location in the US, copies of the archived clips are temporarily stored in the US to facilitate the creation of the zip file. For zip files consisting of archive clips from different regions, clip copies are temporarily stored in the EU.
Feature details
Only video and image data is stored in the selected data storage location for a given camera. Other types of data relating to the use of your camera will be processed and stored in your organization’s chosen data processing location (US, EU, AU, and KR). These include authentication data, metadata, remote video playback, and so on.
Video data
Feature | Details | US | EU | CA | AU | KR |
Local network video playback | When possible, cameras default to streaming over the local network when a user and device are authenticated. | ◉
| ◉ | ◉
| ◉ | ◉ |
Cloud backup data | Every Verkada camera comes with 30 days worth of free cloud backup storage. This feature is enabled on a per-camera basis. If cloud backup has been configured and a camera goes offline:
| ◉
| ◉ | ◉
| ◉ | ◉ |
Archives | Archives are stored using AWS cloud storage services, and these are stored on the corresponding region configured.
When you archive a video clip in Command, the files are retained in Verkada’s cloud service indefinitely until one of these events occurs:
| ◉
| ◉ | ◉
| ◉ | ◉ |
Thumbnails | Thumbnails are stored using AWS cloud storage services, and these are stored on the corresponding region configured. Thumbnails are briefly stored in camera memory before being uploaded to the cloud.
Note: This data remains in the cloud as long as the camera retention or extended cloud backup retention allows. After this period, the Verkada system automatically deletes the oldest thumbnails. | ◉
| ◉ | ◉
| ◉ | ◉ |
Outside of the onboard retention and cloud backup retention of the camera, no versions or copies of the video are retained by Verkada, unless the video has been archived or the customer has consented to the retention.
Need more help? Contact Verkada Support.