Handling the apparent paradox of permanent records in Agile PLM with the new GDPR

Hi all,
I’m hearing a lot of talk on the new European General Data Protection Regulation and how it requires companies to not store personal data after a certain period for people no longer employed at the company.
Any of you good folks run into this?

Without having received any specifications I can hear from legal department that retaining full name and title could be an issue. This is of course part of the useraccounts in Agile, and is part of the permanent Audit trail of the user in the system: creations and approvals throughout their time. There are other regulations that require us to keep those records.

Any insights and experiences would be most welcome!

Best regards

No Files Were Attached
runemeijer Agile User Asked on October 9, 2017 in IT and Networking.
Add Comment
2 Answer(s)
Best answer

Well, names (usernames, that is) and oftentimes job titles aren’t considered PII, unless the EGDPR as you mentioned is considering it personal data.  If compliance is that strict, do an import to update or nullify those selected data fields for inactive users.  You could also develop a script to do just that for future user inactivations.  
Username is not PII, so there shouldn’t be an issue with keeping that as is in your system.  If you have to update the other fields, you can do so – Agile will need something in the First Name and Last Name fields, though it doesn’t have to be a person’s full name.

Matt Paulhus Agile Professional Answered on October 10, 2017.
Add Comment

Check in preference setting of Agile, it  has two options  whether records to be displayed with User id,  default user name.

Paritosh Deshmukh Agile Angel Answered on October 13, 2017.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.