Skip to main content
Agent sessions contain what your users typed. Armature treats them accordingly.

​
Redaction before storage

Detection models scan incoming sessions and redact PII and secrets by default, before anything reaches storage. An email address becomes a PII marker; a live API key becomes a SECRET marker. What you replay in the dashboard is the redacted session.

​
What leaves your server (and what doesn’t)

The SDK runs inside your process, and you can read exactly what it sends:
  • Sent: tool names, timing, outcomes, agent-reported telemetry fields, and size-capped previews of inputs and results (8 KiB each).
  • Hashed on your server: actor identity. The seed — a token, client ID, or header — is SHA-256 hashed before transmission; raw credentials never leave your process. See Identifying users.
  • Never sent: anything when no ingest key is configured. The SDK no-ops rather than buffering.
Delivery is HTTPS, authenticated by your per-server ingest key, which you can rotate or revoke at any time — revocation stops ingestion immediately.

​
Agent-side guardrails

  • The telemetry field descriptions instruct agents not to include secrets or PII when reporting intent.
  • The hosted Armature MCP rejects secret-shaped values passed as tool arguments and never returns credentials in tool responses.

​
Data retention

Session history is kept for your plan’s retention window (7 days on the Free plan; custom retention on Custom plans). Usage and retention for your workspace are always visible under Settings → Usage.

​
Access control

  • Ingest keys are scoped to one MCP server and write-only: they can send events, not read analytics.
  • Workspace API keys and OAuth grants control read access via the Armature MCP; grants are listed and revocable in the dashboard.
For SSO/SAML, audit logs, custom retention, or a full security review, talk to us.