> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vangrid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Privacy at capture

> Faces and number plates are blurred on the device before the video is encoded. Unblurred frames never leave the phone.

Vangrid's privacy model is architectural rather than a policy statement. The filtering happens on the contributor's device, at the moment of recording, before anything is transmitted.

## What happens on the device

While a contributor records, the app detects faces and vehicle number plates in each frame and obscures them. The obscured frames are what get encoded into the video file.

The consequence is the part that matters: **the unblurred frames never leave the device.** They are not uploaded, not stored, and not recoverable later. Vangrid never holds a version of the capture in which a face or a number plate is legible.

> [!NOTE]
>
> No automated detector is perfect. Contributors remain responsible for not recording what should not be recorded, and anyone who appears in a capture can ask for removal or further obscuring. See [Privacy Policy](https://docs.vangrid.io/legal/privacy-policy.md).

## What Vangrid holds

The blurred video is uploaded and reconstructed into a 3D model. Vangrid holds both: the blurred capture and the model derived from it.

Contributors keep control of their own footage. It is never handed to a buyer.

## What a buyer receives

| | Delivered to buyers | Not delivered |
| - | - | - |
| Reconstructed 3D model | Yes | |
| Geometry, classification, ground truth score | Yes | |
| Provenance record | Yes | |
| The contributor's video | | Never |
| Unblurred frames | | Do not exist off the device |

A buyer reviewing a bounty submission sees enough to judge it against their brief. On acceptance they receive the reconstructed model. At no point do they receive the source video.

## Privacy zones

Contributors can designate personal privacy zones, such as a home or a workplace, where capture is disabled. Network level privacy zones around sensitive locations are enforced on the server, and uploads inside them are rejected.

## Where uploads are unavailable

Uploads are blocked in some regions for legal reasons, based on the location of the capture and the contributor's network region.

## Your queries

Query parameters are not retained beyond the request lifecycle. Results are scoped to the regions your API key is authorised for, and query history is not shared between customers.

> [!TIP]
>
> If your use case requires data residency guarantees, see [Data sovereignty](https://docs.vangrid.io/data/data-sovereignty.md) or write to [hello@vangrid.io](mailto:hello@vangrid.io).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.