"Can’t look", not "won’t look"
A privacy policy is a promise a company can change, breach, or be compelled to break. Pairchute doesn’t rely on one. There is no server that ever holds your file, so there is nothing for anyone — including us — to read, log, hand over, or leak. The privacy comes from the architecture, not from a pledge.
End-to-end encrypted by default
The connection is end-to-end encrypted with keys generated on your two devices, and the transport itself (WebRTC/DTLS) is encrypted on the wire. Both screens show the same 6-digit safety code so you can confirm you’re connected to the right person and not someone in the middle. Every block is hash-verified and the whole file is checked against a root hash before it counts as received.
The only outside contact is one STUN lookup
The page loads its own static files and makes exactly one external request: a STUN lookup that reports your network’s public address so the two browsers can find each other. It never sees your file. No analytics, no cookies, no account, no trackers — verifiable in your browser’s network tab. Keep the invite link private, since it carries the connection keys, and nothing else about the transfer ever leaves the two computers.
Nothing left behind
When the transfer finishes and you close the tab, the only trace is the file you saved. There is no account, no stored peer list, no transfer history, and no cookies. The next time you open Pairchute it remembers nothing except this device’s own keypair, which never leaves your machine and exists only to authenticate the encrypted handshake.
Send a file now
Scroll up and hit Create invite — you get a link to send the other person. They click it, send one reply back, and the direct encrypted pipe opens. Nothing is uploaded; nothing is stored.
Related
See also: sending without uploading · a private WeTransfer alternative — and the Pairchute home page.