Panicly handles traffic policy data so your team can control model spend before it leaves the workspace.
This page summarizes the data Panicly needs to authenticate workspaces, apply routing and guardrails, and expose operational history to your team.
What Panicly stores
Panicly stores workspace identity, project configuration, request metadata, and encrypted provider credentials needed to operate the gateway.
What Panicly does not claim
Provider billing, provider retention, and model-level processing are still governed by the upstream providers you connect. Panicly sits in front of those calls to enforce policy before traffic leaves your workspace.
Operational data
Request history includes routing decisions, timestamps, and estimated spend signals so operators can audit why traffic was allowed or blocked.
Access and security
Workspace access is tied to authenticated organization sessions. Secrets are encrypted at rest and used only to forward approved requests to configured providers.