Skip to main content
TrustGuard inspects prompts, completions, and tool traffic, so the first question any security review asks is what it keeps and where. This page answers that for everything a collector sends for evaluation.

​
Where records live

This is the answer that matters most, and it is decided by your deployment — not by a setting you can get wrong later.
On hybrid, evaluated traffic never leaves your perimeter. TrustGuard runs inside your infrastructure and exports records to the OTLP endpoint you configure, which on a hybrid deployment is a collector inside your own network. Prompts, completions, and tool payloads are written there and nowhere else.The link back to NeuralTrust carries configuration only: the control plane pushes policy and collector snapshots down, and your data plane acks the version it applied. Evaluated traffic is not part of that exchange and has no route onto it. If a data residency or data sovereignty requirement is what brought you to this page, hybrid is the deployment that satisfies it.
On SaaS, records live in the region your workspace was provisioned in. That region is set at provisioning time and cannot be changed from the console, so confirm it with your NeuralTrust contact before you onboard traffic.

​
What is stored

An evaluation produces two kinds of record, and they are not equally detailed. The second row is the one to plan around: the evaluated traffic is retained. Anyone who can open Activity in your workspace can read the prompt behind a finding, for as long as the retention window lasts. Scope workspace access on that basis, not on the assumption that only findings are kept. A finding on its own is safe to share widely — it says an email address was masked, not which one. The request body is not, which is why they are worth thinking about separately. If you consume this data downstream rather than reading it in the console, the event schema documents the exact shape of both records.

​
Credential redaction

Redaction runs before anything is written, and it is not configurable. Credential headers are replaced with a placeholder, so a collector API key never lands in storage:
The same applies to Cookie, Set-Cookie, X-Api-Key, X-Auth-Token, and the other well-known credential headers. Credential-looking body fields are replaced with [REDACTED] by key name, at any nesting depth: password, passwd, secret, token, api_key, apikey, authorization, credential, access_token, refresh_token, client_secret, and private_key, plus any key ending in _api_key, -api-key, or _apikey. Multipart bodies are never stored as content. Each part is reduced to its field name: file parts keep the filename and drop the bytes, and every other value becomes [REDACTED].
Redaction keys off names — header names and JSON key names. It is a guarantee about credentials in well-known fields, not a content filter over free text.

​
Attachments

Attachments are handled apart from the detectors’ view of the body:
  • Files attached to a request are decoded for the detectors that read them (today the Document Analyzer), and the decoded content is discarded afterwards.
  • Remote attachment URLs are fetched server-side under a strict SSRF guard — HTTPS only, with loopback, private, link-local, CGNAT, and cloud-metadata addresses blocked — and the fetched content is not retained.
Details: Attachments and SSRF.

​
Retention

Retention is a per-team entitlement, not a single global default. Every stored record is kept for the retention period in force when it was written and then deleted, so a record written today expires on a fixed date — changing entitlements later does not retroactively extend or shorten records already stored. For teams entitled to TrustGuard the default window is 365 days. A shorter window can be provisioned on request, so confirm your team’s window with your NeuralTrust contact rather than assuming the default. If you need a specific window contractually, or shorter than your current one, raise it with your NeuralTrust contact — it is an entitlement change, not a policy setting, so you cannot alter it yourself from the console.

​
Reducing what gets stored

If your threat model calls for storing less:
  • Deploy hybrid. The strongest control available, and the only one that removes NeuralTrust from the picture entirely: records are written to, and stay in, your own infrastructure.
  • Scope your collectors. Traffic that never reaches a collector is never evaluated and never stored. Attach policies deliberately rather than workspace-wide.
  • Use gates to waive traffic. A gate with the Skip action stops evaluation for matched requests, so no detector runs on them and no record is produced. See Policies.
  • Shorten retention. Ask your NeuralTrust contact to provision a window shorter than the 365-day default.