Security & privacy
A posture you can read, with the findings left in.
We publish a pentest ledger rather than a badge. It lists what was tested, what held, and what is still open. In a category built on marketing, a ledger with open items is the more useful document.
| Property | How it is done | Qualifier |
|---|---|---|
| Footage location | Written to storage on the machine you run it on; two local tiers with a daily lifecycle pass | No off-premises destination exists in the architecture |
| Secrets | Held in a sealed vault that sits off the bus, not in the config the modules read | Per-class uid identity for every module |
| Transport to the phone | TLS 1.3 with certificate pinning and mutual TLS | Shipped and exercised daily on our own fleet |
| Evidence handling | Frame-exact export with time and camera burn-in, produced as a queued job with a recorded outcome | Chain-of-custody policy is the operator's, not ours |
| Detection data | The model runs locally on your hardware; inferences are events on your bus | Automated processing is yours to describe to your regulator |
| Test record | A written pentest ledger, with open findings visible | Published extent still being decided |
What we do not claim
No ONVIF or Profile conformance. No NDAA or TAA compliance. No UL or EN certification. No uptime or service-level figure, because we operate one site and it is our own. And no claim of GDPR compliance on your behalf — we can describe the architecture's privacy properties, and you remain the controller.
Reporting something
A disclosure address, a stated response expectation and a published policy belong here. The address and the timeframe are being set; the slot is deliberately visible rather than quietly absent.
Contact