How we build & verify tools

TweakMill does not run a commercial QA laboratory. What we do instead is publish specific behaviour on each tool page, fix mistakes when readers report them, and document where numbers come from when data crosses the network. This page is for anyone reviewing the site for publisher or search programmes—or for readers who want to understand our limits honestly.

What “verification” means here

Functional checks. Before we ship or materially change a tool, we exercise it on current desktop browsers (typically Chromium-family and Firefox) at common breakpoints. For layout-heavy pages we also glance at a narrow phone viewport—real users skew mobile on calculators and games.

Regression priorities. If time is short, we prioritise tools where wrong output could mislead someone about money, safety framing, or privacy expectations: currency flows, mortgage-style calculators where present, translation relay paths, and anything that claims “runs locally” in the browser.

No SLA. We are a small operation; there is no guaranteed fix timeline. What we do commit to is a published Contact channel and visible legal pages (Privacy, Terms, Disclaimer) so problems have somewhere legitimate to land.

Network-backed tools

Some utilities compare against reference datasets rather than inventing rates locally. Example: our currency tools document ECB-style reference publication via Frankfurter. When upstream schedules or symbols change, behaviour can shift until we adapt labels or parsing—another reason we tell users not to treat outputs as bank quotes.

Universal translation may reach third-party mirrors from the browser or through an optional same-origin relay; failure modes are explained on Universal translator. If both paths fail on a visitor’s network, that is an environmental constraint we surface rather than hide.

Privacy-sensitive claims

Smart rewrite documents that listed rewrite modes execute without sending your draft to our servers for rephrasing—those transforms are designed to stay in-tab. Other pages call out different behaviour (network fetch, relay, ads). We repeat this because privacy expectations are easy to get wrong if marketing copy is vague.

Games and dictionaries

Word games and helpers ship with an embedded word list or generator logic described on-page (for example how crossword patterns differ from tournament Scrabble word lists). Verification here is mostly logical consistency—illegal moves rejected, pattern filters behaving as documented—and readability on small screens.

How you can help

Concrete bug mail reduces guesswork: share the exact URL, browser version, what you typed, what you saw, and what you expected. Screenshots help for layout breaks. If something feels “thin,” tell us which sentence misled you—we may expand that tool’s on-page guidance rather than hiding behind generic hype.

Companion pages: Quality & sources · BBQ planner methodology. Site legal stamp: 2026-04-22.