How it works

P2P signaling introduces the devices. The file moves directly.

The receiver app keeps a trusted device ready in the background. P2P signaling only introduces the sender and receiver; the file stream then moves directly between the two online endpoints. P2P file contents are not stored on our servers.

Animated P2P transfer flow with a receiver app A sender invites an online receiver through signaling, then sends the file directly to the receiver app, which saves it into a local folder. Sender Browser or P2P app Signaling Invite and connect Receiver app Installed and online Local folder Saved on device Secure link Fallback if offline 1. invitation 2. direct encrypted data path 3. save
1
Invite the receiver

The sender selects a person or receiver device that is online in the P2P workspace.

2
Use signaling to meet

The signaling service exchanges connection details, but it does not become the file store.

3
Transfer directly

When both sides are available, WebRTC moves the file from sender to receiver app.

4
Save locally

The receiver app writes the incoming file into the chosen folder and stays ready for the next transfer.

1

Pick link delivery or P2P

Start in the main app for tracked download links, or open the P2P app for a live peer-to-peer session.

2

Choose recipients or peers

Select one recipient or a whole group, or connect to an online peer or receiver device.

3

Follow the transfer

Track upload status, download availability, P2P progress, and receiver-side save status.

P2P transfer path

For P2P sessions, signaling creates the meeting point. The actual file stream goes from the sender device to the receiver device, without server-side file storage.

Secure-link deletion path

For standard SENDANYWAIR links, the file is temporarily available for download. As soon as the expected download is complete, it is deleted from our storage; otherwise it expires according to the plan retention period.