Privacy
The short version: tools on My Tiny Utils process your input in your browser, not on a server. There are no accounts, no advertising, and no third-party tracking scripts. This page explains precisely what runs where, what the site does and does not collect, and what any web server unavoidably sees.
What “processed locally” means
Tools marked with the “Processed locally in your browser” badge do all of their work in JavaScript running on your device. When you paste a JSON document, decode a token, or convert a file, the transformation happens on the page itself — your input is never uploaded, sent to an API, or put into a URL. Currently 196 of the 196 tools in the catalog process locally, which is all of them; if that ever changes, the affected tool will say so on its page.
This is why the tools are safe to use with sensitive data — tokens, credentials, production configs, private documents. The data stays on your machine.
What the site does not collect
- No accounts. There is nothing to sign up for, so the site holds no user profiles, emails, or passwords.
- No tracking scripts or ads. Pages ship no third-party analytics, ad networks, or social-media embeds. Fonts and all other assets are served from the site’s own origin, so viewing a page triggers no requests to third parties.
- No cookies from our code. The site’s own code sets no cookies. Your theme preference (light or dark) is kept in your browser’s local storage and never leaves your device.
- No tool content, ever. The codebase includes a usage-measurement layer whose events are typed so they can only carry tool identifiers — never input or output. No measurement vendor is currently connected, so as of this build even those events go nowhere.
What does reach a server
Two kinds of requests leave your browser when you use the site:
- Page and asset requests. Like any website, loading a page sends an ordinary web request. The servers and content delivery network that host the site see the standard details of such requests — the requested URL, your IP address, and your browser’s user-agent string — and may keep routine, short-lived logs of them for operating and securing the service, as is standard for web hosting. Because tool input never goes into URLs, it cannot appear in these logs.
- Tool search. The search box and command palette look up tools by sending the text you type there to the site’s own search endpoint, which matches it against the tool catalog and returns results. This applies only to text typed into search — never to anything you enter into a tool.
Changes
This page is generated from the same codebase as the tools it describes, so it reflects the current build of the site. If how the site handles data ever changes — for example, if a privacy-respecting analytics service is connected — this page will be updated in the same release.
The about page covers how the site is built, tested, and why it works this way.