Local application data
Conversations, canvas state, request logs, and provider settings stay in the current browser profile.
Flowisall is preparing the page and its connected content.
Flowisall keeps conversation structure and local application data visible. Provider-side retention and model traffic still follow the provider and endpoint you configure.
Conversations, canvas state, request logs, and provider settings stay in the current browser profile.
Compatible local models can run without sending their model traffic to a hosted provider.
Messages, branches, references, summaries, and model output remain inspectable on the canvas.
Local backups include conversation data and request logs while excluding API credentials.
Use deployment-supported credentials and revoke them through the system that issued them.
Project exploration, file edits, and tool execution require Plus Agent in the desktop app.
Confirm retention, encryption, access, and audit settings with the administrator of your actual environment.
Compliance badges are shown only after they can be verified for the production service.
Please include reproduction details and avoid placing secrets in the initial message.