No stored prompts
Queries, parameters, and MCP responses are not retained.
Anonymous metrics only
Collected signals are operational, aggregated, and non-content based.
Review-ready summary
Built to answer the first questions buyers and security teams ask.
What we don't store
No user content retention
- We do not store user queries.
- We do not store tool parameters.
- We do not store MCP responses.
- We do not keep route-level payload histories.
What we do store
Anonymous operational metrics
- Basic usage counts, such as routes created or updated.
- Feature-level activity, such as tool selection changes.
- System health signals, such as uptime or error rate trends.
Why we store it
To operate and improve the product
These metrics help us understand reliability, identify broken flows, and improve the product without capturing customer requests or MCP outputs.
How it's anonymized
Separated from user content
The collected metrics are designed to avoid storing prompt content, request parameters, or response payloads. They are limited to aggregate or non-content operational signals.
For teams
Built for security review conversations
This is the page buyers, security teams, and enterprise reviewers can check when they want a clear explanation of how McpSecRouter handles privacy and operational data.