How our tools work
Where your data goes, where our numbers come from, and how we test.
Where your data goes
57 of our 58 tools run entirely in your web browser using JavaScript. Text, code and images you enter are processed on your own device and never sent to our servers. You can confirm this by opening your browser’s developer tools and watching the Network tab while you use a tool.
The Core Web Vitals checker is the exception: to measure a page, Google’s PageSpeed Insights service has to load it. We send only the public URL you enter to Google, through our own server so you don’t need an API key. We don’t store it.
Where the numbers come from
- Readability uses the published Flesch Reading Ease and Flesch–Kincaid Grade Level formulas.
- SERP preview estimates pixel width using the fonts and sizes Google uses on desktop results.
- Core Web Vitals comes directly from Google PageSpeed Insights (Lighthouse lab data).
- Specs checker limits are compiled from each platform’s public help pages and dated so you know when they were last checked.
- Keyword ideas are pattern-based suggestions, not search-volume data, and the tool says so.
How we test
Before a tool is published, we run it with realistic inputs and edge cases: empty input, very long text, unusual characters, and files that are too big or the wrong type. Minifier output is executed to confirm it still works, and generated QR codes are scanned to confirm they decode correctly.
When a tool doesn’t meet the bar
We remove it. Our former plagiarism checker depended on a web-search service that is no longer available to new projects, so rather than leave a broken tool online, we retired it.