As I searched through approximately 30,000 words of terms of use and other policy documents to find answers for this post,

I discovered the issue(s) with privacy policies; however, privacy policies typically are not written with full transparency in mind.
According to Bennett Cyphers, a staff technologist with the Electronic Frontier Foundation, "all a privacy policy can really do is tell you with some confidence that something bad is not going to happen," but "it won't tell you if something bad is going to happen."
Cyphers went on to say, "Frequently, what you'll see is language that says, "we collect X, Y, and Z data, and we may share it with our business partners, and we may share it for any of these seven different reasons," all of which are very vague."That doesn't necessarily imply that the business is doing the worst thing you could possibly imagine, but it does indicate that they have some leeway in case they decide to misuse your data.
He is correct:The majority of the privacy policies I looked at for this post had a lot of the "wiggle cover" cyphers, which are vague, broad language with few actual details.Worse still, a lot of these policies cover the entire company, including all of its products, services, and websites, as well as how it handles data from sales transactions and even applications for jobs.As a result, a lot of what is written might not even apply to routers.