helm get manifest pipecat -n pipecat-system. The sections below describe what each operation can return and how to turn each optional channel off.
Information you submit to Pipecat Cloud, such as deployment configuration or values sent in a managed-secret write, reaches the control plane when you submit it. Log lines returned by an enabled log query also pass through the API and can contain session content or secrets if your agents log them. A restriction on the reference and status routes does not apply to those other inputs.
Always: session records and region health
Sent by the region as sessions run, and the basis of everything you see in the dashboard:- Session records — session ID, agent and deployment, start and end times, outcome, and per-session CPU and memory samples. No session content.
- Deployment state — whether each deployment is ready, and failure verdicts (as category codes, not free text) when an agent cannot be deployed.
- Region health — connected region agents, the platform version and capabilities each one runs, and certificate expiry.
region-agent.telemetry.enabled: false) makes sessions invisible to Pipecat Cloud — the sessions list, metrics, and billing records all stop — so it is not recommended.
By default, on request: platform diagnostics
The support bundle is a read-only snapshot Daily support can pull through the region’s connection when you ask for help. Its access is exactly two namespaced roles:
It does not read agent pod logs, the contents of any Secret, environment variable values, or ConfigMap contents. Every pull is recorded on the region’s event feed.
Disable it with
region-agent.supportBundle.enabled: false, which removes both the capability and the roles.
Only when you enable it: agent logs
With the log store enabled, agent log lines are stored in your region and read only when a member of your organization queries them through the CLI, dashboard, or API. Each query returns the lines that match its filters and nothing else; no log data is collected or stored by Pipecat Cloud, and Daily does not pull agent logs on its own. Log collection is off by default.Sealed Storage and Regional Keys
For Daily-hosted sets using the sealed backend, each organization has a separate key ring in each region. One KMS key per region wraps all of those organization ring keys. An operator with access to the wrapped rings and that KMS key can decrypt values belonging to any organization in the region. This is shared regional KMS authorization, not independently authorized KMS keys per organization. In a self-hosted region, you control the operator, key custody, and wrapping configuration. These sealed-storage guarantees do not apply to legacy managed sets stored in Vault.Deployment Authority
The control plane is trusted to authorize agent deployments, including the image and attached secret sets. An actively compromised control plane could deploy code that reads existing attached Secrets. Keeping decryption keys in your region, or encrypting values before submitting them to the API, does not remove this workload-control authority. Independent admission, image, and egress policies in your cluster can further constrain it.Never Read From Your Region
The operations above have these limits, independent of their settings:- Session traffic. WebSocket and telephony sessions connect directly to your region; Daily WebRTC sessions connect to Daily’s media infrastructure as they do for every region. In neither case does session media pass through the Pipecat Cloud control plane.
- Referenced Secret values. Reference and status operations check existence and type only; their responses cannot carry keys or values.
- Environment variable values, Secret data, or ConfigMap contents through the support-bundle or deployment-status routes. Support bundles include the allowlisted deployment settings described above.
- Support-bundle resources outside the system and workloads namespaces. The bundle’s read-only Roles are scoped to those two.