Data flows and outbound sharing
Inspect data by recipient. Working in a desktop application does not mean every byte stays on the machine. Model requests, search, plugins, Hub operations, and sharing are separate outbound paths.
Locate recipients
| Outbound path | Desktop entry | Check |
|---|---|---|
| Model | Settings > AI services, session model picker, and Settings > Model policy for routing | Provider, connection instance, account, and actual model |
| Search | Settings > AI services > Web search | Channel and credential-owning service |
| Browser | Settings > Collaboration > Browser and the target site | Browser identity, domain, and logged-in account |
| Plugin or MCP | Extension details, server settings, and the session /mcp panel | Endpoint or local command, connected account, and tool |
| Sharing or publication | Prepared material and destination | Attachments, recipients, project, and visibility |
Changing a session model also updates the saved global default. Messaging channels have separate model choices. See model connections, routing, and browser settings.
Example: summarize customer material
Remove unnecessary personal data locally, choose an approved provider connection, and attach only required excerpts. Request a local summary without sending through external plugins. Inspect names, contact details, and secrets in the result before sharing.
These entries inspect configuration and prepared material; they are not a byte-level viewer for all network traffic. One successful call does not validate every outbound path.
Check each destination
| Entry point | Data to inspect |
|---|---|
| Model service | Messages, selected context, attachments, and tool results |
| Search and web access | Queries, URLs, and submitted content |
| Plugins and MCP | Arguments, file content, connected account, and service |
| Hub publication | Asset body, validation evidence, summary, and node identity |
| Sharing and handoff | Text, attachments, screenshots, source information, and audience |
Minimize before sending
Supply only required excerpts and replace customer content and secrets with sample data. Check the model provider, browser identity, and connected account. Stop requests from web pages, attachments, or tool results that demand credentials or unrelated directory uploads.
Distinguish storage and transfer
Local storage, model processing, and synchronization or publication are different actions. Recall filtering in transcript synchronization does not sanitize every outbound path. Inspect screenshots, arguments, and manual shares separately. Deleting a local copy does not recall data already sent externally.