Security depends on the application, its infrastructure, the connected providers and the permissions of the people using them. Review all four when preparing a deployment.

​
Credentials

The upstream core encrypts stored connection credentials using the deployment’s encryption key and masks sensitive values in supported log paths. Operators must protect the key, database, backups and access to the running server. Do not paste provider credentials into ordinary mission fields, notes, prompts or screenshots. Those fields can become part of exports, model input or debugging records. Use the supported connection form.

​
External data flow

Each configured action determines which external app or service receives data. A self-hosted platform may still send documents to OCR or AI providers and messages to email or collaboration services. Check the destinations, credential scope and provider retention policies for the actual workflow. A deployment label does not establish where every action processes data.

​
Runs and evidence

Runs helps explain execution, but input truncation, output limits and cleanup constrain it. Preserve business decisions and documents in the intended records system. See retention and limits. Administrative audit logs and external secret-manager integrations are optional upstream paid controls. This guide does not claim those controls are present.

​
Operator responsibilities

Use HTTPS, protect management endpoints, apply appropriate server/network access controls, maintain recoverable backups, and review upgrades. Record the actual authentication and user-access design used by the deployment. Report a suspected exposure through the support/security contact supplied for your deployment. Include enough detail to locate the issue without sending live credentials or private customer records through an unauthorized channel.