Three ways to move a file.
One simple platform.

Use direct transfer when the other person is online right now — the file goes straight to them and nothing is stored. Use a cloud link when they will open it later, or when several people need the same file. If you need someone to send a file to you instead, create a file request.

For a direct transfer, yes — with nothing stored on a server, the file has nowhere to wait. Cloud links and file requests are the asynchronous options: the recipient can open them whenever they like, up to the expiry you set.

No. All three modes run entirely in a standard browser on desktop and mobile — no app, no extension, no cable.

Direct transfers handle up to 1 GB per file. Cloud uploads have their own per-file limit, and the upload page tells you if a file exceeds it. File requests use a per-request cap that you set when creating the request.

You pick the timer when you create the link — 1 hour, 24 hours, 7 days, or 30 days — and it defaults to 7 days. When the timer runs out the file is permanently deleted from storage.

The file itself is never stored, on any path — though the surrounding record (size, type, timings, both IP addresses) is kept for the periods in the privacy policy. On a direct connection the file data never reaches our servers at all. Two things route it through us instead: a firewall or carrier NAT that blocks a peer connection, and a file small enough that negotiating one would take longer than sending it. In both cases the chunks pass through as ciphertext we hold no key for — passed through, not retained.