Privacy Tools Criteria
These are the requirements we weigh before a privacy tool or service earns a spot on PrivacyTools.io. No single box is mandatory on its own, but the more a tool ticks off, the stronger the case for listing it.
Core requirements
The first things we check for every entry.
Open-source
We love the open-source community. Software and services recommended on PrivacyTools.io are open-source unless marked Closed-Source. Since almost all of our entries are open-source, we don't point it out every single time. In some cases developers release the client source code but not the server or backend code; those entries carry the Partially Open-Source tag.
Usability
Is the app or service user-friendly and easy to use? A modern, well-designed interface makes a tool easy to understand and therefore widely adopted. We generally don't recommend command-line (CLI) tools, but there can be exceptions when no alternative exists. Entries that need a complicated setup are tagged For Experts.
Active development
Were there any recent updates? A tool still under active development is far preferred over an outdated project. Exceptions: no alternative is available, or the tool is in a stable state with no known issues that could pose a security threat or leak data that harms your privacy.
Cross-platform
Tools available across several devices and operating systems are preferred. It makes life easier for the end user, and it helps convince people to switch to a privacy-respecting alternative.
Publicly available
Invite-only services, providers and tools are not listed. To convince users to switch to privacy-respecting alternatives, getting started should be as easy and fast as possible.
Jurisdiction
Where a provider is based, and the laws it's bound by, can shape how it handles data requests and gag orders. We treat jurisdiction as one factor, not a pass/fail test, and weigh minimal data collection more heavily than any address. We may exclude services case by case over censorship concerns.
What else we weigh
Softer factors that strengthen, but don't make or break, a listing.
Security audits
Ideally the tool received an independent security audit from a reputable cybersecurity firm. This is optional, since open-source developers often can't afford the cost. Audited entries carry an Audited tag. Remark: an audit is not 100% proof that software is safe. Flaws can be missed even by the best auditors, and an audit is valid only for a snapshot of the code: new code can introduce new vulnerabilities.
Business model
Lately, everything became a paid subscription. To counter that, we look for tools you can use for free or that offer a freemium tier. We also prefer paid services with a fair money-back guarantee and a free trial.
Test of time
Time reveals whether a privacy tool can last. Where relevant, we note when a company was founded and whether any significant incidents happened since. Court cases show whether a company kept its promises. Time also shows whether a tool reached widespread adoption and a broad user base.
Sponsorships
Sponsors can be exempted from the criteria, though our sponsors generally share the same ideology and meet most of them anyway. A sponsorship never buys a free pass on the things that matter for your privacy.