Re:GDPR – A Practical Guide for Developers (2017)
by nokcha on Saturday March 03, 2018 @01:51PM
(#16510844)
What if the purpose of the archiving is to not only record what was changed but also who changed it?
Re:GDPR – A Practical Guide for Developers (2017)
by marten-de-vries on Saturday March 03, 2018 @03:15PM
(#16511322)
From the GDPR, recital 45:
> [...] where processing is necessary for the performance of a task carried out in the public interest [...] the processing should have a basis in Union or Member State law.
I don't think that purpose of archiving has a basis in law.
That said, I do remember my law professor calling the 'right to be forgotten' one of the weaker parts of the GDPR, and I'm not an expert, so it's possible I'm missing something.
Re:GDPR – A Practical Guide for Developers (2017)
by Neuron4ger on Saturday March 03, 2018 @12:47PM
(#16510469)
Thank you for emphasizing that last part. I think you might be right.
> [...]
> (d) for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes in accordance with Article 89(1) in so far as the right referred to in paragraph 1 is likely to render impossible or seriously impair the achievement of the objectives of that processing;
(emphasis mine)
I'd not say redacting a git repository does 'seriously impair' processing for archiving purposes. All the data (with the exception of the redacted e-mail) is still there, after all.
Still, the hashes will have changed, making the repo less useful for current users. But that has nothing to do with archival.