Trust · Data handling
You decide what is kept, and for how long.
Every use case carries its own data class and capture policy. IntSen records what it needs to govern; content is stored only when you switch it on.
What is recorded
Records, verdicts, turns—and bodies only by choice
| Data | When | Contents |
|---|---|---|
| Request record | Always | Client, use case, agent, model, tokens, cost, timings, status, refusal code |
| Guardrail verdict | Always | Check, category, score and action—never the matched content |
| Turn and steps | Always | Model calls, tool names, call ids, timings; arguments and results only with body capture |
| Request and response bodies | Only if capture is on | Stored for the use case's retention period, with optional PII redaction |
| End-user id | If your app sends it | Stored only as a hash |
| Evaluation and compliance results | If switched on | Scores, findings and judge reasoning per turn |
Capture policy
Set per use case, in its Registration
Body capture is needed for full traces, evaluations and compliance. Switch it off and you keep structural traces, cost and verdicts without content.
maxDataClass: confidentialcapture: { bodies: true, retentionDays: 90, redactPii: true }guardrails: pii: { enabled: true, action: mask } # mask before the model sees itData classification
Models are cleared per data class
A use case declares the most sensitive data it may send. Only models cleared for that class are usable; restricted models must also list the registration explicitly.
- public
- Information already public
- internal
- Internal business information
- confidential
- Sensitive business or customer information
- restricted
- Most sensitive; models must be explicitly cleared
Visibility and boundaries
Who sees what
Owners
Owners of a use case or agent see its traces, verdicts, scores, spend and—where captured—bodies.
Platform roles
Admin, leadership and approver roles come from your identity provider's groups and are checked on the server.
Model providers
Receive the request content needed to answer, without IntSen headers, and with personal data masked if you set it.
Map IntSen to your data policy.
We'll walk your privacy and security teams through capture, retention, redaction and access.