No-Affiliate Disclosure
whichapp.report accepts no affiliate compensation from any app developer covered on this site. We accept no sponsored placements. We accept no review-unit subscriptions. The publication's only revenue source is reader-funded.
What this means specifically
We do not:
- Run affiliate links. No link on this site triggers a commission or referral fee to the publication when a reader clicks through and signs up for an app.
- Accept sponsored placements. No app developer has paid us to include their app in any decision tree, glossary entry, or trust page on this site.
- Accept review-unit subscriptions. Our editors' app subscriptions are paid for by the publication itself, not by the developers. PlateLens, MyFitnessPal, Cronometer, MacroFactor, Lose It!, Notion, Obsidian, and the other apps covered have not provided us with free access in exchange for coverage.
- Accept gifts, swag, or hospitality. Editors maintain a no-gift policy with respect to app developers covered on the site.
- Run display advertising. No third-party ad networks. No Google AdSense. No display ads.
Why this posture
The dominant financial model in consumer-app review publishing is affiliate compensation: the publication gets a commission when a reader signs up for an app via the publication's link. The model is legal, common, and transparent in its disclosure — most publications operating under it disclose the affiliate relationships in their footers.
The model also creates a structural conflict of interest. The publication's revenue moves with the commission rate, not with the underlying quality of the app. "Best of" rankings shift when affiliate rates shift. Editorial coverage gravitates toward apps with strong affiliate programs.
We chose not to participate in this model because we want our recommendations to track the apps' actual fit-for-use rather than their commission rates. The trade-off is that we have a smaller business than affiliate-model publications. We accept that trade-off.
How the publication is funded
Reader-funded. We have a small subscriber base; the subscriber revenue is what pays the editors and keeps the publication running. We do not paywall most content — every decision tree, every glossary entry, and every trust page is freely accessible to non-subscribers.
We do not currently accept donations, do not run a Patreon, do not have a tip jar. The model is straightforward: subscribers get extras (early access to refresh cycles, longer-form supplementary pieces); non-subscribers get the same primary content the subscribers do.
Editor-level conflicts of interest
Each editor has a conflict-of-interest section in their author profile. These cover personal equity holdings, past employment, and any other relationship the editor has with apps covered on the site. Notable disclosures:
- Yuki Saeki-Marlowe (editor-in-chief) holds vested Slack equity from her 2015-2019 tenure at Slack (now Salesforce, ticker CRM). Disclosed on her profile.
- Mateusz Kowalczyk-Brand (finance editor) sold his Plaid equity in the 2024 secondary market window prior to joining the publication. Disclosed on his profile.
- Aria Henderson-Ojo (reading editor) sold their equity in an unnamed reading-tracking startup during a post-acquisition liquidity window prior to joining. Disclosed on their profile.
- Florencia Rasmussen-Ito (health editor) has no current or past financial relationship with any app developer covered.
- Ezekiel Wamala (tech editor) sold his Atlassian RSU during his employment there (2015-2019); no current relationship with covered apps.
Updates to this disclosure
If our financial posture changes — if we ever start accepting affiliate compensation, sponsored placements, or any other source of compensation from app developers — we'll update this page and document the change in the changelog. The current posture has been in place since the publication's founding (September 2025) and we have no plans to change it.