Editorial Policy

This is the publication's documented editorial policy. It covers the review chain, our fact-checking standards, our corrections process, and our conflict-of-interest disclosure standards. Any deviation from this policy is itself documented in the changelog.

The review chain

Every decision tree, glossary entry, and trust page on this site goes through the following review chain before publication:

1. Writer drafts. The writer is one of the five editors documented on the editorial team page. The writer's vertical is the category they cover (productivity, health, finance, reading).
2. Cross-vertical reviewer reviews. A second editor outside the writer's vertical reviews the draft for clarity, structural consistency with the publication's house style, and methodological adherence to the decision-tree framework. Disagreements are resolved before publication.
3. Editor-in-chief signs off. Yuki Saeki-Marlowe (editor-in-chief) reads every piece before publication. The sign-off is recorded in the changelog.

This chain is shorter than some publications use because the team is small and the cross-vertical review step does most of the work. The editor-in-chief's sign-off is non-perfunctory — meaningful changes happen at this step on roughly 1 in 4 pieces.

Fact-checking

Every factual claim in a decision tree is checked against a primary source where available. The primary sources we lean on:

• App pricing claims. Verified against the app's official pricing page on the date of publication. We document both the date and the price tier.
• Accuracy claims for calorie apps. Verified against the Dietary Assessment Initiative's published validation studies. We do not run our own validation — see calorietrackerlab.com's methodology for that work in this category specifically.
• Behavior-change research claims. Verified against published peer-reviewed research with citations.
• Author credential claims. Editors document their own credentials in their author profile pages, which serve as the primary source for their own background.

Corrections

If you find a factual error in any piece on this site, email corrections@whichapp.report. We will:

1. Acknowledge receipt within 5 business days.
2. Investigate the claim, contacting the relevant source if necessary.
3. If the correction is warranted, update the piece and add a corrections note explaining what was changed.
4. Add a changelog entry documenting the correction.
5. Email you (the reporter) confirming the correction.

If the correction is not warranted, we'll explain our reasoning. We don't ignore corrections requests; we respond to all of them.

Conflict-of-interest disclosure

Every editor on this site discloses their conflicts of interest in their author profile page. The standard disclosure covers:

• Current and past equity holdings in apps covered by the publication.
• Current and past employment at apps covered by the publication.
• Current and past consulting/contract relationships with apps covered by the publication.
• Personal subscriptions or use of the apps covered (typically not a COI but disclosed for transparency).

The publication itself does not accept affiliate compensation, sponsored placements, or review-unit subscriptions. See our no-affiliate disclosure for the full posture.

Tone and house style

The publication's tone is pragmatic, structured, helpful, modestly nerdy. Heavy use of conditional structure ("if you... then..."). Mono headers, prose body, code-style aesthetic where appropriate. We deliberately avoid:

• Listicles. Every piece is a decision tree, a glossary entry, or a trust page.
• Affiliate disclosure boilerplate. We don't have affiliates, so the boilerplate isn't relevant.
• "Best of" framing in titles. Our titles use the conditional form ("Which X for You?") deliberately.
• Sponsored content. None exists on this site.
• Aggressive newsletter / app / push-notification prompts. Reader experience matters.

What this policy doesn't cover

This policy doesn't cover privacy, terms of service, or data-processing agreements — those are documented separately on our privacy and terms pages. It also doesn't cover the technical infrastructure of the site (Astro, AWS, etc.); those are documented in the project README rather than on the public site.