Every time one of <i>millions</i> of developers commits code to a centralized service, they have a hand in exposing individual&#x27;s data to the surveillance society we live in today. Data exposure can come from being publicly available on the site itself, being obfuscated through aggregation in the service&#x27;s APIs, leaked through security holes in implementation of said services, risk of theft by hackers looking for high value targets with private data, or misappropriated by the company itself or its upstream providers. The idea that customers can somehow understand the scope of their exposure to privacy violations is laughable.<p>One thing which became apparent to me when I began to focus on this issue was the fact there are countless other services which provide services to other services, all of which have some degree of access to upstream customer data. For example, if you log to a hosted logging service, some of your customer&#x27;s data is sent to them. If <i>that</i> service use AWS, then data is sent to Amazon. And so on.<p><a href="http:&#x2F;&#x2F;www.stackgeek.com&#x2F;blog&#x2F;kordless&#x2F;post&#x2F;a-code-of-trust" rel="nofollow">http:&#x2F;&#x2F;www.stackgeek.com&#x2F;blog&#x2F;kordless&#x2F;post&#x2F;a-code-of-trust</a><p>Arguing efforts to make things better is pointless is a very dangerous thing to do, assuming we actually want things to be better. Cognitive dissonance is a powerful force, especially when there are startups to be built!