Skip to main content

How ToolUpKit works

Last updated: September 19, 2026

ToolUpKit is a set of browser-based utilities. That phrase is usually filler — here it is a technical description. Every calculator, converter and generator on this site is a static page containing JavaScript. When you type a number or paste a document, the work happens inside your own browser tab. No server takes part in the calculation.

At a glance

  • No account, no sign-up, no email required
  • Inputs, files and results are processed in your browser
  • Nothing you enter is uploaded, stored, or written to our logs
  • Tools keep working after you disconnect from the network

There is no server doing the work

Most online tools work by sending your input somewhere: you type in the browser, the browser posts your input to an API, the API computes an answer and sends it back. That design is what makes the result possible — and it is also why your input leaves your device and exists on someone else's machine, at least for the duration of the request.

ToolUpKit has no such backend. The site is generated ahead of time into plain HTML, CSS and JavaScript files and served as static files. There is no application server to query, no database holding your input, and no API endpoint that accepts it. When you work out a mortgage payment or format a JSON document, the arithmetic runs in JavaScript in your tab — the same way a spreadsheet runs on your own laptop.

This is not a security layer bolted on top of a normal site. It is the architecture. There is no upload path to switch off, because there was never an upload path to begin with.

What that means for your data

  • Your input stays in your tab. The numbers you type and the text you paste are read by JavaScript running in the page you are looking at. They are not posted anywhere.
  • Files never leave your device. Tools that handle images or PDFs read those files through your browser's own file API and process them in memory.
  • Closing the tab erases the only copy. Because nothing was transmitted, there is no server-side copy to delete or to leak. Nothing is kept between visits.
  • Our logs cannot contain your data, because your data never reaches us. This is a property of the design rather than a promise about our behaviour.

How to verify it yourself

You should not have to take any of the above on trust. All three checks below take under a minute, and all three are meant to be run against us.

1. Disconnect, then keep using it

Open any tool and let the page load fully. Now turn off your Wi-Fi (or switch on airplane mode) and carry on using the tool. It keeps working, because the calculation never needed the network. A tool that rounds your numbers on a server cannot pass this test.

2. Watch the network panel

Open your browser's developer tools, go to the Network tab, clear the list, then type into a tool or drop in a file. Nothing you enter produces a request — you will see only the static assets the page already loaded. There is no request carrying your input, because there is no code that would send one.

3. Read the source

View the page source. You will find ordinary HTML, a stylesheet and a script tag. There is no form action pointing at an endpoint, no API key, and no request that includes what you typed. If you are comfortable in a terminal, the same check applies to the files themselves — they are static assets, and static assets have nowhere to send anything.

If any of these three checks fails for you, that is a bug rather than a difference of interpretation, and we would like to hear about it — pleaseget in touch.

What we do collect

Being precise here matters more than sounding pure, so this section is deliberately narrower than the ones above.

  • Tool inputs, files and results: not collected, not stored, not transmitted. This is enforced by the architecture, not by a policy we could quietly change.
  • Aggregate usage statistics: we may use privacy-respecting, aggregated analytics to see which tools are useful and how the site performs. This data is anonymous and is never tied to what you typed into a tool.
  • Advertising: the site is free, and we may display sponsorship or ads to keep it that way. Advertisers never receive your tool inputs — those never leave your browser, so there is nothing to pass on.
  • Email you send us: if you write to us, we keep the message. That is the one place where something you send does reach us — by your choice and through your own mail client.

The full legal wording, including cookies, lives in theprivacy policy.

Why we built it this way

A password generator, a PDF merger or a tax calculator all ask you to hand over something sensitive. The usual arrangement asks you to trust an unfamiliar party with it and hope for the best. Running everything in the browser removes that trade-off entirely: the tool can be useful without ever being in a position to leak anything. It also means the tools are fast — there is no round trip — and that they keep working when your connection does not.