Editorial method
Selection criteria.
A place in this directory is not an endorsement. It means a tool has a clear privacy use case, makes claims we can verify and gives people enough information to judge its trade-offs.
What qualifies
We consider tools that meaningfully reduce data exposure, protect communication content, limit tracking or help people separate their identity from an activity.
- The privacy benefit must be central to the product, not a marketing add-on.
- The project must have an official site, maintained releases and public documentation.
- Its purpose and limits must be explainable without implying that encryption, privacy and anonymity are the same thing.
What we check
Every profile starts with the project’s primary documentation: technical explanations, support articles, privacy policies, source repositories and audit reports where available.
We check what data is protected, where encryption begins and ends, which platforms are supported, what an account requires and which common failure cases users should know. Each profile links to its sources and carries a real review date.
What we avoid
We do not rank tools by affiliate payouts, accept paid placement or present one product as a universal solution. KeepMeDark has no affiliate links. A polished privacy claim without enough evidence is not sufficient for inclusion.
Review cycle
Profiles are reviewed when material facts change and periodically as the catalog grows. The date on a page describes the last effective check of its claims, not a cosmetic edit.
Older review dates are a signal to verify the official sources before making a high-risk decision.
Corrections
Found an error or a missing limitation? Open a GitHub issue with the tool name, the statement to change and a primary source. You can also submit a pull request that updates the catalog data.