Security and Privacy
Security posture and legal policy links for fluos users.
Security Model (User View)
fluos runs preview and generation in isolated sandbox environments. This reduces cross-project execution risk and keeps runtime boundaries cleaner.
Access Control
- Authentication is handled through Clerk-based flows.
- Project/workspace access is permission-scoped.
- Invite and membership state control what a user can access.
Data and File Handling
Chat content, project metadata, and export records are handled through authenticated backend paths with access checks.
Legal Policies
Reporting Concerns
For security concerns, use the official fluos support/contact channel listed on the product site.
Policy detail
This page is an operational summary for users. Legal pages above are the source of truth.