Who these recommendations are for and what they rest on
The recommendations are addressed to the controller, the data protection officer and the IT department at a plant that considers tracking employees with wearable devices: an active card or a watch. They rest on two GDPR principles. Article 5(1)(c) requires data to be adequate and limited to the purpose, and point (e) requires that it is kept no longer than necessary.
Article 25 adds the duty of data protection by design and by default, and Article 32 requires technical and organisational measures adequate to the risk. The practical approach follows from this: minimisation is set during configuration, not added after deployment.
The legal opinions describe the variant with an app on a company phone. For wearable devices they apply by analogy, and a wearable device collects less data than a phone, which is its advantage from the minimisation point of view.
Recommendations 1-3: scope of data and identification
The first group of recommendations concerns what enters the system at all.
Recommendation 1: collect position, not a profile of the person
The position is calculated from signals of several transmitters averaged on the map and works without GPS. This is enough to show which zone a person is in. There is no justification for additionally collecting data on activity, heart rate or movement if the purpose of the act does not cover them. Every additional field must be justified by the purpose.
Recommendation 2: limit identification to what the purpose needs
In many uses, for example counting people in a zone for the evacuation list, an identifier is enough, and the first and last name are needed only when an event occurs. It is worth setting the visibility of personal data by role: the dispatcher sees identity, the shift manager sees the number of people in a zone.
Recommendation 3: do not duplicate data from other systems
InnerWeb is an independent system that complements the client's existing systems: access control, time and attendance, HR and ERP. It receives card-badge events from the client's access control system. If data on qualifications or employment is already in HR, do not copy it without need; connect it where the purpose requires it.
Indicative number of transmitters: a hall versus the whole plant
Recommendations 4-5: area scope and retention period
The second group concerns where and for how long.
Recommendation 4: narrow the location area
In a building one transmitter is installed per 100-200 m2, and on plant roads one transmitter roughly every 100 m. The scope of location therefore follows the installation points. Installing transmitters only in zones where the purpose requires it is the technical implementation of the minimisation principle. Toilets, smoking areas and canteens may be covered by location, but this requires an explicit entry in the act and additional marking, so by default it is better to exclude them.
Recommendation 5: set the retention period yourself
The three-month retention limit for recordings in Article 22(2) § 3 does not apply directly to location, because Article 22(3) § 3 refers only to §§ 6-10. The period is set by the controller in line with the minimisation principle. The lack of a statutory limit is not an incentive to keep data long: the period must follow from the purpose and be written in the act and in the information under Article 13 GDPR.
Recommendations 6-7: access and the alarm function
The third group concerns who sees the data and how to separate the alarm purpose.
Recommendation 6: role-based access and a trace of changes
Access to position history makes sense only for roles that need it. Changes to selected data, such as permits or training results, are recorded in an audit trail with the author and the time, and sensitive fields, such as a password or a device token, are excluded from it, so the change log does not store secrets.
Recommendation 7: describe the alarm function as a separate purpose
The SOS alarm and motionlessness detection are described as a separate purpose based on Article 207 § 2 of the Labour Code. Model acts for wearable devices contain a separate paragraph on the alarm function. Separating the purposes makes it possible to limit visibility of position to alarm events, if that is the controller's decision.
How to check that minimisation works
For each of the seven recommendations prepare one piece of evidence: a configuration screenshot, an entry in the act, a retention setting, a list of roles. On that basis the data protection officer can go through all the points within an hour. A missing piece of evidence for any recommendation is a signal that the configuration needs to be clarified before launch.
After the pilot it is worth a review: which data was actually used and which only sits in the database. A field that no process uses is a candidate for switching off.
Checklist
Video
Frequently asked questions
Does an active card collect less data than a phone?
Legal opinions indicate that a wearable device collects less data than a phone. The scope, however, depends on configuration, so minimisation must be set and documented.
How many transmitters does a 5,000 m2 hall need?
At the rule of 1 transmitter per 100-200 m2, this comes to 25 to 50 units. It is an indicative calculation, and the exact design depends on the structure of the hall.
Does the person's name have to appear on the map?
Not always. An identifier is enough to count people in a zone, and identity is revealed to the role that needs it, for example the dispatcher in case of an alarm.
Sources
Let's set minimisation on your map
We will show which data is needed for a specific purpose and how to set visibility by role.
Let's talk