Why the tools have no accounts

Every tool on this toolchain keeps its state in the visitor's browser. None of them has a login, a server-side store, or a row with your name on it. That is a deliberate choice with real costs, and it is worth setting out both sides.

The security argument is the boring one

A database of user work is a liability that grows on its own. It needs encryption at rest, backups, a retention policy, an access log, a deletion path, a breach process and someone to own all of it. None of that work makes the tool better. All of it has to be done correctly forever, and the failure mode is other people's data in someone else's hands.

The cheapest way to secure a store is not to have one. A page that never had a backend cannot leak it. When a certificate decoder tells you it parses in your browser, that is not a promise about our operational discipline, which you cannot verify. It is a claim about where the code runs, which you can verify by reading the bundle or by watching the network tab while you use it.

The second argument is about incentives

An account creates a relationship that wants to be maintained. Maintenance wants engagement. Engagement wants email. Email wants a reason to send it. Every tool that started as a utility and ended as a newsletter took that path one reasonable step at a time.

Removing the account removes the first step. There is no list to grow, so nothing here has a motive to become something else.

What it costs

This is not free, and we would rather name the costs than pretend they are not there.

• No sync. Work started on a laptop is not on a phone. For a calculator

that is fine. For an invoice you revise over a week, it is a real limitation, which is why the invoice tool exports a file.

• Clearing site data loses everything. There is no recovery, because there

is nothing on our side to recover from. Tools that hold something worth mourning offer an export for that reason, and only those tools do.

• No collaboration. Two people cannot work on the same document. Where that

matters, these are the wrong tools.

• Browser limits are real. Storage can be refused in a private window or by

a policy. Every tool handles that case with a message that says so, rather than failing silently.

What we did not do

We did not add an export button to every tool.

It is tempting: it looks like a feature, it costs an afternoon, and it appears in a list of capabilities. What it actually produces is the same disconnected control on nine apps, most of which hold nothing anyone would mourn. A backup for a subscription list that took an hour to build is a feature. A backup for a loan calculation you can redo in fifteen seconds is clutter with an implied promise attached.

So export exists where losing the work would hurt, and nowhere else.

How to check any of this

Open the network tab and use a tool. Nothing of yours goes out. Read the source on GitHub (V-3), which is where these are built. Or read the built bundle served from the host itself (V-2) and search it for a URL.

We would rather be checked than believed.