InnerWeb
Skip to main content

Location data retention period: FAQ

The three-month limit in Article 22(2) § 3 of the Labour Code concerns video surveillance recordings and does not automatically apply to employee location data. That does not mean there are no limits: the retention period must follow from the purpose and from the GDPR storage limitation principle. Below are answers to the questions administrators ask most often before setting retention periods.

3 months
limit for video recordings, not for location data
Source: card
95%
share of one aggregation table in audit size before its exclusion
Source: card
14 days
from announcement of the act to launching location
Source: card

Does the three-month limit from video surveillance apply?

Not automatically, but that does not mean there are no limits. Article 22(3) § 3 of the Labour Code refers to Article 22(2) only for paragraphs 6 to 10, i.e. the internal act, the 14-day term, written information and signage. Paragraph 3, with the three-month limit for recordings, is not on that list, so the statute does not set a single number for location retention.

Instead, the GDPR principle applies: data may be kept no longer than necessary for the purpose (Article 5(1)(e)) and must be limited to what is adequate (point c). The administrator sets the period and must be able to justify it to the data protection officer, the Personal Data Protection Office (UODO) or the National Labour Inspectorate (PIP).

How to set the period for a specific purpose?

The period is set separately for each purpose, not as one value for the whole system. Location used for SOS alarms and motionlessness detection has a different horizon than location history used for settlements or incident analysis. Legal opinions describe the alarm as a separate purpose based on Article 207 § 2 of the Labour Code, so its retention is recorded in a separate paragraph of the internal act.

A practical method has four questions. What is the data needed for? How long after an event can it realistically be used? Is an aggregated version sufficient? Who has access to it after this period, and on what basis?

  • Current purpose (alarm, dispatcher response): data needed at the moment of the event and for a short analysis.
  • Settlement purpose (attendance time, permits): period resulting from other regulations and complaint deadlines.
  • Evidence purpose after an event: keeping records of a specific event for the duration of proceedings.
  • Statistical purpose: aggregated or anonymized data instead of personal data.

Share of tables in audit data size before the change

Share of tables in audit data size before the changeDonut chart: 95% of the audit size was taken by one aggregation table, 5% by other audited tables.Aggregation table of time spent: 95 % (95%)Other audited tables: 5 % (5%)100%Aggregation table of time spent95 % (95%)Other audited tables5 % (5%)
Source: Function documentation for the audit trail: 6,331 MB, which is 95% of all audit tables

What about data recorded only by the system?

Technical data, such as the presence signal of a wearable device or location history, is source data in InnerWeb, not a human action. The audit trail records data that a person may change; records created only by the system are outside it, because their history is itself source data.

Conclusion for retention: two independent periods must be set. The first covers the location data itself, the second covers the log of changes made by people (who changed a permit, a rule or an inspection route). The change log serves as proof of accountability and is usually kept longer than raw location points.

Why should the audit log not grow without control?

Retention also applies to the log. In one analysis, the table aggregating time spent in a location took 6,331 MB, which is 95% of all audit tables, even though it did not document any human action. Excluding it from the audit reduced the size of the log, while the source heartbeat data remained.

A coverage review compared 127 entities with 60 audited ones and added 48 more; the largest added table had 5,825 rows, so the cost is negligible. Lesson: select objects for audit by whether a person changes them, not by their size, and record this in the retention documentation.

How to record the period in documents and inform employees?

The retention period appears in three places: in the internal act (regulations, collective agreement or notice), in the written information given before admission to work, and in the register of processing activities. GDPR Article 13 requires stating the retention period or the criteria for setting it, and Article 30 concerns the register.

The most common mistake is inconsistency: the act states one period, the register another, and the system configuration implements a third. Before launch, check that all three sources match and save the comparison result with a date as evidence. A signed employee statement is not required by statute, but a list of signatures helps in a PIP inspection.

Do employees of external companies have the same period?

There is no reason for them to have a longer one. For them the Labour Code rules on monitoring do not apply; the basis is Article 6(1)(f) GDPR read together with Articles 208 and 304 of the Labour Code, as a separate processing activity. Since the basis is weaker, the period should be no longer than for the company's own staff, and ideally shorter and stated in a separate notice.

Checklist

Video

Frequently asked questions

Is 3 months a safe default value for location data?

It can be a starting point, but it is not a requirement. What matters is the justification that follows from the purpose. For alarms and motionlessness the period may be shorter; for evidence after an event it may be longer for a specific case.

After the period ends, must data be deleted or is anonymization enough?

The storage limitation principle allows both approaches, provided that after anonymization the person cannot be identified. Record the chosen method in the register of processing activities.

Does changing the period require new information for employees?

Yes, if the period is part of the written information. Treat a change to the internal act as a new announcement and keep proof that it was delivered.

How to prove that data has actually been deleted?

Keep the record of the period configuration, the date of the change and the result of the retention review. The audit trail shows who changed the settings and when, for settings that can be changed manually.

Sources

Let's set retention periods together with your legal department

In a demo we will show how retention periods are configured and how the audit trail documents changes. Book a conversation with the InnerWeb team.

Let's talk