Privacy & security
Real-world data means real people and real premises. Consent, custody and confidentiality are designed into the protocol before a single frame is captured — not retrofitted when your security team asks.
How we work
Every participant and every site owner gives informed, documented consent before recording begins — in a language they actually read.
Data is encrypted from the moment it leaves the capture device until it lands in your bucket.
Least privilege by default. Nobody has standing access to a dataset they are not working on.
Every recording is traceable from the operator who captured it to the moment you receive it.
Written SOPs for collection, handling and delivery — so a security review has something concrete to read.
Confidentiality, IP and data-handling terms written for your project, not a generic template.
Data lifecycle
Six stages, each with a defined owner, a defined control and a defined record.
Recorded to encrypted media on a supervised device. Hashed on the spot so later tampering is detectable.
Encrypted, resumable transfer from the field. Custody is logged at handoff and the local copy is wiped on confirmation.
Reviewed only by named QA staff assigned to your project, inside an access-controlled environment.
Metadata generation and any agreed redaction — face or plate blurring, audio removal, location coarsening.
Pushed to your cloud storage or collected from ours, in the format and structure agreed at scoping.
Held only for the agreed window, then destroyed with a written confirmation of deletion.
Consent
This is the part most data vendors gloss over, and the part that becomes your problem later. We treat participant consent as a deliverable, not a formality — and we can evidence it for every episode in a dataset.
Ask for a sample consent packDe-identification
Some models need faces, most do not. We agree the redaction profile at scoping so you receive exactly the signal you need and nothing you would rather not hold.
Participants and bystanders obscured while hands, tools and objects stay sharp.
Audio dropped entirely, or speech removed while task sounds are preserved.
Documents, screens, badges, plates and branded signage masked on request.
GPS reduced to region, or removed, where precise position is not needed.
Operator and site IDs pseudonymised, with the mapping held apart from the data.
Company-identifying detail removed so a customer's premises cannot be traced.
Compliance posture
We would rather tell you exactly what we have than imply more. Here is our current position, and what we are building toward.
We do not currently hold SOC 2 or ISO 27001 certification. If your procurement process requires one, tell us early and we will discuss timelines rather than work around it.
We would rather answer it before the pilot than during it. Send the document your security team uses and we will complete it and come back with anything we cannot meet.