GroupChatOnGroupChatOnSend

Security: how Send keeps your files private

Send was built so that the people running it can't see what you send, even if they wanted to. Here is exactly what protects you, and the limits you should know.

What protects you

ProtectionWhat it means for you
End-to-end encryption (WebRTC DTLS)Files and notes are encrypted on your device and decrypted only on the other device. Browsers make this compulsory.
No upload, no storageThere is no server that holds your file. Nothing can leak from a server that never had it.
One-time codesCodes are 8 random characters from a 32-character alphabet (over a trillion combinations), made by your browser's secure random generator. After pairing, both devices leave the pairing service and the code dies.
Accept before anything arrivesThe receiver sees the name, type and size of each file and must tap Accept. Nothing downloads or opens by itself.
Safety codeBoth screens show four pictures computed from the encryption keys of this connection. Same pictures on both = nobody in the middle.
Risky-file warningPrograms and scripts (.exe, .msi, .apk, .bat, .ps1, .js, macro documents and more) get a clear warning before you accept.
Locked-down pageThe transfer page may only run its own code plus two pinned libraries (PeerJS and a QR-code drawer, each checked against a fixed fingerprint so a changed copy is refused). It shows no ads and loads no trackers.
Code kept out of addresses sent to serversPairing links put the code after a # sign. Browsers never send that part to any website.

Honest limits

Good habits

  1. Read the code out loud or scan the QR code rather than posting it publicly.
  2. For something sensitive, compare the safety code on both screens before sending.
  3. Tap Disconnect when you are done.

Found a security problem? Please tell us through the contact page.