Data Policy
0ctx is local-first. The local daemon and SQLite database are the source of truth. No data leaves your machine by default.
Default policy
New workspaces default to:
| Setting | Default |
|---|---|
| Workspace data policy | local_only |
| Local capture retention | 14 days |
| Debug artifacts retention | 7 days |
| Debug artifacts | Off by default |
Local-only by default
The local_only policy means all captured sessions, checkpoints, and workstream state stay on your machine. There is no cloud sync or remote storage in the default path.
What stays local
Local state lives under ~/.0ctx/ and can include:
- SQLite database — sessions, checkpoints, workstreams, and workspace metadata
- Hook dumps — raw capture output from repo-installed hooks
- Transcript snapshots — session transcripts for supported agents
- Backups — periodic database backups
Debug-heavy artifacts are reduced by default to keep the footprint lean.
Legacy remote sync states
Older builds used two additional workspace settings that are no longer part of the supported path:
metadata_only— legacy setting from older builds. No longer part of the supported local-only path.full_sync— legacy setting from older builds. Should be normalized back tolocal_only.
Privacy defaults
- A clean source build does not send CLI telemetry unless explicitly enabled and configured.
- UI surfaces do not initialize Sentry unless
NEXT_PUBLIC_SENTRY_DSNis set. - Payload and debug data are utility-only — available for support, debugging, and advanced inspection, but not part of the normal workflow.