Every tool on this site — signing, OCR, QR codes — makes a specific promise: your file never leaves your device. Here’s what that actually means in practice, and why it’s worth caring about.
What “processed locally” actually means
Most online document tools work the same way: you upload your file, it travels to their server, gets processed there, and the result is sent back to you. Somewhere in that round trip, your document exists on infrastructure you have no control over — even if it’s deleted five minutes later, it was there.
Our tools skip that step entirely. The PDF you choose, the signature you draw, the text OCR recognises, the QR code you generate — all of it is built and processed by code running inside your own browser, on your own device. There’s no upload button that sends your file anywhere, because there’s no server-side step that needs it.
Why that matters for the documents people actually sign
The documents people run through tools like this aren’t usually random test files — they’re contracts, ID copies, medical forms, tenancy agreements, things with a real person’s name, address and signature on them. The fewer places that information passes through, the fewer places it can leak from, get logged by accident, or sit around longer than intended.
What we do collect
To be clear about the boundary: like virtually any website, our server logs basic technical data when you visit — things like your IP address and the page requested — needed to keep the site running and secure. That’s separate from your documents, which we simply never receive. The full details are in our privacy policy.
You can put this to the test yourself: open your browser’s network tab while using any of our tools, and you’ll see your file never gets sent anywhere.