Privacy Policy

1. How the Transfer Works

When you send a file, we use WebRTC to establish a connection between you and the recipient. Our signaling server introduces the two devices and then steps aside. In most cases, data flows directly between browsers. When a direct path is not available, our TURN relay server bridges the connection. Even through the relay, files remain encrypted and are never stored.

2. Information We Collect

• Files: We do NOT collect or store any files.
• Metadata: We temporarily process filenames and sizes during the signaling phase to display them to the receiver. This data is not stored permanently.
• Aggregate Transfer Total: When a transfer completes, the receiving side reports only the number of bytes it received. We add this to one shared, all-time counter of total bytes transferred, shown on our homepage. The sender never reports. We do not store file names, file contents, individual transfer records, or any link between this number and you. You can opt out of this report: uncheck "Contribute to global stats" on the receiver view in the browser, or use --no-report (or set FLOE_NO_STATS=1) when using the CLI.
• IP Addresses: Like all web servers, our hosting provider may log connection request IP addresses for security and abuse prevention. We do not link this to your identity.

3. Third-Party Services

Floe uses third-party infrastructure providers for hosting and network relay services. The web app is hosted on Vercel. For usage analytics we use only Umami, which is cookieless and does not track you across sites, and we optionally use Sentry for error monitoring. The link you share carries its room id in the URL fragment (the part after the#), which browsers never send to any server or analytics provider, so the transfer secret stays between you and the recipient. Please refer to each provider's privacy policy regarding data handling.

4. Relay Server

When a direct connection cannot be established, file data is routed through our TURN relay server (turn.floe.one). This server processes encrypted data packets in transit and does not store, decrypt, or inspect any file contents. Relay sessions are limited to 2 GB per session. Connection metadata (timestamps, IP addresses) may be logged by the hosting provider for security purposes.

5. Error Monitoring & Session Replay

Floe uses Sentry to monitor application errors and performance. Sentry may capture:

• Error stack traces and browser metadata (browser version, OS, device type)
• Connection type (direct or relay) and transfer progress at time of error
• Session Replay: An anonymized, video-like recording of a small sample of browser sessions, plus any session where an error occurs. All on-screen text and media are masked, so file names and file contents are never captured.

Sentry does not capture file names, file contents, or any personally identifiable information. Session recordings are used solely for debugging technical issues. Sentry Privacy Policy.

6. Usage Analytics

Floe uses Umami, a privacy-focused analytics tool, to understand how the service is used. Umami collects:

• Aggregate transfer metrics: number of files and total bytes transferred per session
• Connection type (direct or relay) and whether a transfer succeeded or failed
• Standard page view data: pages visited, browser type, country (not city)

Umami does not use cookies, does not collect personally identifiable information, and does not track individuals across sessions or websites. File names and file contents are never recorded. Umami Privacy Policy.