Privacy Isn't a Feature — It's a Foundation
Most web tools treat privacy as an afterthought. Upload your files, trust the server, hope they delete it. We think that's backwards. Privacy should be the starting point, not a checkbox.
This post explains how we architect our tools to process your data locally, why that matters, and what trade-offs we navigate to make it work.
The Client-First Architecture
Our tools follow a simple principle: if it can run in the browser, it should run in the browser. Here's how that works in practice:
- File reading — The browser's File API reads your file directly from disk into memory. No upload.
- Processing — WebAssembly modules handle compression, conversion, or analysis. All computation happens on your CPU.
- Output — Results are generated locally and offered for download. The Blob API creates the file right in your browser.
At no point does your data travel over the network. Our servers deliver the HTML, CSS, and JavaScript that make up the tool — but they never see your actual files.
We can't leak what we never receive. That's not just a privacy policy — it's an architectural guarantee.
When Server Processing Is Necessary
Some operations genuinely require server-side processing — tasks that are too compute-intensive for browser WebAssembly or require resources a browser doesn't have (like GPU-accelerated AI upscaling).
For these cases, we follow strict rules:
- Data is encrypted in transit (TLS 1.3)
- Files are processed in ephemeral containers that are destroyed after use
- No files are logged, cached, or stored beyond the processing window
- We clearly label which tools use server processing vs. browser processing
No Tracking, No Analytics Surveillance
We don't use Google Analytics, Facebook Pixel, or any third-party tracking service. Our analytics are limited to aggregate, anonymous page view counts — enough to know which tools are popular, not enough to identify any individual user.
We don't set advertising cookies. We don't build user profiles. We don't sell data. Period.
Open Source Transparency
Trust but verify. Our client-side processing libraries are open source, so you can inspect exactly what code runs on your machine. The Network tab in your browser's dev tools will confirm that no data leaves your device when using our browser-based tools.
The Future of Private Web Tools
We believe the industry is moving toward local-first computing. With WebAssembly getting faster, WebGPU enabling ML inference in the browser, and storage APIs maturing, there's less reason than ever to send user data to servers.
We're committed to pushing the boundary of what's possible in the browser, so your data stays exactly where it belongs: with you.
