The design principle throughout: local-first, shared by choice. Recording happens on your machine; TracesHub only ever holds what someone explicitly pushed. This page covers what that is, and every control around it.
What TracesHub stores
For each project, the hosted trace store holds what pushes have shipped:
- Traces — structured session records: tool, model, files touched, timing.
- Attribution ledgers — per-commit, per-line maps of AI authorship (line hashes, not code contents).
- Commit links — bindings from git commit SHAs to traces.
- Conversations & summaries — prompts and session transcripts behind traces, if your configuration ships them.
Around that, the application keeps what it needs to operate: your GitHub profile (login, name, avatar, email) synced at sign-in, org/project/membership records, token hashes and prefixes (never secrets), and an audit log of administrative actions.
Your source code is not stored as a copy. The Files and Analytics views read the repository live from GitHub via the App at the default branch’s HEAD; the trace store itself carries diffs/changes inside trace records and transcripts only to the extent your push settings include them.
You decide what ships
Three layers of control, all on the CLI side, all documented in the CLI configuration reference and push / pull / sync:
- Nothing syncs automatically. Uploading is always an explicit
agent-trace push/syncby someone holding a write token. - Config toggles decide how much detail is recorded and included — full conversations, prompts and summaries, or attribution only.
- Push flags narrow a specific push (
--only traces|ledgers|commit-links; unattributed traces are skipped unless--full).
A team that wants the hub to hold “which model wrote which line” and nothing else can have exactly that.
Who can see what
Access to everything above is governed by the access model: projects are visible only to org members and explicit collaborators, per their read/write/admin level. There are no public projects. The gateway enforces this on every request — including CLI reads like agent-trace pull.
Data export
Org owners and admins can download a full export of an organization — Settings → Data export. It’s a ZIP archive containing the org’s trace data, metadata, and audit log. Each export is itself recorded in the audit log.
Use it for backups, compliance reviews, or moving to a self-hosted agent-trace-service.
Deletion
- Delete a project (project Settings tab, owners/admins, type-to-confirm) permanently removes its hosted trace data — traces, ledgers, conversations, summaries. The GitHub repo and everyone’s local data are untouched. See Projects.
- Disable traces (project header) is the reversible half-step: nothing is deleted, but reads and writes are refused until re-enabled.
- Revoke tokens (Settings → API tokens) to cut off any pusher immediately.
Legal
The Privacy Policy and Terms of Service are the authoritative statements of how data is handled.
Questions about your data, export, or deletion? Email support@traceshub.com.