Privacy and Data Handling

Connections and relay providers

Online discovery and room signaling use internet services. Files, text and clipboard prefer direct WebRTC. TURN and MQTT content relay require explicit permission in each tab; room and share fallback also require the other device to approve. Direct only disables content relay, while online discovery and signaling remain internet-dependent. Relay permission resets on reload and can be disabled. Data already sent cannot be recalled. A DIRECT badge describes the selected connection route and does not prove a shared Wi-Fi network.

WebRTC data channels use browser-negotiated transport encryption. A public room does not encrypt broker payloads against the broker. Set a room password to encrypt room payloads with AES-GCM. Share links use a separate secret stored in the link fragment; anyone with that link can attempt to receive its file. Third-party service operators may process connection metadata, IP addresses and unprotected public-room payloads.

Storage on your device

Room history and message metadata are saved in browser IndexedDB. Browser settings and visited room information use local storage. Room passwords are saved in the current tab session. Live retry source files and temporary blob URLs are not persisted as room history. History is local storage, not encryption at rest.

Optional temporary file recovery is off by default. If enabled in Preferences, incomplete received files are saved unencrypted in local IndexedDB, limited to 256 MiB and four transfers. Verified checkpoints expire after 10 minutes; if the app is closed, expired records are removed when it next runs. Completed or rejected transfers remove their recovery records. Disable and clear temporary recovery data in Preferences to remove these records immediately. After a refresh, the sender must select the original file again. With temporary recovery enabled, disk-received files up to 256 MiB can resume after choosing a destination again. Share receivers can resume the same link; the sender must keep the source page open and choose Try Again.

Downloaded files or files saved to a chosen directory remain on your device. System-share handoff files temporarily use browser CacheStorage until they are read; application resources are cached for offline use. Clearing the stream removes that room's message history; it does not delete files already saved to disk. Browser site-data controls can clear settings, history and cached handoffs.

Clipboard and camera permissions

Clipboard synchronization requires explicit enablement and browser permission. Focus, background and lock-screen restrictions apply. Offline QR scanning uses camera input to decode connection data; scan only a device you trust. Stop or close the scanner to release its camera stream.

Analytics and advertising

The site loads Google Analytics, Microsoft Clarity and Google AdSense scripts. These third-party scripts can process page and interaction information, use their own storage, and have access within the page. Transfer encryption does not remove the need to trust software running in either browser. Do not treat this site as a zero-tracking environment or a guarantee of zero third-party retention.

Application usage events report coarse transfer type, size bracket, context, outcome and fixed diagnostic labels, not file names, message contents, room codes or share secrets. Application event locations omit room/share fragments and non-campaign query parameters; standard bounded UTM campaign tags are retained for attribution. Observed entry attribution reports only fixed channel/source labels and whether evidence came from a campaign tag or referrer; unknown sources remain unknown. These labels are retained in tab-session storage for up to 30 minutes of inactivity. Reported referrers omit paths, queries and fragments. Versions 2 and 3 use bounded SHA-256 fingerprints in tab-session storage to deduplicate completion events for up to 24 hours; fingerprints are not sent to analytics. Preview/LAN hosts and detected automated browsers do not initialize site telemetry.

To exclude this browser from future usage statistics, open Preferences and enable Exclude this browser from usage statistics. Save and reopen the tab after transfers finish to prevent previously loaded third-party scripts from running in the next page. This does not delete earlier provider data. The preference is saved only in this browser.

Questions

For questions about this application's data handling, use the contact page. Provider retention, installed browser extensions and device-level backups are outside the application's control.