How pages are researched
Pages are built from the developer's public documentation, the behavior of the software as described in that documentation, and general knowledge about how Windows manages disk space, file systems, and permissions. Where a page describes a step-by-step process, such as how to use TreeSize, we describe the general workflow rather than a specific dialog that may change between versions.
Claims we refuse to publish
Some kinds of claims go stale or become misleading faster than we can maintain them, so we avoid stating them as fact:
- Current prices. Pricing changes on the vendor's schedule, not ours. Pages point to the developer's site for current pricing instead of quoting a figure.
- Specific version numbers as current. We reference version numbers only when discussing history or a documented change, never to imply a stated version is the latest one available today.
- Benchmark or performance figures we have not run ourselves. We do not publish scan-speed or memory-usage numbers we cannot reproduce, and we do not repeat a vendor's marketing benchmark as independent fact.
- Legal or licensing conclusions. We describe what license terms generally exist for the free edition versus paid editions in broad strokes and tell readers to confirm specifics with the developer before commercial use.
How we word uncertainty
When behavior can vary by Windows version, permissions, or TreeSize edition, we say so explicitly instead of stating a single outcome as universal. Phrases such as "usually," "in most cases," or "confirm on the developer's page" are used deliberately, not as filler. If we are not confident about a detail, we leave it out rather than guess.
Corrections and the review date
Every page shows the date it was last reviewed. That date means the page was checked against the developer's current documentation and general Windows behavior on that date; it does not mean every sentence was rewritten. When a factual error is reported through the contact page, we correct the page and update its review date at the same time.
We do not silently rewrite a page's substance without updating the date, and we do not backdate corrections.
Independence from the vendor
jam-software.org has no business relationship with JAM Software GmbH. We do not receive compensation from that company, we do not host their installers, and we do not sell licenses. See About for the full non-affiliation statement.
Continue reading
Last reviewed by the jam-software.org editorial team on . Spotted something out of date? Tell us.