InnerWeb
Skip to main content

Access control and time attendance data and GDPR: implementation notes for the integrator

One card reader event is a single event, but it can feed several processes: working time records, work permits and the evacuation list. Each of them has a different purpose under GDPR. Below are notes for the integrator on how to split the purposes, limit the fields and record this in the documentation.

3
purposes to split for one card event
Source: example calculation
4
minimum event fields: identifier, point, direction, time
Source: example calculation

One event, several purposes

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 and does not manufacture readers. For the integrator this means two things: the access control system remains the data source, and InnerWeb is the recipient that uses the event for its own processes.

From the GDPR perspective what matters is not that the event is one, but that there are several purposes. Article 5(1)(c) requires data to be adequate and limited to the purpose. If the event feeds working time records, work permits and the evacuation list, each of these purposes must be justified separately and entered separately in the register of processing activities under Article 30.

Three purposes and their limits

The division below is a proposal for the integrator. The final purposes and legal bases are set by the controller with the data protection officer.

Purpose 1: working time records

Working time records from QR gate scans produce daily, monthly and yearly views, exception queues, period closing and timesheets in PDF. This is an HR process with its own permissions and its own retention period. Access belongs to the people responsible for working time, not to the whole security team.

Purpose 2: permits and qualifications

For a work permit it matters whether a person is present in the zone and whether their qualifications are valid. The fact of entry is enough, not the full history of movements. For this purpose it is worth limiting the event fields to the identifier, the passage point and the time.

Purpose 3: evacuation list

The same scans serve the evacuation list. This is a safety purpose, but for employee location the alarm and evacuation purpose is described separately, on the basis of Article 207 § 2 of the Labour Code, not as 'security' under Article 22(2) § 1, which concerns video monitoring. The evacuation list requires access at the time of an event, and there is no need to review it every day.

Number of event fields: full package and minimum package

Number of event fields: full package and minimum packageBefore and after chart: full package 12 event fields, minimum package 4 event fields.02.557.51012.5fieldsFull package from the access control system (example): Fields in the event: 12 fields12 fieldsFull package from the access control system(example)Minimum package: Fields in the event: 4 fields4 fieldsMinimum package
Source: Example calculation: an assumption of 12 fields in a full export and 4 fields in the minimum package (identifier, point, direction, time), to be replaced by the number from a specific access control system

Specification for the access control vendor: what to report and what not

The integration works on the event side: the client's access control system sends the events to InnerWeb, for example by webhook. For the data protection by design principle in Article 25 GDPR, it is worth listing in the specification for the access control vendor only the fields that the purposes need. Typically these are the identifier of the person or card, the identifier of the passage point, the direction and the time.

Do not send fields that no purpose uses: photographs, biometric data, descriptive fields from the access control system. A field that is not sent does not require security, retention or an entry in the register.

  • Card or person identifier, passage point, direction, time of the event.
  • No biometric or photographic fields, unless the purposes require them.
  • Rejected and erroneous events recorded separately, with a shorter retention period.
  • Fixed format and authentication of the channel, because Article 32 requires measures adequate to the risk.

Access, retention and evidence

The split of purposes must be reflected in permissions. HR sees the time records, people issuing permits see presence in the zone, and the dispatcher sees the evacuation list during an event. Roles are set by purpose, and changes to permissions and permits are recorded in an audit trail with the author and the time.

The retention period is set for each purpose separately. Article 5(1)(e) GDPR requires that data is not kept longer than necessary. For events feeding working time the period follows from HR needs, and for the evacuation list a shorter technical period is sufficient. The values are entered by the controller, not by the software vendor.

Integration traps and a checklist for the integrator

Three traps recur in access control integrations. The first is sending the full set of fields from the access control system 'just in case'. The second is using the data for a purpose that is not in the register, for example analysing time spent in a place. The third is not informing employees that the card events also feed other processes.

The information under Article 13 GDPR must name all purposes. If the events feed working time records, permits and the evacuation list, the employee should read about it in one place, together with the retention periods and rights.

Video

Frequently asked questions

Does InnerWeb replace the access control system?

No. InnerWeb is an independent system that complements the client's systems and receives the events from the client's access control system. It does not manufacture or replace readers.

Can one card event feed working time records and the evacuation list?

Yes, if both purposes are described in the register and in the information for employees, and access and retention are set separately for each purpose.

Which event fields should be sent?

Only those the purposes need: identifier, passage point, direction and time. Send biometric data and photographs only when a purpose justifies it.

Do the same scans create working time records?

Yes. Working time records from QR gate scans produce daily, monthly and yearly views and timesheets in PDF, and the same scans feed the evacuation list.

Sources

Let's build the event specification for your access control system

Together with your integrator we will prepare the minimum set of card event fields and the split of purposes for the register of processing activities.

Let's talk