Terms of Service
Last updated: April 30, 2026.
About these terms
These terms govern your use of whichapp.report. They're short on purpose. They cover the legal basics; if you have questions email editor@whichapp.report.
Use of the site
You may read this site freely. You may share links to pieces. You may quote short passages with attribution.
You may not: scrape the site at high volume to rebuild it elsewhere; republish whole pieces without permission; misrepresent yourself as the publication or any of its editors.
Editorial content is informational, not advice
The decision trees and glossary entries on this site are editorial content. They are informational, not advice. We do not know your specific situation. The recommendations are calibrated for typical users matching the conditions in each branch; your situation may differ.
For decisions with significant financial, health, or legal consequences (e.g., health-app selection in the context of a clinical condition; finance-app selection in the context of a serious financial decision), consult a qualified professional in addition to using our content.
External links
We link to apps, research papers, and external resources. We're not responsible for the content or behavior of those external sites. Their terms apply when you visit them.
App pricing and features change
The decision trees on this site are dated. App pricing, features, and competitive positioning change over time. We refresh trees quarterly (see the changelog), but between refreshes the information may be slightly stale. Always verify current pricing on the app's official site before subscribing.
Limitation of liability
To the extent permitted by law, whichapp.report is not liable for any losses you incur from acting on our editorial content. The recommendations are informational; you make your own decisions.
Governing law
These terms are governed by the laws of the State of New York, USA. Disputes are resolved in the courts of New York County, NY.
Changes to these terms
If we change these terms materially, we'll post the change here and document it in the changelog.