Custom software for retention periods and purging personnel files
A personnel file is not a folder with a single expiry date. Application data goes within weeks, data without a statutory retention period after two years, the copy of the ID document after five years, and parts of the payroll records only after seven. Four retention periods in one file, and a single delete button won't separate them.
Which retention periods sit in one file
Application data is generally deleted no later than four weeks after the end of the procedure. If you want to keep it longer, for example for a future vacancy, you need the applicant's consent.
For data in the personnel file that has no statutory retention period, the rule is: keep it for up to two years after the employee leaves. If the data is no longer needed sooner, you delete it straight away; the period is a maximum, not a target.
The file also contains data with its own statutory period. You keep wage tax declarations and a copy of the ID document for five years after the employment ends. Parts of the payroll records must be kept for seven years after the employee leaves.
And there is an exception that holds everything up: if there is an employment dispute with the employee or legal proceedings are under way, you may keep data for longer. That means a purge run cannot work blindly; it needs to know which files are on hold and why.
How we build this
The key is the type of data, not the file. As long as everything sits in one folder, the only possible action is to delete the whole file or keep the whole file, and both are wrong.
Record what each item is: application, terms of employment, absence, ID document, payroll records.
With the legal basis alongside, so it can be explained later why something was kept for that long.
End of the procedure, end of employment or something else. The starting point determines the deletion date.
What was deleted, when and on what grounds. That is what you show when someone asks whether you really did it.
What the software actually does
Organising by data type carries the whole approach. What else you need depends on your size and on how many systems hold personnel data.
Retention period per data type
Four weeks, two years, five years or seven years, with the legal basis next to each type.
Starting point per file
The clock starts at the end of the procedure or at the end of employment, and that moment is recorded.
Hold in case of a dispute
If a dispute or proceedings are under way, the file is excluded from purging until it is resolved.
Purge proposal in advance
What is due next month, so someone can check before anything disappears.
Proof of deletion
Which type of data was deleted from which file and when, without keeping the deleted data itself.
Across systems
Personnel data is rarely in one place. The schedule also applies to the surrounding systems.
Who we build for
Who works with this differs per organisation. Four situations.
HR departments
They manage the files and are the ones who do the purging, usually on top of all their other work.
Data protection officers
They are asked whether the retention policy is actually carried out, which is not the same as whether it exists.
Payroll administrators
They deal with the longest retention periods and with data that cannot simply be deleted.
Organisations with many temporary staff
High turnover means many files that quietly pass their retention period.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
Retention periods can change and new categories of data get added. Categories, periods and starting points should be configurable rather than hard-coded.
For employers who want to manage and comply with retention periods for personnel files, there is our software for personnel file retention periods.
If you carry out DPIAs regularly and want the pre-scan, risks and DPO advice in a single workflow, there is our DPIA workflow tool.
If you want to track per supplier which personal data is processed and under which agreements, there is our contract register for data processing agreements.
Why Appfront
One file, four retention periods
A delete button at file level is always wrong: too early for payroll or too late for everything else.
The retention period is an upper limit
If data is no longer needed earlier, you delete it straight away. We build that as a rule, not as an option.
A dispute stops the clock
In the event of a dispute or legal proceedings, you may retain data for longer. A clean-up run that does not know this will delete exactly the wrong thing.
Policy is not execution
The question in an audit is not whether you have written down retention periods, but whether they are being followed.
Security and privacy
By definition, this system deals with employees' personal data, and sometimes with special categories such as health data related to absence. That data shouldn't be visible to the same people as the rest of the file. We set up access per role and per data type, separate absence from HR, and log every access, including by administrators. Integrations run through secure connections to your existing software.
For this subject, what matters is being able to trust the record of what happened at the time. In the event of a complaint, what counts is whether you acted in line with your own policy at that moment. We record clean-up runs immutably with timestamp and person, without keeping the deleted content, and turn a correction into a visible correction alongside the original entry. How we handle security ourselves is set out in our information security policy.
Frequently asked questions about retention periods for personnel data
Generally no longer than four weeks after the application procedure ends. If you want to keep the data longer for a future vacancy, you need the applicant's own consent.
For data without a statutory retention period, the rule of thumb is up to two years after the employee leaves. If the data is no longer needed sooner, you delete it straight away; the period is an upper limit, not a target.
Wage tax statements and a copy of the ID document are kept for five years after the employment ends. Parts of the payroll records must be kept for seven years after the employee leaves.
Yes. If there is an employment dispute with the employee or legal proceedings, you may keep the data for longer. In practice, this means your clean-up process must know which files have been excluded for that reason.
By recording which type of data was deleted from which file and when, without keeping the deleted content itself. That last part is the pitfall: a log that quotes the deleted data undoes the deletion.
No. This is specifically about retention periods and deletion. Monitoring contracts, certificates, leave and working hours is a different subject; for that we have a page on HR compliance software.
Are there still files for people who left three years ago?
Search your system for employees who left more than two years ago and see what is still held on them. If you find more than the payroll records and the legally required documents, your policy is not cleaning up after itself. We build this as a standalone application and as part of a broader custom software development project.