Somewhere along the way, "free online tool" started to mean something different. You search for a simple BMI calculator, click the first result, and before you can type a single number you're asked to create an account, confirm your email, accept forty cookies, and — if you read the privacy policy, which almost nobody does — agree to have your health data "shared with trusted partners." For a calculation your browser could have done in a microsecond, offline.
ToolWeb exists because we think that trade is absurd. This article explains, in concrete technical detail, how we built twelve tools that never ask who you are, why that architecture matters more than any privacy policy, and how you can verify every claim we make yourself — no trust required.
The hidden price of "free" calculators
Most free tool websites follow one of three business models. The first is honest advertising: show ads, keep the tool free. The second is data collection: the tool is bait, and the real product is your input — email addresses harvested at signup, health metrics from BMI forms, financial details from budget calculators, all packaged for marketing databases. The third is the upsell funnel: the "free" tool is deliberately crippled until you subscribe.
The second model is the one that should worry you, because it's invisible. When a BMI calculator sends your height and weight to a server "to compute your result," that data has left your control forever. You have no way of knowing whether it was logged, linked to your IP address, or sold. The privacy policy might promise good behavior — but a promise is not an architecture.
Our answer: computation that never leaves your device
Every ToolWeb tool — the password generator, BMI calculator, word counter, age calculator, Hijri date converter, and the rest — runs entirely in your browser using client-side JavaScript. When you type a password length or a birth date, that value lives in your device's memory, is processed by your device's CPU, and is displayed on your screen. It is never transmitted, because there is no code in the page that transmits it.
This is not a policy decision that could quietly change in an update. It is an architectural one with real consequences:
crypto.getRandomValues() — a cryptographically secure random source — and the resulting password exists only in your page's memory until you close the tab. We could not log your passwords even if we wanted to.
The one exception, explained honestly
One tool on this site genuinely needs the internet: the currency converter. Exchange rates change by the minute, so the page fetches current rates from a public exchange-rate API. Here is exactly what that request contains: the currency pair you selected — for example "EUR to USD" — and nothing else. No amount, no identity, no account. The conversion math itself still happens on your device.
We mention this because a privacy claim that hides its exceptions isn't a privacy claim; it's marketing. If we ever add a tool that requires a network call, this is where we will document precisely what it sends.
What we do collect — and how to say no
ToolWeb is funded by advertising, and we believe you deserve the same transparency about that as about the tools. Two third-party services can run on this site:
Google Analytics tells us which tools people use and which articles they read, so we know what to improve. Google AdSense displays the ads that pay for hosting and development. Both are governed by a consent banner: when you first visit, all tracking is switched off by default (a setup called Consent Mode), and it stays off unless you explicitly accept. Decline, and the tools work exactly the same — analytics and personalized advertising simply never activate for you. The full details, including how to change your choice later, are in our privacy policy.
Don't trust us — verify us
The best property of client-side tools is that our claims are checkable by anyone in about ninety seconds. Here's how:
We designed for this verifiability on purpose. Any site can write "we respect your privacy" in a footer. Very few can say "turn off your internet and watch the tool keep working."
Why two languages, and what's next
ToolWeb ships in English and French from a single interface — not as an afterthought translation, but because everyday tools are exactly the kind of software that should meet people in their own language. A password's strength or a date conversion shouldn't depend on your English comfort level. The language toggle in the navigation switches every tool and label instantly, and your choice is remembered locally on your device (in localStorage — again, not on a server).
The roadmap follows the same philosophy: more tools, same rules. Anything we add must work without an account, compute locally wherever technically possible, and document any exception the way the currency converter is documented above. If a proposed feature can't meet that bar, it doesn't ship.
Put the claim to the test
Open the password generator with your network inspector running — or in airplane mode — and see for yourself. Then explore all twelve tools.
Frequently asked questions
If nothing is sent to a server, how do you know how many people use the site?
Through Google Analytics — but only for visitors who accept the consent banner, and it records page-level usage (which pages are visited), never the values you type into tools. Tool inputs are handled by local JavaScript that has no connection to analytics code.
Can I use ToolWeb for sensitive data like client documents or medical values?
Yes — that's precisely the use case client-side processing is best for. Text pasted into the word counter and numbers entered into calculators are processed in your browser's memory only. For maximum assurance on highly confidential material, load the page first and then go offline before pasting.
Do the tools store anything at all on my device?
Two small preferences: your language choice and your light/dark theme, both kept in your browser's localStorage so the site remembers them next visit. They never leave your device, and clearing your browser data removes them instantly.
How is this different from other tool sites that also claim privacy?
The difference is verifiability. We don't ask you to trust a policy; we invite you to open the network inspector or switch to airplane mode and observe the architecture directly. A claim you can test yourself is worth more than any certification badge.
Will ToolWeb ever require accounts for "premium" features?
No. The no-account rule is the founding constraint of the project, not a launch promo. Features that would require server-side storage of personal data are simply out of scope by design.