Security

Production insight with deliberate data boundaries.

Flowlines is designed to analyze agent behavior while keeping transport, access and identity responsibilities explicit.

Data handling

Follow the boundary from source to evidence.

Select each stage to see what Flowlines uses for analysis and what stays outside the product boundary.

choose what leaves your server

Data pathClick a boundary to inspect it
Ingest boundary

MCP telemetry stays within the approved boundary.

Flowlines processes permitted MCP telemetry according to the workspace's capture and retention choices. Other trace sources have their own data boundaries.

Used for analysisTool activityRelevant journey contextOutcome context
Outside the boundaryRaw headersStack traces

A clear boundary

Observability identifiers are not security credentials.

Request IDs, user IDs and session IDs help group production behavior. Authentication and authorization remain the responsibility of your application and identity layer.

Security review

Bring your architecture and requirements.

We’ll map your telemetry sources, data fields, connector scopes and retention expectations before production rollout.

Review current security, privacy, and compliance documents in the Flowlines trust center ↗.

Use Flowlines with your assistant

Review Flowlines against your production requirements.