The strongest privacy guarantee is the absence of a server in the middle. AgentiqFlow runs entirely on your machine, holds your keys in a sealed vault, and only touches the network when you call a model provider. Here's exactly how that's enforced.
The sidecar binds to 127.0.0.1 — loopback only. The dashboard runs in your browser at localhost:8858. It is not reachable from your LAN unless you deliberately set HOST=0.0.0.0, and LAN exposure is an explicit opt-in, not the default.
Provider keys and OAuth tokens are sealed with a passphrase you set — AES-GCM encryption, PBKDF2 at 200k iterations. Stored on your disk under ~/.agentiqflow. Lock and unlock from the UI. Secrets never leak to logs.
Every layer runs on your machine. Outbound network traffic happens only when you call a model provider — and you choose which calls leave the box. There is no telemetry and no background analytics.
Updates are verified against a minisign signature over the release manifest, plus a sha256 integrity check on every artifact. A build that doesn't match its signature is rejected before it's applied.
HTTP calls made from workflows and integrations pass through an SSRF guard that blocks loopback, private, and link-local targets — including the cloud-metadata address at 169.254.169.254 — so a crafted URL can't be pointed at your internal network.
You bring your own provider keys. The runtime calls the provider directly, at the provider's price — nothing is relayed through our servers and there is no token markup. Prefer no third party at all? Point an agent at a local Ollama model.
Want the full picture of what runs where? Read the self-host guide or see how the layers fit together on the capabilities overview.