Privacy
No file storage.
Transfer in Seconds provides a live route between two open browsers. This page explains the limited technical data needed to establish and, when necessary, relay that connection.
Files and file names
The selected file stays in the sender's browser until the recipient requests it. The service first tries an encrypted direct WebRTC connection. If the networks cannot establish that route, encrypted WebSocket traffic is relayed temporarily through our Cloudflare-hosted connection service. Neither route stores the file contents or file name.
Closing or resetting the sender page ends availability. The recipient must keep their page open until the transfer is complete.
Connection metadata
Vercel hosts the website and may process standard request information such as IP address, browser details, timestamps, and requested pages for security and service operation.
Our Cloudflare-hosted connection service and the Cloudflare and Google STUN services process temporary technical identifiers and network information needed to connect two browsers. When the direct route fails, Cloudflare also processes the encrypted-in-transit file blocks solely to relay them to the open recipient. The blocks are not retained.
Privacy-focused analytics
We use Vercel Web Analytics to understand aggregate traffic such as page views, referrers, device types, and countries. It does not use third-party cookies and Vercel describes its analytics data points as anonymous and aggregated.
Unique transfer codes in receiver URLs are replaced with the generic path /t/[code] before an analytics page view is sent.
Your choices and contact
You can stop a transfer by closing the sender page. For privacy questions, contact hello@transferinseconds.com.
Last updated: September 4, 2026.