Privacy-First Hybrid Architecture

Documenttoolsthatrespectyourprivacy.

Core tools run locally in your browser with zero unnecessary server uploads. Heavy PDF tasks use ephemeral server pipelines that purge immediately, and the optional cloud vault is protected by authenticated encryption.

Up to ~80% smallerClient-first processing12 tools available
Verifiable proof

Drop → Process → Download in action

Watch client-side WebAssembly compression in real-time. Document bytes process directly in browser memory.

Client-side processing in action
Demo workflow:2.4 MBLocal WASM482 KB (~80% smaller)
Try with your own file
Data Architecture Proof

Watch your network tab. This is real.

For standard document tools, zero bytes are transmitted to remote servers. All parsing, conversion, and rendering execute directly in client memory.

Inspectable client sandbox
Local Document
In-browser volatile memory
Egress Blocked
WASM & Canvas Sandbox
Zero external server calls
Direct Local Save
Downloaded straight to device
All tools

Tools

How It Works

Three steps. Zero unnecessary uploads.

01Client-side Ingestion

Select & Ingest

Files are loaded as ArrayBuffers directly into client RAM. No upload happens for standard PDF & image workflows.

Step 1 of 3
02Zero Egress Pipeline

WASM & Canvas Compute

WASM workers, pdf-lib, and HTML5 Canvas compress, merge, or convert your documents using your device hardware.

Step 2 of 3
03Zero Persistent Retention

Direct Download & Purge

Save your processed document directly to your filesystem. Session storage and temporary buffers are immediately freed.

Step 3 of 3

We don't store without consent.

We don't track your files.

No email needed for core tools.

Core tools run 100% locally in your browser. Heavy compression uses ephemeral processing with immediate cleanup. Cloud vault sync requires an authenticated account.

Open source — verify it yourself in your browser's Network tab.·Inspect source on GitHub