Huh? If that was the case, it would go a bit too far, as it would make technologies like e-mail or git illegal to use internally, considering those are likely to have a real name of a person who sent an e-mail/committed.
Git history can be modified, as can email headers, but yeah - the law is more about e.g. disciplinary records, stuff stored on your section of the company file server, and other things which the company really has no legitimate use for once you’ve left.
In practice, the best solution to this is for companies to check over their data retention policies and making sure they’re not holding on to data for longer than they need to - which may involve creating processes to take information out of emails and put it somewhere more structured/permanent - rather than being blindsided with a request without the infrastructure to handle it. The best response, after all, is “we deleted/modified that data so as to comply with your request already”, rather than “we’ll be back to you once we’ve read through your 50,000 emails and decided which ones we need to keep”.
In practice, the best solution to this is for companies to check over their data retention policies and making sure they’re not holding on to data for longer than they need to - which may involve creating processes to take information out of emails and put it somewhere more structured/permanent - rather than being blindsided with a request without the infrastructure to handle it. The best response, after all, is “we deleted/modified that data so as to comply with your request already”, rather than “we’ll be back to you once we’ve read through your 50,000 emails and decided which ones we need to keep”.