What to include in a report
A useful report lets us find and check the claim quickly. Please include:
- The exact page URL where you saw the issue.
- The sentence or claim you believe is wrong or outdated.
- What you believe the correct information is, ideally with a source such as the developer's own documentation.
- Your TreeSize version and Windows version, if the issue is about behavior that seems to have changed between releases.
We cannot act on vague reports such as "this page is wrong" without knowing which claim is in question.
What we cannot help with
Because we are an independent editorial site and not the developer, we cannot help with:
- Installing, activating, or troubleshooting TreeSize itself.
- License keys, renewals, upgrades, or refunds.
- Account or billing questions tied to a purchase made on the developer's site.
- Requests for support tickets or bug reports about the software's behavior.
Those requests need to go to JAM Software directly through their own website. Our is-it-safe page and troubleshooting page cover the most common issues in general terms, but they are not a substitute for vendor support.
How corrections are handled
When a correction is confirmed, we update the affected page and refresh the review date shown at the bottom of it. We do not promise a specific turnaround time, but factual errors are treated as a priority over stylistic edits. Our general approach to accuracy is described in the editorial policy.
Contact questions
Will I get a personal reply?
We read every message sent to the address on this page, though we cannot guarantee an individual reply to every one, particularly for questions better directed to the developer.
Is this the right place to ask for a refund?
Continue reading
Last reviewed by the jam-software.org editorial team on . Spotted something out of date? Tell us.