Privacy Guides should cover the reasoning behind why you should switch from X to Z

I’ve often shared Privacy Guides around to lots of people but found that it is lacking something I believe to be crucial, that being the reasoning behind why people should switch from what they currently use to what PG recommends. For example when looking through the recommended mobile operating systems I can see that PG recommends GrapheneOS and DivestOS, but it doesn’t look like it goes into any detail as to why I should avoid iOS or (default) Android in the first place. I found this to be the case with most (if not all) categories on Privacy Guides.

I’ve had some people come back to me after reading the PG site and not being very convinced as to why they should switch to alternatives when they don’t see what’s wrong with what they already use. Then I’m left trying to collect a bunch of sources and present an argument by myself just for one person to see the issues with what they currently use and why they should consider using a better alternative, but because I’m limited in time, energy, and knowledge I am sometimes not able to make a strong enough case and ultimately they don’t consider making any changes. I think it’s crucial that we share the reasons as to why people should avoid the privacy-invasive software/services most of them are using now in addition to recommending alternatives. I recall back when PG was PTIO, it included examples of what not to use. For example under the desktop operating systems category it mentioned that you should avoid Windows. I think we should bring that back but also include the reasoning (backed by sources) as to why people should avoid X (Windows, macOS, ChromeOS, etc) and switch to Z (QubesOS, GNU/Linux).

I’m sure the PG team already knows all about the privacy concerns with much of the mainstream software/services used, but if it helps there are a few resources which cover some of these concerns including GNU’s “Proprietary Software” section, Stallman’s “What’s bad about:” section, Whonix documentation, Mozilla’s *Privacy not included, ToS;DR, and PrivacySpy.


This discussion is usually in our discussion forum, or on Github.

We don’t litter the site with every anti-recommendation, otherwise the whole site would become just that, and it would be painful to maintain as there are a lot of things, the team purposely does not use.

The reason this was removed, is because it was not entirely accurate. That being said we are still looking at re-introducing a Windows section Windows guide by IkelAtomig · Pull Request #1659 · privacyguides/ · GitHub though it does require some significant work before it will be ready.


I somewhat agree with @Cartridge2508. Ultimately, this comes down to PG’s target audience, which is still unclear.

I’ve also noticed that PG is highly dynamic; A Lot of stuff changes for a site that intend to be read only once or twice.

We are actually going to be writing a blog post about this change soon.

Essentially, evergreen content such as the Knowledge Base and Recommendations will remain on the site, while content that is likely to “age” and lose relevance will be on the blog. Of course, that doesn’t mean blog articles can’t be updated.

We do within the knowledge base link to specific blog articles, and those can be sorted by category.

1 Like

Thank you for your clarification.
How do you address changes in recommendations (like with brave in past)? Specially without any guide on how to choose right tool in world where we have so many tools focused on privacy.

I’ve had some people come back to me after reading the PG site and not being very convinced as to why they should switch to alternatives when they don’t see what’s wrong with what they already use.

It is no surprise that the average person have no interest in PG. Again, what is the target audience about? Is it for the average person? Technically proficient person?

You can keep up to date by checking our releases page Releases · privacyguides/ · GitHub this links to specific discussions about things.

That’s certainly not true at all.

A mixture, as those who are technically proficient, don’t often know about privacy, likewise those who are not technically proficient may need extra help to get up to speed.

The site does not target any specific segment. The intention of the site is to be a filter of all the “privacy noise” that is out there, and provide meaningful things one can do. Just because it’s on the website doesn’t mean you must take all our advice.

We don’t jump on every shiny new bit of software released like some other privacy websites do because essentially everything needs to have time to build a reputation.

1 Like

Yes. However, I’m asking in the perspective of an end user. For example, PG was recommending Bromite and then removed it. A risk may exist for someone who visited and installed Bromite because PG suggested it. This neither the person fault, as PG is intended to be a static site and aren’t expected to visit the site every day to check for changes.

I think this should be stated clearly in the site as disclaimer. The fact that recommendations are the most visited page make this a big issue. This is also sending the wrong message that such tools are needed in order to be private (which is wrong, as Privacy isn’t about the tools you use or the software you download) specially when it recommends as a beginner to privacy resource in most places.