Last updated: June 29, 2026

Privacy Policy

This policy explains how ctx handles information for the public documentation site, support channels, and the ctx local search CLI.

Local CLI data

ctx is a local CLI for indexing existing coding-agent session history into SQLite and searching it from your machine. Setup, source discovery, import, search, show, locate, and transcript output read local files and local ctx storage for their transcript content.

The CLI may store sensitive developer history locally, including prompts, responses, code snippets, command text, command output previews, file paths, working directories, session metadata, and normalized searchable text. Treat the ctx data root, SQLite database, logs, and written JSON or transcript output as private developer data.

By default, the ctx data root is ~/.ctx. You can choose a different root with CTX_DATA_ROOT or --data-root.

CLI analytics

The ctx CLI uses default-on product analytics for command invocation metadata, including install-triggered setup runs. This helps us understand which commands are used, whether they succeed, and where the CLI needs improvement.

CLI analytics are not intended to upload transcript text, prompts, responses, source code, indexed search content, search queries, result snippets, source paths, repository or branch names, native session IDs, command text, command output, or SQLite database contents. Setup, import, search, show, locate, and transcript output do not send your indexed transcript content to a model API as part of normal CLI operation.

Official installer-managed binaries can contact ctx release metadata endpoints for ctx upgrade and for background auto-upgrade checks after successful non-JSON commands. Upgrade checks are intended to send only ordinary HTTP request metadata plus release channel/platform context; they are not intended to upload transcript text, search queries, snippets, source paths, repository names, command output, or SQLite contents. Disable managed background auto-upgrade with ctx upgrade disable, CTX_UPGRADE_OFF=1, or CTX_DISABLE_AUTO_UPGRADE=1.

Analytics may include a generated install identifier, ctx version, OS, architecture, command name, success state, duration bucket, option booleans, bucketed counts, selected provider filters, and coarse network geography derived by hosting infrastructure.

We may process this metadata with service providers that host ctx sites, downloads, support, and analytics infrastructure. We keep analytics and support records only as long as needed for product operations, security, support, abuse prevention, legal compliance, and aggregate reporting.

To disable CLI analytics, set any of these before running install, setup, or other ctx commands:

export CTX_ANALYTICS_OFF=1
export CTX_DISABLE_ANALYTICS=1
export CTX_ANALYTICS_ENABLED=false

Public site and support

When you use the public docs site or contact us, we may receive information such as your email address, support messages, issue reports, diagnostics you choose to provide, IP address, browser and device metadata, referring pages, pages viewed, and basic site usage data.

Do not send unnecessary secrets, credentials, customer data, proprietary code, private transcripts, SQLite databases, logs, or written ctx output in support messages.

Third-party providers

ctx indexes history created by third-party coding agents and developer tools. Those providers control their own products, storage locations, network behavior, terms, and privacy practices. You are responsible for understanding the providers you use and for deciding what local history ctx should index, write to files, or share.

Contact

For privacy requests, email [email protected]. We can respond for data that ctx controls, such as support records and first-party analytics. Local CLI data remains on your machine unless you choose to send it somewhere.