Floom Cloud Terms

These terms apply to Floom Cloud, including the hosted web app, CLI authentication, MCP server, connected accounts, and hosted worker runtime. Self-hosted Floom deployments are operated by their deployer and are governed by the open-source license and that operator's own policies.

Your account and workspaces

You are responsible for the workspaces you create, the credentials and connections you add, and the workers or agents you run. Keep login sessions, API tokens, CLI tokens, and MCP client configs private. You may revoke tokens and connections from product settings.

Acceptable use

Do not use Floom Cloud to break the law, abuse third-party services, access data you do not have rights to use, send spam, evade platform limits, or violate the terms of model, sandbox, communication, or tool providers that Floom connects to.

Workers and outputs

Floom Cloud can create and run automations that read connected data, call tools, generate files, send messages, or schedule future work when you configure them to do so. You are responsible for reviewing worker behavior, approving sensitive actions, and deciding whether outputs are accurate or appropriate for your use case.

Costs and limits

Running workers and agents can consume model tokens, sandbox time, storage, and third-party provider quota. Floom may apply product limits, rate limits, spend controls, or safety pauses to protect the service and your workspace.

Service changes

Floom may change, suspend, or discontinue features as the product evolves. Preview, beta, and generated-worker features may be less stable than core product surfaces.

Liability

To the maximum extent permitted by law, Floom Cloud is provided without warranties and is not liable for indirect damages, lost data, provider charges, business interruption, or decisions made from worker output.

See also Floom Cloud Privacy.