ToolWise is a library of free, browser-based utility tools. This page documents how we build, test, and maintain those tools, and what we will and will not do with your data.
Last reviewed: July 2026
What This Policy Covers
ToolWise publishes two kinds of content: utility tools (interactive pages that perform a specific task, like a JSON formatter or an image compressor) and guide articles (long-form explanations of the concepts behind those tools). The standards below apply to both. They exist so that readers, reviewers, and search engines can trust what they find here.
How We Build Tools
Every tool on ToolWise is built by a named engineer (see the founder’s bio) and shipped only after it passes three checkpoints:
Functional correctness. Each tool is exercised against a fixed set of inputs and the output is compared to an expected result. For tools with a single correct answer (a Base64 decoder, a case converter) this is automated. For tools with subjective output (an AI paraphraser) the output is reviewed by hand before release.
Boundary handling. Empty inputs, very large inputs, malformed inputs, and Unicode edge cases are explicitly tested. A tool that crashes on a 50,000-line file is not ready to ship.
Client-side verification. Wherever a tool claims to run locally, we verify in the browser’s network panel that no file, image, or text payload leaves the device. If a tool must call a server (the AI tools), the page says so plainly in its description.
How We Write Guides
Our guide articles exist to explain why a tool works the way it does, not to pad word count. Each guide is written from scratch by the founder and follows four rules:
Original prose. We do not paraphrase Wikipedia, MDN, or other publishers. If we reference a specification or a third-party fact, we link to the source. No guide is generated by bulk article-spinning software.
Testable claims. Any number we publish (a crack-time estimate, a compression ratio, a word count) is either computed from first principles in the article or cites the source we used.
Practical utility. Every guide links back to at least one working tool on this site so the reader can act on what they just read. A guide with no tool counterpart is not in our scope.
Dated and revisited. Guides carry a publish date and a “last reviewed” date. Articles that reference third-party products (password managers, browsers, libraries) are re-read at least once per year and updated or marked stale.
Data & Privacy Standards
ToolWise is built around a single privacy commitment: your inputs do not leave your browser unless a tool explicitly tells you otherwise. Concretely:
The text, PDF, image, and audio tools that can run client-side do run client-side. We use the File, Canvas, Web Crypto, and WebAssembly APIs to do the work in your tab.
The AI-powered tools (summarizer, paraphraser, grammar checker, translator, essay writer, cover letter generator) call a server endpoint to run the model. Only the text you submit is sent. We do not retain submitted text after the response is returned.
We do not require an account. We do not sell or share user data with third parties for advertising targeting beyond the standard ad-network vocabulary already described in our Privacy Policy.
Cookie-consent for advertising personalization is opt-in via the consent banner; declining it serves non-personalized ads only.
Corrections & Updates
When a reader reports an error in a tool or a guide, we treat it as a bug. Tool bugs are fixed and retested before the next deploy. Factual errors in a guide are corrected in place, with a note added to the article recording what changed and when. We do not silently rewrite history.
We do not publish AI-generated articles pretending to be human-written. Every guide carries a named author.
We do not accept sponsored or paid-placement tool reviews. There is nothing to buy on this site and no “premium” tier.
We do not scrape or republish other publishers’ content.
We do not gate tools behind email capture, downloads, or browser extensions.
Summary
ToolWise is a small, named team building tools we wanted to exist ourselves. We test what we ship, write what we know, keep your data in your browser, and fix what readers tell us is broken. That is the whole policy.