For IT and security teams
Enough detail to make an informed decision.
Transfer in Seconds is a browser-based, live file handoff. It requires no installation or account and does not place files in Transfer in Seconds cloud storage.
Data flow
The interface is delivered over HTTPS from Vercel.
Peer IDs and WebRTC connection details are exchanged through PeerJS.
The file payload travels over an encrypted RTCDataChannel, direct when the network allows it.
The receiver checks the SHA-256 fingerprint before reporting success.
Network allowlist
The current client uses the following endpoints. Direct WebRTC also needs the organisation's firewall and browser policy to permit RTCDataChannel connectivity.
| Endpoint | Protocol | Purpose |
|---|---|---|
| transferinseconds.com and www.transferinseconds.com | TCP 443 | Website and transfer interface |
| 0.peerjs.com | TCP 443 (HTTPS/WSS) | Connection signalling; no file payload |
| stun.l.google.com | UDP 19302 | Public-address discovery for direct WebRTC |
| eu-0.turn.peerjs.com and us-0.turn.peerjs.com | UDP/TCP 3478 | Encrypted relay fallback when direct connectivity fails |
Controls and limitations
- The sender must keep the browser page open until completion.
- The possession of a transfer link grants the ability to attempt one connection; compare the safety code for higher-assurance handoffs.
- File contents are not available to our server for antivirus, DLP, eDiscovery, retention, or audit inspection.
- Corporate proxies, TLS inspection, blocked WebSockets, or restrictive UDP/WebRTC policies can prevent the connection.
- Chrome and Edge can stream large incoming files directly to a user-selected disk location. Other browsers may need to buffer before saving.
Assessment contact
For a security questionnaire, scoped pilot, or current endpoint list, contact hello@transferinseconds.com. See the full security explanation and privacy notice.