Back to Home

Privacy Policy

Last updated: May 2026

The Short Version

Floe is a Peer-to-Peer (P2P)file transfer service. This means your files stream directly from the sender's device to the receiver's device whenever possible.

We do not store, view, or process your files. In direct connections, files never touch our servers. In relay connections, encrypted file data passes through our TURN server in transit but is never stored or inspected. We do not operate a database.

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.
  • 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. We also use Sentry for error monitoring and Umami for privacy-respecting usage analytics. Please refer to their respective privacy policies 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. When an error occurs, 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 your browser session may be captured when an error occurs. Text inputs are masked. 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.