Integrations
Everything Paperwell connects to lives on this machine
An integrations page usually means a wall of cloud logos. Every one of those is a copy of your document on somebody else's server, so this page is the other kind: the ways Paperwell plugs into the computer you are sitting at. Your file manager can open a PDF straight into it, your phone's share sheet can push one in, the save dialog can put the result back exactly where it came from — and none of that crosses a network.
Two of these need the app installed first. That is not a paywall or a sign-up: an operating system will not hand files to a browser tab, and installing is how a web app gets a place in the “Open with” menu. What leaves the device · Work offline
On this machine
Checking what this browser can do…
What will never be here
These are the integrations people ask for. Each one is refused for the same reason, and the reason is specific enough to check: the exact thing that would have to leave this device.
Google Drive, Dropbox, OneDrive, iCloud
To edit a file from Drive here, the file has to be copied out of Drive and back in. That copy is an upload and a download through somebody else's server, and it happens for every file, every time.
Send by email, or to a chat app
The file leaves for a mail server the moment you press send. Your own mail client can do this with the file you saved, after the work is done and where you can see it happening.
Zapier, Make, n8n cloud, and the rest
A hosted automation runner has to hold your document to act on it. Automations here do the same job in this tab — no account, no runner, and nothing waiting on a queue somewhere.
Cloud AI — OpenAI, Gemini, Claude and friends
The document's text is the request body. That is the one thing this app exists not to do, which is why the AI here is your browser's own model or a model downloaded to your machine — worse at writing, and honest about it.
Analytics, crash reporting, a newsletter pixel
Not a file, but still a beacon that says you were here and what you opened. The Content-Security-Policy that ships with every page would block one anyway; there is nothing to block.
The workaround is the same in every case and it is not much of a workaround: save the file, then use the app you were going to use. The difference is that you can see it happen.