Privacy and your data

Agent session logs often contain source code, file contents, command output, and anything you typed into a prompt — sometimes including secrets. Origin copies these logs so that they survive the agents' own cleanup. This page explains what it stores and how to remove it.

What Origin stores

Everything lives in one directory, ~/.origin (or ORIGIN_HOME):

• origin.db: a SQLite database with the normalized events, their search index, your entries, and the record of everything you forgot.
• raw/: append-only copies of the original session log files.

Your data lives only on machines you control: your devices and, if you run one, your own hub. Origin never calls a third-party service or an LLM API. Without a hub it makes no network connections at all; with a hub, the only traffic is between your devices and your hub. The directory is not encrypted, so protect it the way you would protect the original logs.

Forgetting

origin forget <id> (or the agent's forget tool, used only when you ask) is permanent:

1. Forgetting an entry forgets every version of it and hides the events it cites.
2. Forgetting an event hides it and forgets every entry that cites it.
3. An entry left with no visible source is forgotten too.

Forgotten entries and events disappear from search, timelines, and every MCP tool, and can never be cited again, even after re-syncing. For example, use origin forget <event-id> on a prompt where you pasted a secret.

Forgetting hides; it does not erase. The raw mirror files under ~/.origin/raw/ still contain the original lines, because the archive is append-only.

With a personal hub

A personal hub changes where your data lives:

• A server you control. The hub holds a full copy of every connected device's sessions and all your entries. Run it only on a machine you control, and protect its data directory like ~/.origin.
• TLS and tokens. The hub speaks plain HTTP, so put it behind TLS before exposing it. Every request except /healthz needs a token. The hub stores only hashes of tokens, and you can revoke a token when a device is lost or retired.
• Forgetting reaches every device. Forget on the hub, through an agent or the CLI on the hub, and each device applies the same tombstones on its next push. Forgotten events stay hidden even if a device pushes them again.
• Staging copies. Each device keeps a local staging copy of its own sessions. Forgetting hides data there too, but as everywhere, the raw mirror files still contain the original lines.
• The admin UI shows your sessions. If you enable the hub's admin UI, anyone who knows the admin password can read your archived sessions and entries in a browser. Guard the password like the hub itself. The UI never shows the text of forgotten entries or events.
• The audit log records clients. Sign-ins and administrative actions are logged on the hub with the client's address and the browser's user agent, but never with entry or event text.
• A CDN sees decrypted traffic. A CDN or proxy that terminates TLS sees everything that passes through it: what devices push, what agents read, and what the admin UI shows you. Prefer private access to the admin UI if that matters to you.

Removing everything

Delete ~/.origin (or your ORIGIN_HOME). Without a hub, Origin keeps nothing anywhere else; with a hub, also delete the hub's data directory (/data in the container) and revoke the device's token. Also remove the MCP registration from your agents (for Claude Code: claude mcp remove --scope user origin).

Reporting a problem

If you find a way Origin could leak, expose, or corrupt your data, please report it privately as described in the security policy.