Why most TextFixer tools run in your browser

A case converter does not need my server. Neither does a line-break cleaner, a JSON formatter, or a Base64 encoder. Those are string operations. Sending your draft to a datacenter to capitalize letters would be slower, more expensive, and a privacy problem I cannot justify.

What “in your browser” means

The page downloads a script. The script reads the text in the box and writes the result back into the page. If you turn off the network after the page loads, the non-AI tools still work. I never receive the text. I cannot log it because it is not on my machines.

That is also why these tools work on a plane and why a company can paste a customer list without signing a data-processing agreement with me for that paste.

The exception: AI tools

Rewriting a paragraph, summarizing a report, or explaining a stack trace needs a language model. Those tools send the text you submit over HTTPS to OpenAI, only to produce the result. TextFixer does not store the prompt. You should still not paste passwords, medical records, or unpublished legal strategy into an AI box.

Every AI tool page says this in the privacy copy. The label “AI” in the nav is the other signal. If the page does not say AI, the text stays on your device.

Why I still have a server

The site has to be hosted. Analytics, if you allow it, and ads, if AdSense is approved, run on Google’s side. The AI proxy keeps the model key off the public page. None of that requires your tool input. Those are separate pipes.

If a vendor ever needs the contents of the box, the page will say so before you click Generate. The QR tool is the other exception: it sends the string to api.qrserver.com to draw the image. That is in the privacy policy on purpose.