How identifi.cam handles data
A two-page document for a client’s data protection officer. It explains what the system does with images, what leaves the device, and which formalities still apply.
Last updated: August 2026
The principle
Edge processing here is not an architectural preference: it is the decision that makes installing a camera in public space viable. The frame is read, processed and discarded inside the device itself. What goes out onto the network is a number or a state.
Mapping to the GDPR
| Principle | How the product meets it |
|---|---|
| Minimisation (art. 5) | Only a number or a state leaves the device. The image does not travel. |
| Privacy by design (art. 25) | The personal datum never comes into existence outside the node. |
| Storage limitation | Frames are processed and discarded; there is no continuous recording. |
| Proportionality | The camera does not identify people: it counts objects. |
Concrete product measures
- The node stores no video. Frame, inference, discard.
- An alarm snapshot is sent only when there are no people in the scene. Abandoned waste is static and in no hurry: the system waits for the first clean frame.
- Face and plate blurring is available as an option wherever a snapshot is unavoidable.
- The data model of each installation is documented and handed to the client’s data protection officer as an annex.
What has to be said plainly
This cuts the red tape substantially; it does not remove it. In public space you will still need informational signage, a pass by the data protection officer and probably an impact assessment.
But arriving at that conversation with “the images never leave the device” turns it into a formality rather than a fight.