Privacy

Local processing

Files are processed in your browser using the File API, Canvas, Web Workers and WebAssembly. A file you select stays in that browser tab's memory and is discarded when the tab closes. Nothing is uploaded, stored, or logged.

This is an architectural property, not a policy: there is no backend, no database, and no file storage to upload to.

No unnecessary uploads

A tool never sends a file, its contents, or its name anywhere. That includes analytics, error reporting and third party scripts. If a feature would require it, it does not ship.

Site analytics

The site uses Firebase Analytics to see which pages and tools get visited, and whether a tool run succeeded, failed or produced a download. Each of those events carries only a tool's name and category, plus the standard device and approximate location data any site using it collects. It never sees a file, a file name, or anything typed into a tool.

If server processing is ever needed

A small number of tools may eventually need a server for a format that is impractical in the browser. If that happens, it is an explicit per tool decision, never a silent fallback, and the tool page states plainly what is sent, why, and how long it is kept. The default stays local; server processing is opt in and the rest of the site stays browser only.

Contact

Questions about this policy can be sent through the contact details on the homepage.