Local-first: why our tools never upload your files

October 16, 2026 · Apal Notes

Most online tools work the same way: you upload your file to somebody else's server, their software processes it, and you download the result. It feels convenient — until you think about what actually happened. A contract, a scanned ID, a medical report, an unfinished draft crossed the internet, sat in someone else's storage, and you have no idea for how long.

Every Apal tool takes the opposite approach: your files never leave your device.

How is that possible?

The heavy lifting that used to require a server now runs in the browser. Modern engines like pdf.js and pdf-lib, compiled to WebAssembly, can parse, modify and render complex documents at near-native speed. The "server" is your own laptop. When you compress a PDF with our tool, the work happens on your CPU, in your RAM, and the output is written straight back to your disk.

What this buys you

• Privacy by physics, not by promise. We don't need a privacy policy that says "trust us" — there is simply no upload step to trust. Unplug your network cable and the tools still work.
• Speed. No upload wait, no queue, no download wait. A 50 MB PDF doesn't travel over your connection at all.
• No artificial limits. Servers cost money, which is why "free" tools cap you at two tasks a day. Our marginal cost per task is zero, so there is nothing to cap.
• No accounts. Nothing to track means nothing to log in for.

The trade-off

Local-first is honest about one thing: your browser does the work, so a very old device may feel slower on huge files. That is a trade we make deliberately. Convenience that costs you your privacy isn't convenience — it's a subscription paid in data.

That's the Apal promise, and it applies to everything we will ever ship: a pal doesn't peek at your files.