Home/Process library/Personal data that cleans itself up
Process library · HRPersonal data that cleans itself up
When a contract ends, the personal data of the former employee does not stay forever. It is cleared and deleted in stages, per type of data, with a short window in which HR can still step in.
See the flow Map your own flow
In short
In this blueprint the personal data of an employee is kept in separate records by sensitivity: identity and bank data, family and fiscal data, address, emergency contact and facility data. When the contract ends, every record moves to waiting. During two weeks, HR can still move a record back, for example for a re-hire. After that, birth data, nationality, address fields and family and fiscal data are cleared, and emergency contacts and facility data are deleted. A year later, the national number, bank details and private e-mail are cleared and the address record is deleted. Each type of data has its own retention rule. SoftAdvice designed and documented the process.
Keeping personal data is easy. Letting go of it is not.
An employee left two years ago. Their national number and bank account are still in the file.
An HR file holds the most sensitive data an organisation has: national number, bank account, family situation, disability, emergency contacts. Privacy law asks you not to keep it longer than needed.
In practice, nobody deletes anything by hand. Former employees stay in the file for years, with every detail still there.
- Personal data split by sensitivity
- A retention rule per type of data
- A window for HR to step in
- Clean-up recorded in the history
What happens from the end date to a year later
Not everything goes at once. What is no longer needed goes first; what may still be asked for goes later.
On the end date
Waiting
Every linked record of the former employee moves to waiting.
During two weeks
A window to step in
HR can move a record back, for example when the person is re-hired.
After two weeks
First clean-up
Birth data, nationality, address fields and family and fiscal data are cleared; emergency contacts and facility data are deleted.
A year later
Final clean-up
National number, bank details and private e-mail are cleared, and the address record is deleted.
From end of contract to clean file, step by step
One step needs a person, and only when there is an exception. The rest follows the retention rules and is recorded in the history.
Start the clock
When the employee is contractually out of service, every linked record of personal data moves to waiting.
Step in if needed
During the waiting period HR can move a record back to active, for example for a re-hire. Otherwise, nobody has to do anything.
First clean-up
After two weeks, birth data, nationality, address fields and family and fiscal data are cleared. Emergency contacts and facility data are deleted.
Final clean-up
A year later, the national number, bank details and private e-mail are cleared and the address record is deleted.
One rule per type of data
Each kind of personal data has its own record and its own retention rule, so nothing is kept longer than its purpose.
Identity and bank data
Family and fiscal data
Address
Emergency contact and facility data
From good intentions to a rule that runs
Nobody has to remember to delete anything. The retention policy is in the workflow, and the history shows that it ran.
Before
- Former employees kept for years
- All personal data in one file
- Deleting depends on someone remembering
- No proof of what was deleted
Now
- Clean-up starts on the end date
- A rule per type of data
- A window for exceptions
- Every step recorded
M-Files with the Compliance Kit
Standard building blocks, configured and documented by SoftAdvice.
Personal data as separate records
Identity, family, address and emergency data each live in their own record, linked to the employee.
Retention in the workflow
Timed steps clear fields or delete the record, per type of data, without anyone pressing a button.
Records that follow the employee
The Compliance Kit starts the clean-up of every linked record when the employee leaves, and stops it on a re-hire.
Questions about this blueprint
Does this make us GDPR compliant?
It helps you apply your own retention policy consistently and shows that it ran. Which data you keep, and for how long, stays your decision, ideally with legal advice. Compliance stays the responsibility of your organisation.
Can we choose other periods?
Yes. Every type of data has its own timed step, so each period can be set separately.
What about the employment contract itself?
The contract follows its own route and is kept as a document. This blueprint is about the personal data around the employee.
How long do you keep the data of former employees?
In Discovery we map your HR data and your retention rules, and show how M-Files can apply them by itself.
