They are also not even remotely as extensive as privacy policies are. Case in point: Back in 2012 one already needed 76 workdays to read all the privacy policies accepted on the Internet in one year [0].

Since then that number has very likely gone extensively up as people use even more online-services on average, particularly on mobile devices, and a lot of these services now also have extensive codes of conduct in addition to the privacy policies and bloated ToS/EULAs.

So while reading the ingredients of everything you eat is a very realistic and plausible thing to do, something people with allergies do on a near-daily basis, trying the same with privacy policies is just not realistic. Particularly when one wants to read them in an informed way to actually understand what you are agreeing to [1], for that you would need a lawyer to read them with you to make sense of the convoluted legal-speak they are usually written in.

A fact that is pretty common knowledge to such a degree that companies have even written $10k rewards into their ToS for people actually reading them. [2]

That's why most privacy policies do not really exist to inform the users as food labeling does, their main purpose is for the company to cover their ass legally while doing all kinds of shady things with users' data.

[0] https://techland.time.com/2012/03/06/youd-need-76-work-days-...

[1] https://www.cracked.com/article_19683_6-terrifying-user-agre...

[2] https://www.npr.org/2019/03/08/701417140/when-not-reading-th...