02 — SecureConverterOur own product
The file never leaves your computer
A product that converts, analyses and prepares video, image, audio and documents with artificial intelligence running entirely in the browser. Privacy by architecture rather than by policy — the only kind anyone can verify.
The facts
- What it is
- Our own product. SaaS with free, pro and enterprise plans.
- What we did
- All of it: product, design, engineering and business.
- The idea
- That file content never reaches a server. Not even ours.
- Year
- 2026.
Every online file converter asks for the same thing: upload the file. And with that, a law firm's contract, somebody's payslip or a client's video end up on a server you do not control, under a privacy policy that says it gets deleted and that you cannot verify.
SecureConverter flips the architecture instead of the policy. The bytes are processed in the browser; the server only knows who you are, which plan you are on and how many conversions you have run.
How it works
The content is not uploaded. Web Workers, WebAssembly, Canvas and WebGPU do the work inside the tab. You can check it by opening developer tools: there is no request with the file inside it.
Four execution paths, depending on the device. On desktop with WebGPU, the model is chosen by the device's memory. On iPad and iPhone, a real WebGPU probe and, if it fails, a descent through successively smaller quantisations before giving up. On Android and desktops without WebGPU, the model runs on WebAssembly. Making it work on a laptop is not the achievement: not falling over everywhere else is.
Video, audio, image and document. Video and audio conversion, image compression, PDF text and manipulation, optical character recognition, text document reading, and metadata inspection and cleanup — all inside the same boundary.
A visual workflow builder. Chain operations and save them to run again, which is where a converter stops being a loose utility and starts being a team tool.
The numbers
- 0file bytes sent to the server
- 4AI execution paths by device
- 3engines: WebGPU, WebAssembly and CPU execution
- 4format families: video, audio, image and document
Only the first one really matters, and it is the one almost nobody can write.
What nobody shows
The server is not decoration: it handles identity and sessions, billing, email and a few aggregate counters — how many conversions, how many messages, how many bytes. And in the default configuration, models are downloaded from an allowlisted public origin. None of that touches file content, and saying it plainly is more useful than a privacy badge.
«In the browser» is not magic either: a small model on a mid-range phone is not a large model on a server. That was a deliberate product decision — a slightly worse result beats an uploaded file.
Let's talk
Tell us what you're building.