Unlike traditional services, your files are never uploaded to, stored on, or passed through our servers. The transfer happens exclusively between your devices.
By removing the central server from the transfer process, we eliminate the single biggest point of vulnerability. There is no central database of files for hackers to target.
The connection is a pure peer-to-peer (P2P) tunnel. This is the most direct and private form of file transfer, ensuring only the intended recipient ever touches the data.
An ephemeral, 2-minute pairing code allows your devices to find each other via a minimalist signaling channel. This channel only exchanges the technical data needed to build the direct tunnel, then it gets out of the way. It never sees your files.
The direct WebRTC connection is fortified with mandatory, always-on, end-to-end encryption (DTLS). This means no one can intercept and read your files in transit—not us, not your ISP, not anyone on your Wi-Fi network.
We use a CRC checksum to verify that the file received is a bit-perfect copy of the file sent. This protects against data corruption and tampering during the transfer, guaranteeing the integrity of your data.
We do not use any tracking or session cookies. Your usage is completely anonymous and cannot be linked to other web activity.
We never ask for an email, username, or any personal information. When you close the tab, your temporary session vanishes.
Since files are never sent to our servers, we have no record of what you sent, to whom, or when. We simply can't.
When a file is received, it is not fully loaded into your computer's memory or stored in a recoverable browser cache. Our system acts as a smart pipe, catching the data chunks and streaming them directly into a file in your "Downloads" folder. This minimizes the data footprint on your device and prevents forensic recovery of the file from temporary browser storage.
| Feature | iCanSend (Peer-to-Peer) | Traditional Services |
|---|---|---|
| File Path | Device ➡️ Device | Device ➡️ Server ➡️ Device |
| Server Data Access | ✓ Impossible | ✗ Possible (or likely) |
| End-to-End Encryption | ✓ Mandatory & Unbreakable | ✗ Often optional or "at-rest" only |
| User Identity | ✓ Anonymous (no accounts) | ✗ Required (email, login) |
| Tracking Cookies | ✓ None | ✗ Yes (ads, analytics) |
| Server-side File History | ✓ None | ✗ Yes (stored in account) |