It seems weird that it's being stated that it's the nature of each company that prevents merging from being possible (as in @macuser_22's recent reply [and then in their post before that they point to a FAQ while staying it's a federal privacy concern while the FAQ they're referring to says nothing about it being a federal limitation.])
I say this because someone can create a new account now to have it work as a single sign-on across each. So it's not a hard limit that they can never work together.
If it's a matter of a previous policy being agreed to upon the past accounts being created not allowing for them to work together, why can't there be a new policy shown for the user to then agree to in order to proceed with the merge which then alleviates any issues between the services having different policies that were agreed to in the past (again, with a single sign-on otherwise existing showing it should be doable)?
If it's a matter of making sure the merge process is secure & privacy-centric, why can't there be a verification process that sufficiently confirms access & the identity of both accounts before being able to merge the accounts?
I'm just missing out on what exactly is the real reason this isn't being done (with the reasons being presented so far not really making all that much sense or otherwise not having a way to address the issue to then be able to still offer the merge capability [outside of them just not taking the time to do it being the fallback reason.])
