> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enfors.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Data captured vs. not captured

> Exactly what Enfors records for each turn, what it never records, and how PII is handled.

Both capture paths produce the same decision-grade record of each turn — the **watcher**
(reading the transcript) for Claude Code + Claude Desktop, and the **gateway** for agent SDKs.
This page is the authoritative list of what that includes — and what it excludes.

## Captured per turn

| Field                            | Source                        | Example                            |
| -------------------------------- | ----------------------------- | ---------------------------------- |
| `agent_id`                       | Machine username              | `claude_desktop_jsmith`            |
| `agent_name`                     | Username + platform           | `claudecode_claude-desktop-jsmith` |
| `session_id`                     | Session (call or transcript)  | `sess_abc123`                      |
| `model`                          | Request / transcript          | `claude-sonnet-4-5`                |
| `input_tokens` / `output_tokens` | Usage                         | `1,243` / `512`                    |
| `timestamp`                      | Call / transcript             | `2026-05-28T09:41:00Z`             |
| Prompt content                   | Request / transcript          | captured                           |
| Response content                 | Response / transcript         | captured                           |
| Tool calls                       | Request/response / transcript | captured                           |

## Not captured

| Data                             | Reason                                                            |
| -------------------------------- | ----------------------------------------------------------------- |
| File attachments                 | Not logged.                                                       |
| Provider credentials / API keys  | Never persisted. The watcher never touches provider auth.         |
| Network traffic (Claude Desktop) | The watcher reads the transcript — it does not intercept traffic. |

## The PII nuance

<Warning>
  Prompt/response content and tool calls are captured **as-is** — on the gateway path from the
  request/response, and on the watcher path from the local session transcript (which already
  contains that content on the machine, before Enfors is involved). Raw content lives in
  ingest logs with **14-day retention**, encrypted at rest.

  When a turn is reconstructed into the **durable decision ledger**, PII is **scrubbed**, and it
  is removed from API responses. So raw content is transient; the long-lived, queryable record
  is scrubbed.
</Warning>

See [Tenancy, Privacy & PII](/concepts/tenancy-privacy-pii) for the product-side view and
[Data residency & retention](/security/data-residency-retention) for retention periods.