Nobody on the record but the work.
Faces, bodies and vehicle plates are blurred on upload — on 100% of frames, before the walk is visible to a single user. The work stays legible; the people don't.
What it does
Blurring runs as part of the upload, not as a review step a busy week can skip. A frame is visible to nobody — not the project team, not the client, not the head office — until the pass has run across it and logged that it did.
The blur is baked into the frame people see. The original is discarded, or held encrypted for the window your policy sets, in the region your policy names. Your privacy officer, and the works council where there is one, can pull a per-walk report of what was blurred and when.
How it works
- 01
Detect on upload
Every frame is scanned for faces, bodies and vehicle plates as it arrives — before indexing, before pinning, and before any user is granted a view of the walk.
- 02
Blur irreversibly
The published frame carries the blur in its pixels. Originals are discarded, or held encrypted for 0–90 days in the region your policy names, and never served to the project team either way.
- 03
Report what ran
Each walk gets a record: frames processed, regions blurred, and any manual redaction added afterwards. Exportable for the works council, the client or an audit.
Spec
- COVERAGE
- 100% OF FRAMES
- TRIGGER
- ON UPLOAD · PRE-INDEX
- RESIDENCY
- EU · US · IN · AU
- ORIGINALS
- POLICY-SET · 0–90 D
100%
Frames blurred before the walk is visible to anyone