Transparency
Questions, answered directly.
How the project works, what the recommendations mean, and what you should expect when using the site.
What exactly is PrivacyStack?
PrivacyStack is an independent, opinionated guide for regular users who want practical alternatives to mainstream digital services. It focuses on a small number of approachable options instead of trying to catalog everything.
Is this a list of the “best” privacy apps?
No. There is no universal best choice. Requirements, threat models, budgets, and tolerance for inconvenience differ. These recommendations aim to cover the common needs of non-technical users while explaining important tradeoffs.
How are recommendations selected?
Selections consider privacy design, public documentation, source availability, security history, active maintenance, platform support, usability, and community experience. Open source is strongly preferred but is not the only criterion.
Does PrivacyStack track visitors?
No. The initial site contains no analytics, advertising scripts, tracking pixels, or application cookies. It is built as static HTML and CSS. The hosting provider may still process short-lived technical logs needed to serve the site.
Are any links sponsored or affiliated?
No. PrivacyStack does not use affiliate links or paid placement. Product links lead directly to official websites or source repositories.
How current is the information?
Every recommendation records a review date. Products and policies change, so the catalog should be treated as maintained guidance rather than a permanent certification.
Can I suggest a tool or correction?
Yes. Open an issue or pull request in the PrivacyStack GitHub repository with official sources and a clear explanation of the proposed change.
Why is a popular tool missing?
The catalog intentionally stays short. A missing tool may overlap with an existing choice, demand more technical knowledge, lack sufficient evidence, or simply not have been reviewed yet.