# Security Policy

## Trace data

This extension intentionally captures complete Pi-level LLM requests, final LLM responses, tool arguments, tool results, provider payloads, and errors. It does not redact values. Trace files can therefore contain API keys, credentials, source code, personal data, or other sensitive content that appeared during a session.

The Viewer binds to `127.0.0.1`, requires a random per-run token for trace data and WebSocket access, loads its assets locally, and does not upload trace data. These boundaries reduce accidental exposure but do not make trace files safe to share.

Do not attach an `events.jsonl` file or an unreviewed Viewer screenshot to a public issue.

## Reporting a vulnerability

Report security issues through GitHub's private security advisory feature for this repository. Include a minimal reproduction with synthetic data. Do not include real credentials or private trace files.