The Case for Client-Side AI: Why Privacy-by-Architecture Beats Privacy Policies

Almost every free online tool follows the same shape: upload your file, a server processes it, you download the result, and somewhere in between your data sat on infrastructure you have no visibility into and a privacy policy you didn't read. TBC Tools takes a structurally different approach for its public-facing tools — file conversion, invoicing, accounting, an open-source API aggregator — none of it touches a server. The processing happens entirely in your browser.

A promise versus a constraint

"We take your privacy seriously" is a policy — a statement of intent a company can quietly walk back. "Your data is processed in the browser and never reaches a server" is an architectural constraint — it's not a promise that can be broken without literally rewriting the application. Every tool in the hub — the file-to-Markdown converter, the invoice generator, the local accounting tracker — stores its state in `localStorage`/`IndexedDB` on the visitor's own machine, not TBC's infrastructure.

What this costs, and what it buys

The honest trade-off: client-side-only means no cross-device sync, no cloud backup, no admin dashboard of user data to analyze. For TBC, that's not a limitation to route around — it's the entire point. Cloud infrastructure cost for the public tools is $0 by design, which is what makes the whole hub sustainable to run for free with no signup wall. The tools that genuinely need a paid API — an SEO auditor calling Gemini, a travel planner calling a weather API — follow a strict bring-your-own-key pattern: the visitor's own API key, entered at runtime, stored in browser storage only, never logged or persisted server-side.

You can't leak what you never received. That's not a privacy feature — it's a category the product doesn't belong to.

The one deliberate exception

• One internal, password-gated operator dashboard reads a real database — isolated to its own route, never linked from the public hub, never touched by tool-facing code
• Every public tool remains framework-agnostic at the logic layer, so it can be lifted out into its own standalone open-source repo without a rewrite
• Seven-plus tools, one quiet graphite shell, each keeping its own accent color as its only visual identity

Most AI and SaaS tooling asks users to trust a privacy policy. TBC Tools' bet is that architecture is a more credible promise than a paragraph of legal text — and that a genuinely free, genuinely private tool is worth building even when it means giving up the convenience features a server would make trivial.