Sensor data is personal data when it relates to a person who can be identified, directly or indirectly, with means reasonably likely to be used. A tank level or motor current in a plant is not. A badge reading, a worn tracker’s position, an assigned-desk sensor or a camera image of people usually is, under both GDPR and KVKK.
Both laws ask about the person behind any data, readings included, not only names and e-mail addresses. This post explains the test as the texts stood in June 2026; it is not legal advice.
When does IoT data become personal data under GDPR?
IoT data becomes personal data when it can be linked to an identified or identifiable natural person. Article 4(1) of the GDPR names identifiers such as an identification number and location data, and Recital 26 says to count all the means reasonably likely to be used, such as singling out, by the controller or by another person.
Recital 26 also keeps pseudonymised data that could be re-attributed in scope, and leaves only anonymous information outside. I ask whether someone here, with the data and the lookup tables we keep, could say which person a reading is about.
| Signal | Usually personal data? | Why |
|---|---|---|
| Tank level, pump current, room temperature | No | It describes a machine or a space |
| Access badge event | Yes | The badge number is an identification number issued to one person |
| Worn tracker, vehicle assigned to a driver | Yes | Location data linked to a person |
| Camera image | Yes, when people can be identified | Looks and other details identify them |
For cameras, the EDPB guidelines on video devices say the GDPR does not apply where an individual cannot be identified, directly or indirectly.
Is occupancy data personal data?
A people count for a large open floor usually is not personal data; presence at an assigned desk or in a single-person office usually is, because it shows when a known person arrives, leaves and steps away. The sensor can be identical; only the second reading singles someone out.
I would keep occupancy coarse, counts per zone rather than per desk, because any seating plan the organisation keeps turns a desk reading back into a person. Tags in BLE indoor asset tracking work the same way: on a pallet a tag is machine data, on a lanyard it is location data about a person.
Does KVKK apply to sensor data?
Yes, when a reading relates to an identifiable person. The Personal Data Protection Law No. 6698 (KVKK) defines personal data, like the GDPR, as any information relating to an identified or identifiable natural person, and anonymisation as rendering data impossible to link with such a person, even through matching it with other data.
A badge log with names replaced by badge numbers fails that bar if the HR system can match the numbers back. Requests from people run on a clock: KVKK Article 13 sets thirty days at the latest, and GDPR Article 12(3) one month, extendable by two further months.
Hermetry connects field devices to live dashboards, rules and alerts: IoT telemetry and SCADA in one platform. Its privacy requests and data erasure tools give an organisation a request queue, a dossier of everything the platform holds about one person, and an erasure that runs across every module, with a setting that makes a second person approve each erasure. The docs treat telemetry as machine data and state that erasure does not search it, so for trackers worn by people they advise keeping personal names out of device names and the tracker-to-person mapping outside device data.
Decide who may see personal readings with the same roles as in least privilege in OT. For a site that tracks people as well as assets, see yard tracking of trailers, vehicles and people.
Frequently asked questions
Does hashing a badge number make the data anonymous?
Usually not. A hashed badge number is at best pseudonymised in the sense of GDPR Article 4(5), and Recital 26 treats pseudonymised data as information on an identifiable person. In EDPS v SRB (2025) the EU Court of Justice added that such data may not be personal for a recipient with no reasonable means to re-identify anyone. If your organisation can recompute the hash from its badge list, the readings remain personal data.
How long may personal sensor data be kept?
Neither law sets a fixed number. GDPR Article 5(1)(e) allows identifiable data for no longer than necessary for its purposes, and KVKK Article 4 allows storage for the period set by legislation or required by the purpose. KVKK Article 7 requires erasure, destruction or anonymisation once the reasons for processing no longer exist.
Is a live camera view personal data processing if nothing is recorded?
Yes, if people in it are identifiable. The GDPR’s definition of processing in Article 4(2) covers any operation on personal data, and its list includes collection, consultation, use and disclosure by transmission as well as recording and storage. A live view of identifiable people needs the same thought about purpose, who may watch and how people are informed.

