Terms of Service

Last updated: 3 August 2026. Versión en español.

These terms govern the use of Fluyo: the editor at fluyo.space, the MCP server at mcp.fluyo.space and the code published in the project's repositories. By using any of the three, you accept what follows.

1. What this is and who maintains it

Fluyo is a free software project maintained by itsnect (Claudio Jiménez Flores), domiciled in Chile. It is not an incorporated company, it sells nothing and it has no customers.

The service is offered free of charge and as is, without consideration of any kind. There is no paid plan, no premium tier, and no intention of introducing either as a condition for continuing to use what is free today.

2. Software licence

The code is published under the MIT licence. That entitles you, without asking permission or paying anything, to use, copy, modify, merge, publish, distribute, sublicense and sell it, including for commercial purposes, provided you keep the copyright notice and the licence text.

• Editor: licence of the fluyo repository
• MCP server: fluyo-mcp repository

Should these terms contradict the MIT licence with respect to the code, the MIT licence prevails. These terms govern the use of the hosted services; they do not restrict the rights the licence grants you over the software.

3. No account required

There is no registration, no email, no password and no identification of any kind. Consequently there is no account to suspend, no credentials to protect, and no obligation on your part to keep anything secure.

4. Your content is yours

The diagrams you create are entirely yours. This project claims no ownership, no licence of use and no rights over them.

In the editor, your diagrams never leave your browser. If you use the remote MCP server, the document does travel to it so that it can be processed, is handled in memory and is discarded without being stored. The detail is in the privacy policy.

You are responsible for your own backups. Autosave uses your browser's local storage, which can be emptied by clearing site data, by using private browsing or by switching devices. Keep your .fluyo.json files somewhere you can recover them from.

5. Acceptable use

The MCP server at mcp.fluyo.space is a shared, open and unauthenticated resource sustained by one person. These rules exist so that it keeps working for everyone.

Not permitted:

• Circumventing or attempting to circumvent the service limits — the maximum requests per minute, the request size or the response size — including rotating IP addresses or forging headers to that end.
• Carrying out denial-of-service attacks, load testing or high-volume automated campaigns against the public endpoint.
• Seeking unauthorised access to the infrastructure, or interfering with its operation or with that of other users.
• Using the service for unlawful activities, or to produce material that infringes third-party rights or that is defamatory or harmful.
• Presenting the service as your own, or implying endorsement, affiliation or sponsorship by this project where none exists.

Permitted, and welcome: using it for professional and commercial work, integrating it into your own tools, forking it, and hosting your own instance. If you need high volume or availability guarantees, the right answer is not to push the public endpoint: deploy your own instance — the code and the instructions are published — or run the server locally over stdio, which has no limits at all.

6. Service availability

There is no service level agreement, no availability commitment and no response time commitment. The service may be modified, interrupted or withdrawn at any time and without notice, including the usage limits, which may be adjusted according to real load.

Access may be restricted or blocked from addresses that breach section 5, without prior notice. As there are no accounts, this is a technical measure on traffic, not a sanction on a person.

The counterpart is concrete and worth more than any promise: the entire project is MIT. If this hosting disappeared tomorrow, the code is still yours and you can deploy it yourself. Nothing you build with Fluyo depends on this service continuing to exist — .fluyo.json files are your files, on your disk, in an open and documented format.

7. Third-party software

The editor loads the gif.js library from a public CDN, and the MCP server uses the official Model Context Protocol SDK and its dependencies. Each is governed by its own licence. This project neither controls those components nor answers for them.

8. No warranties

In accordance with the MIT licence, and to the fullest extent permitted by applicable law:

THE SOFTWARE AND THE SERVICES ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

In practical terms: there is no guarantee that the service will be available, that it will be free of errors, that results will be correct, that a diagram will export the way you expect, or that content generated with the help of an AI assistant will be accurate. Always review whatever a model produces before using it for anything that matters.

9. Limitation of liability

To the fullest extent permitted by applicable law, the authors and copyright holders shall not be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from or in connection with the software, the services or their use.

This expressly includes loss of data, loss of unsaved diagrams, service interruption, loss of profits and indirect or consequential damages.

Nothing in these terms excludes or limits liability that applicable law does not permit to be excluded or limited. If you are a consumer, you retain the non-waivable rights granted to you by the consumer protection rules of your jurisdiction.

10. Indemnity

You agree to hold the project's authors harmless against third-party claims arising from your use of the service in breach of these terms or of applicable law.

11. Changes to these terms

These terms may be updated. The date in the header indicates the latest version, and the entire change history is public in the repository, commit by commit. Continuing to use the service after an update constitutes acceptance of it.

12. Governing law and jurisdiction

These terms are governed by the laws of the Republic of Chile. Any dispute shall be submitted to the ordinary courts of justice of Santiago de Chile, without prejudice to the right of anyone qualifying as a consumer to bring proceedings before the courts of their own domicile where the applicable rules so permit.

If any clause of these terms is declared invalid or unenforceable, the remainder shall stay in force and that clause shall be construed as closely as possible to its original intent.

13. Contact

For any question about these terms: nectdnb@gmail.com, or through the support page.

In case of discrepancy between translations, the Spanish version prevails.