I doubt it. I've never heard first-hand of anyone running into any trouble that this would mitigate. Some people are just crazy overzealously fearful of employers and BigCos.
And it's not about being fearful. It's about realizing that the relationship between you and your employer is often adversarial. They want to pay you as little as they can get away with for the most work possible. You want the exact opposite. Otherwise why would you have to "negotiate" for a higher salary when you were hired?
There is another perspective: many companies don't want their employees to use company resources for personal use. They don't want that email from their domain name to be misconstrued as official business, to be entangled in their employees' legally or morally questionable actions, or simply to foot the bill for the resources used. It is a bit odd that a business would ask their employees to merge personal and professional accounts.
It's also worth noting that using personal accounts for professional purposes can confuse things. Personally, I forward any email that my supervisors inadvertently send to my personal account to my work account so that everything is archived and is in one place. Given the amount of filtering of some services (e.g. email) correspondence sent between internal accounts also tends to be more reliable. I have seen situations where dozens of employees did not receive a vital message since it was either sent to a spam folder, or simply dropped, since almost everyone found their personal email provider more convenient.
I've personally started working for a company that demanded any code that I write during employment for company is owned by them regardless if I write it during working hours or at home. I had to list out each project that I had worked on or continuing to work on to establish a history of before/after start of employment. Any new personal project had to be added to the list after a discussion to see how that project and continued employment could co-exist.
The concept here is that if you learned something new at work and then implement it into your own private projects, the company wants that project since they paid for your time learning new something. Also, NDAs and other forms of copyright and what not gets weird.
To me, the gold standard of how to do this is how Woz handled the creation of the first Apple computer. He took it to his employeer multiple times being told they did not claim any ownsership on each occassion.
> The concept here is that if you learned something new at work and then implement it into your own private projects, the company wants that project since they paid for your time learning new something.
This is not how the law works if you’re in California at least. They’ll still get you for other things if you work at a large company, but not for that.
You also wouldn't hear about the trouble someone didn't avoid if the subsequent legal settlement included a gag clause as well as seizing control of the affected IP and a large financial element.
Never accept terms that give your employer control over anything you do independent of work that doesn't affect your performance at work. There is nothing in it for you and the only reason it would be of value to them is if they intend to abuse it.