What stays on the workstation
Argus is a desktop application. It stores its working data in the user’s application data directory, readable only by that operating system user and covered by whatever disk encryption and endpoint policy the workstation already has. The following are never transmitted by Argus, in any deployment mode:- CAD models, assemblies and drawings
- Simulation input and output files
- The local databases holding chat history and agent state
What leaves the workstation
Every outbound connection is listed below with what it carries. “Content” means the text of the conversation and the results of tool calls, which can include model parameters, script output, error messages and screenshots from the engineering application.
In the bring-your-own-key deployment, model requests go to the endpoint the customer configures and never touch Cosmon. The packaged application still makes the update, error-report and analytics connections above unless they are switched off or blocked at the network. A deployment with no Cosmon contact at all needs those connections disabled as well; see Deployment options and talk to Cosmon about an offline configuration.
What Cosmon stores, by plan
The Cosmon backend is plan-aware. Whether conversation content is ever written to Cosmon’s systems is decided server-side on every request, from the account’s plan, and cannot be changed by the end user.
On the Enterprise plan the result is that Cosmon holds no copy of any conversation. There is nothing server-side to export, share or subpoena, and nothing for Cosmon staff to read.
If an organization is on the Enterprise plan, its members are treated as Enterprise for this purpose regardless of any personal plan they hold.
Model providers
Cosmon does not train or fine-tune models. All models are third-party foundation models accessed by API under Cosmon’s provider agreements, and Cosmon does not use customer content to train anything. Provider-side retention is governed by those agreements; ask your Cosmon contact for the current terms that apply to your deployment. In BYOK mode the provider relationship, and its retention terms, are yours.Sharing and export
Argus has no share-link, publish or collaboration feature. Conversation content cannot be sent to another user or a third party through the product. The only export is user-initiated: a user can export a chat, including agent history, as a JSON file written to their own workstation through the operating system’s save dialog. That file is then subject to the workstation’s own data-loss-prevention policy like any other document.Encryption in transit
All connections from the desktop application and the browser to Cosmon use HTTPS. Cosmon’s public endpoints accept TLS 1.3 only, enforced at Cosmon’s edge in front of the load balancer; TLS 1.0, 1.1 and 1.2 handshakes are refused. Plain HTTP is redirected to HTTPS and HSTS is set for one year including subdomains. Connections from the backend to the database and to model providers are encrypted. Customers that inspect TLS on their network configure the workstation’s OS certificate store; see TLS inspection.Access on Cosmon’s side
- The production database has no public IP address and accepts encrypted connections only, from Cosmon’s private network.
- Backend services run under dedicated service accounts with per-service least-privilege grants. No service account holds a project-wide owner or editor role.
- Cosmon’s internal operations dashboard is reachable only over Cosmon’s private network, with device approval and named identities, and requires a verified
@cosmon.comstaff identity. It fails closed. - Administrative changes to infrastructure are recorded in cloud audit logs. Infrastructure is defined in Terraform and changed through reviewed pull requests.
- Application logs record user identifiers and routes, never passwords (Cosmon’s servers never receive one) and, on the Enterprise plan, never conversation content.
Retention and deletion
Deletion requests go to support@cosmon.com. Content deletion is performed per named account, never by domain sweep, so that the scope of a deletion is exactly what the customer approved.