Editorial Policy
CaseWren is a tools site, not a newsroom — but the copy still needs rules. These are the standards every page is written to.
How tools are built and tested
Every CaseWren tool runs on a shared, unit-tested transformation library — the conversion, encoding and analysis logic carries hundreds of automated test cases that must pass before any build ships. New tools ship only with bilingual copy, a how-to section and an FAQ.
Copy standards
We write only what the tool can prove. Feature claims are limited to behavior you can verify on the page itself — we do not publish invented statistics, unsourced market figures or testimonials we do not have. If a claim cannot be checked, it does not go on the site.
Corrections
Found a wrong result, a broken conversion or a factual error in the copy? Email hello@casewren.com with the tool name and an example. Verified bugs go into the test suite so they cannot regress, and fixes ship with the next build.
Updates
The site is updated continuously — the footer of every page shows the build date of the version you are reading. CaseWren currently ships 147 tools; new tools and fixes are released together rather than on a fixed schedule.