> For the complete documentation index, see [llms.txt](https://docs.volt.ai/volt/8EnMblOhYy6VQJFNi0Vz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.volt.ai/volt/8EnMblOhYy6VQJFNi0Vz/faq/privacy-security.md).

# Privacy/Security

## Questions

1. [Is VOLT SOC 2 compliant?](#is-volt-ai-soc2-compliant)
2. [What does VOLT do with camera data?](#what-does-volt-ai-do-with-our-camera-data)
3. [How long does VOLT retain data?](#how-long-is-data-retention-and-how-is-it-secure-on-the-cloud)
4. [Why do we need to whitelist ports?](#why-do-we-need-to-whitelist-ports)

## Answers

### Is VOLT SOC 2 compliant?

Yes! We are SOC 2 Type 2 compliant, to request a copy of our report please contact <_help@volt.ai>.\_

### What does VOLT do with camera data?

On-prem solution: All camera data is processed on the edge device(s) by our AI models. If an incident is detected, the relevant metadata will be encrypted and transmitted to the cloud.&#x20;

Cloud solution: Camera data is encrypted and sent to the cloud for processing by our AI models.

### How long does VOLT retain data?

Incident data is encrypted and stored on the cloud for 1 year, this can be configured.

Regular recordings are available for up to two weeks, depending on your configuration.

### Why do we need to whitelist ports?

Domains and their associated IP addresses are tied to servers on the internet. Our hardware needs the ability to send data (not readable by humans) to some domains - including AWS, intrusion and antivirus software, and a few others for software and security updates. These domains are the only entity that can access volt servers, and only in one direction - outbound.

<br>


---

# 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://docs.volt.ai/volt/8EnMblOhYy6VQJFNi0Vz/faq/privacy-security.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.