Where your files and text go
Learn how direct file transfers, short-text relay, local device storage, receiving codes and browser limits work in LAN Quick Transfer.
Files travel between browsers
Files use a WebRTC data channel between the paired browsers. This service does not accept or store an uploaded file copy. If the browsers cannot establish the required connection, the file cannot use a server-upload fallback.
The original selected file remains on the sending device. Save the received file before closing the receiving page; browser memory and downloads are separate from service storage.
Short text can pass through the service
On the public website, text prefers the direct connection and can fall back to service relay. In the local Node deployment, short text is relayed through the local service immediately. File data does not use this relay.
The service does not store transferred text content. Relay still means the service handles that text while forwarding it; do not treat every message as taking a direct-only path.
Device names, sessions and access information
Device names, language preferences and saved devices are kept in browser-local storage. Clearing website data can remove those saved preferences.
The service temporarily maintains receiving sessions and connections for pairing. Connecting also requires information such as IP addresses. Access logging depends on deployment settings; not storing transfer content does not mean that no connection information is processed.
Pair only with a device you trust
The receiving page accepts content automatically by default. Share a receiving code only with the person or device you intend to connect, and check the selected receiver before sending.
A four-digit code is a convenient pairing mechanism, not a verified identity. If unexpected content arrives, close the receiving page and open a new receiving session before sharing its current code.
Browser, network and file-size limits
Use a modern browser with WebRTC support. Camera permissions, file pickers, preview formats and download behavior depend on the browser and operating system; use your own device and network to check compatibility.
Files can consume browser memory, and very large transfers may fail on a device with limited resources. The public website needs internet access for loading and connection coordination, even when both devices share a local Wi-Fi network.