Terms of use

By using Floe, you agree not to:

• ✕Transfer illegal content (e.g., malware, pirated software, child exploitation material).
• ✕Use the service for phishing or social engineering attacks.
• ✕Use a request link to ask for files or documents under false pretenses, or to impersonate a person or an organization.
• ✕Disrupt, overload, or abuse the signaling server or the relay service behind floe.one.

The code itself is open source: reading it, running your own copy, and reporting what you find are welcome. See Copyright & license below and our security policy.

Since Floe is a peer-to-peer service, you are solely responsible for the content you send. We do not (and cannot) moderate file contents, and Floe does not scan files for malware. You agree to indemnify the developers of Floe against any legal claims arising from your use of the service, that is, to cover the cost if your use of Floe leads to a legal claim against them.

If you make a request link, you are responsible for who you send it to and for what you ask them to send. Sending files through someone else's request link is sending, and the paragraph above applies to it in full.

We can turn request links off for everyone at any time, as the privacy policy describes.

The source code for Floe is available under the MIT License. You are free to inspect, modify, and host your own version of this software, subject to the terms of the license.

When your connection uses the TURN relay, transfers are limited to 2 GB per session, which for a request link means per drop. Excessive or automated use of the relay may result in rate limiting or restrictions on access to the signaling and relay infrastructure. These limits exist to keep Floe free for all users.

Questions about these terms, bug reports, and abuse reports go to our public issue tracker: github.com/jannskiee/floe/issues. Security vulnerabilities, and abuse reports that include personal details or copies of the content, go privately instead: use the vulnerability report form or the email address in our security policy rather than a public issue.

To report a request link, use "Report this link" at the bottom of its page, or write to paredesjancarlo99@gmail.com with the part of the link before the #. Never post a whole request link in a public issue: the part after the # lets anyone use it.

Because transfers are peer-to-peer, we cannot inspect or remove content sent between users, and our signaling server keeps no record of who took part in a transfer once its room has closed. Automatic per-address rate limits and a few fixed caps, such as the 2 GB relay limit, are the only restrictions the service applies on its own.