Audit the data path, not only the notice
Audit the data path, not only the notice
Audit the data path, not only the notice
Take the chapter’s room-occupancy example and trace one raw window through acquisition, feature extraction, local decision, diagnostic logging, export, backup, and deletion. At each handoff, record who can read the data, how it is linked to a person, and when the copy disappears. A short retention label is unproven if a debug log or backup still holds raw phase or a tracked path. Test deletion by inspecting those actual stores, including the failure path when the device loses its connection.
Then compare the intended purpose with the inferences the same measurements could support. A count for lighting can become an attendance history when joined with timestamps and a room roster. Remove unneeded detail before storage, keep uncertainty and abstentions in the operational output, and give operators a route for correction. The chapter’s ICO minimisation and worker-monitoring guidance supports the purpose and proportionality review; the cited GDPR text frames the EU legal assessment. The downloadable checklist is a design record for that review, not a substitute for it.