Your data
What Introspection stores, how it is protected, and how to get it out or remove it.
Introspection stores what your agents do: conversations, tasks, files, memory, and telemetry.
Where it is stored
| Data | Where |
|---|---|
| Conversations, telemetry, observations, judgements, feedback, tasks, files, memory | The project’s data plane |
| Members, bindings’ credentials, audit log | The control plane |
| Per-user connections | Your own Pipedream Connect project (Per-user tool access) |
How it is encrypted
- At rest: every store a data plane provisions is encrypted under that plane’s KMS key.
- Per organization: stored credentials, files, and the conversation payloads the platform processes are also sealed with keys wrapped by your organization’s own key.
- In transit: every call that leaves the data plane (to the control plane, the model gateway, Pipedream, your MCP servers) uses TLS to a public hostname. Inside the plane’s cluster, the sandbox reaches its egress proxy over plain HTTP so the proxy can add credentials; contact us for the rest of the in-cluster hop list.
On BYOC and on-prem, the plane’s KMS key is in your account.
Files stored without the organization key
A file uploaded with metadata {"encryption": false} skips the organization
key and is protected only by the plane’s KMS key. The platform uses this for
large raw uploads such as image layers. Omit it for your own files.
How long it is kept
| Data | Kept |
|---|---|
| Conversations and other telemetry | Until retention is enabled for your data plane. Retention is set per plane and is off by default; contact us to set a horizon. |
| Tasks, files, memory, members | Until deleted |
| Audit log | At least 2 years (Audit log) |
A file with --ttl-seconds | Until it expires |
Export a conversation
introspection conversations export <conversation-id> --format json --output-file conv.jsonTo export several at once, name the IDs; the list command prints them:
introspection conversations list --lookback 30d --query "[].id" -o table
introspection conversations get <id-1> <id-2> --output-file conversations.jsonlMore in Find a conversation.
Delete data
| To remove | Run |
|---|---|
| Files or memory files | introspection files delete --yes <file-id-1> <file-id-2> (several IDs need CLI 0.52.0 or later) |
| One person’s memory | Delete one owner’s memory |
| A task | introspection tasks delete <task-id> |
| A conversation’s telemetry | Contact support@introspection.dev for a purge |
Deleting a task does not remove its conversation: telemetry is append-only.
Contact us for
Email support@introspection.dev for:
- whether customer data is used to train models, and model providers’ retention terms
- a BAA or HIPAA
- customer-managed keys on Managed Cloud
- the full list of subprocessors
- the list of regions
Limits
| Not supported | Do this instead |
|---|---|
| Redaction before content is recorded | See what leaves your cloud. |
| Deleting a conversation yourself | Ask support for a purge. |
Next
Last updated on