Security

Every non-Slack integration is read-only — Foggy delivers findings, not actions. Credentials are encrypted at rest and never sent to LLM providers. Investigation data is never used to train models.

​

Read-only access

Foggy runs with read-only permissions for observability and infrastructure integrations — no agents, no sidecars, no writes to production. All non-Slack integrations are enforced as read-only at the connector level, regardless of the API token permissions you grant. The exception is Slack, where Foggy sends investigation results and alert notifications.

​

Credential encryption

All connector credentials (API tokens, URLs) are encrypted at rest using Fernet symmetric encryption:

• Credentials are encrypted the moment you save them
• Decrypted only when making API calls to your tools
• Never logged, cached, or exposed in the UI after initial entry
• Never sent to LLM providers — only query results are sent for analysis

​

Project isolation

All data is scoped to projects (workspaces). Users can only access projects they belong to. See Teams and access for invite and workspace-setup details.

​

Integration scopes

Foggy requests the narrowest scopes each integration supports. Setup details are in each integration’s page under Integrations.

​

Data handling

• No model training — Investigation data is never used to train models or shared across projects.
• Encryption in transit and at rest — Connector credentials use Fernet symmetric encryption.
• Credential isolation from LLMs — API tokens and connection strings are never sent to LLM providers. Only query results (metrics, logs, events) are sent for analysis.

​

Bring Your Own Model

Use your own LLM API keys to control which provider processes your data. Choose the model per-message via the model selector in the chat input.

​

LLM data flow

What data goes where: