Privacy policy

The short version

• What you type into a tool stays in your browser. It is never uploaded, stored or logged by this site.
• As the site stands today no cookies are set, and there is no account, login or user profile.
• Page views are counted with anonymous, cookie-less analytics that never see a tool's input.
• The one place you can deliberately send data is the suggestion form, and only when you press Send.

What stays in your browser

Every tool is a client-side program. Formatting JSON, decoding Base64, hashing a string, generating a password, parsing a cron expression, diffing two blocks of text — all of it happens in the page you have open, using JavaScript and the browser's built-in APIs. There is no backend to receive the input, because the site is exported as static files and has no API routes.

Concretely, that means the following never leaves your device: the text you paste or type, the output the tool produces, files you have open, anything you copy to the clipboard, and any secret that happened to be inside one of them — an API key in a config file, a token in a JWT, a customer record in a CSV.

The only thing the site stores on your device is your theme preference, saved in localStorage under the key "theme" so the page does not flash the wrong colours on your next visit. It contains nothing but the name of a theme, it is not sent anywhere, and clearing your browser storage removes it.

What does leave your device

Three things, none of which involve the contents of a tool.

1. The request that loads the page

Like every website, loading a page means your browser contacts the server hosting it. That server sees your IP address, your user agent and the URL you asked for, and its infrastructure may keep short-lived request logs for operational and security reasons. This is inherent to HTTP, applies to the static files only, and happens before any tool code runs.

2. Page-view analytics

The site uses Vercel Web Analytics (the @vercel/analytics package) to see which tools people actually use. When a page loads it records a page view: the path visited, the referrer that led there, and coarse information derived from the request such as browser, operating system, device type and country.

Per Vercel's documentation, Web Analytics sets no cookies, writes nothing to your browser storage, and does not store the IP address of the request; returning visits are counted through a hash derived from the incoming request that is rotated regularly rather than a persistent identifier, so the measurement cannot follow you to other sites. The script is served from this site's own domain, under /_vercel/insights/, and the aggregated data is processed by Vercel as the hosting and analytics provider. Their current terms are documented at vercel.com/docs/analytics/privacy-policy.

What analytics never receives is the content of a tool: no input, no output, no file names, no clipboard data. If you block the request with an ad blocker, a content blocker or a privacy extension, every tool on the site keeps working exactly as before.

3. The suggestion form

The Suggest a tool page is the one part of the site that sends data to a server, and only when you submit it. It transmits what you typed: the tool name, your description of it, and an email address if you chose to give one — the field is optional and a suggestion without it is accepted. The submission goes to a third-party form provider configured at build time, which forwards it as an email to the maintainer; the provider processes it under its own terms. The form warns you not to include keys, tokens, passwords or personal data, which is worth taking literally.

Cookies

At the date above, this site sets no cookies: not for analytics, not for preferences, not for advertising. That is why you are not being asked to dismiss a consent banner — there is nothing yet to consent to beyond the anonymous page view described above. If a service that does set cookies is introduced, advertising included, this section and the consent handling change with it, before it ships.

Third-party content

As of today the site carries no ads, no advertising SDKs, no social media embeds, no chat widgets, no A/B testing scripts and no session recording. Web fonts are downloaded at build time and served from this site's own domain, so opening a page makes no request to Google Fonts or any other font host. Apart from the analytics endpoint described above and any link you follow yourself, a tool page makes no outbound network requests.

That is a description of the present, not a vow. The site has running costs and is expected to pay for itself eventually, so advertising or sponsored placements may appear later. If they do, this page will name what was added, what it collects and whether it sets cookies, and it will be updated before the script goes live rather than after someone notices it. The line that does not move is the tool input itself: it is processed in your browser, the site never receives it, and there is therefore nothing in it to sell, share or hand to an advertiser.

Data we hold about you

None, unless you sent it through the suggestion form. There is no user database, because there are no users to store — no accounts, no profiles, no saved documents, no history of what you converted. Analytics data is aggregate and not linked to an identity, so there is no per-person record to look up, export or delete.

If you did send a suggestion and want it deleted, or want the email address you supplied removed, send that request through the same form and it will be deleted from the inbox that received it.

Changes to this policy

If the site starts collecting something new — a different analytics provider, an advertising or sponsorship script, an optional saved workspace, anything at all — this page is updated before the change ships, and the date at the top changes with it. Where a section describes what the site does not do, read it as a statement about the version dated above, not as a permanent commitment; the commitment is that this page keeps matching what actually runs.