The system captures no personal data in the first place: no images, no biometric data, no MAC address. What a city receives is counts, flows, and dwell times, which contain no identifiers. That is a different starting point from camera analytics, where personal data is captured and must then be protected.

The Act's high-risk Annex III categories address biometric identification and categorisation. Ariadne performs neither: nothing biometric is captured at the sensor and no demographic attributes are detected. The architecture sits structurally outside those categories, which simplifies the procurement review.

Yes. Because the outputs are aggregate counts and flows with no personal data in them, they can go into open-data portals, council reports, or shared dashboards with district partners without a redaction step.

Pedestrian traffic on streets and squares, dwell in parks and plazas, event attendance, and how flows shift with weather or season. Towns like Waldkirchen and Bad Nauheim use Ariadne for exactly this kind of measurement.

CCTV analytics starts from video, so it creates personal data that then needs safeguards, retention rules, and impact assessments. Ariadne starts from depth geometry and phone signals with no identifiers attached, so the sensitive data never exists at any point in the pipeline.

Yes. Signal sensing measures movement across open spaces where a door-based counter has nothing to attach to, and Time-of-Flight depth sensing covers defined choke points such as station entrances or bridges. Deployments combine both as the space requires.