Security and Privacy

Isolation

Every build and preview runs in an isolated sandbox that is created for the run and torn down afterwards. Nothing from one project's runtime is reachable from another.

Access control

• Sign-in is handled by a dedicated authentication provider — fluos never stores your password, and there is no password to store.
• Projects, chats, library assets, and exports are scoped to a workspace, and every request is permission-checked on the server.
• Membership and role determine what you can do. Removing a member revokes their access immediately.
• Export download links follow the same checks, so they are not usable outside the workspace.

Your content

Chat messages, compositions, uploads, and exports are stored so the product can work — history, version restore, and a shared library all depend on it.

Training and product improvement is opt-in. The Help improve fluos toggle in Account settings controls whether your prompts and generated videos may be reviewed to improve the product. It is off unless you turn it on, and you can change it at any time. Your data is never sold or published.

Connectors

Connectors authorize through the provider's own OAuth flow. fluos receives a scoped, read-only token and never sees your credentials, never writes back to your tools, and loses access the moment you disconnect. Connections are per workspace.

Deleting things

• Delete a project to remove its chats, versions, and exports.
• Delete an asset from the library to remove the file and its derived proxy, poster, and search index. Assets attached to saved chat messages are protected from deletion so your history does not break.
• Delete your account to trigger a full cascade removal of your data.

Legal

• Privacy Policy
• Terms of Service
• Cookie Policy

Reporting a concern

Use the support contact on the product site, or Product feedback in the account menu.