Privacy

Effective May 25, 2026. We’ll post a notice on this page and update the effective date if anything material changes.

ctxpilot is local-first by design. The product runs on your machine, talks to your AI provider with your own keys, and writes captured memories to a SQLite file in your home directory. We don’t see any of it. This page explains, in plain English, exactly what data we do touch and what we do with it.

The short version

• Your code never leaves your machine. Hook events, memories, sessions, and CLI reports all run locally.
• No telemetry. ctxpilot doesn’t phone home. No analytics, no error reporting, no usage pings.
• No third-party data sharing. We don’t sell or rent your data. Website hosting, beta signups, and payments use the providers listed below.
• We only collect data you give us. If you join the beta or buy a paid plan, we collect the account and billing details needed to run that flow.

What ctxpilot stores on your machine

The ctxpilot worker writes the following to your local disk:

• The SQLite database at ~/.contextpilot/contextpilot.db containing memories, sessions, and ingest event metadata.
• Configuration at ~/.contextpilot/config.json.
• Hook scripts installed into your agent’s config directory (e.g., ~/.claude/hooks/).
• License status at ~/.contextpilot/license.json if you activate a paid beta license.

None of these files are sent anywhere. You can read them, copy them, encrypt them, or delete them at any time. A first-class export command is planned; today the data is stored in your local SQLite database.

What ctxpilot does NOT collect

• Source code or file contents (those stay in your repo and in the local memory DB only)
• Tokens, prompts, or model responses
• API keys or credentials (the secret scanner actively blocks these from storage)
• Telemetry of any kind — no event pings, no crash reports, no “anonymous usage stats”
• IP addresses or machine fingerprints

What we collect if you pay for a plan

If you upgrade to Pro, Builder, or Team:

• Email address — for account recovery and billing notifications.
• Plan and license key — issued at purchase and verified through the license endpoint when you activate it.
• Payment information — processed by Stripe. We never see your card details; Stripe stores them.
• Optional: a company name and seat count if you’re on Team.

That’s the complete list. We don’t collect names, addresses, phone numbers, or anything we don’t need to run billing.

License key validation

Paid beta licenses are validated when you run contextpilot license activate. The validation request includes the license key and a device name so we can debug activation issues. It does not include usage data, code, prompts, model responses, repository names, or information about what you’re building.

This website

The marketing site you’re reading right now (ctxpilot.dev):

• Hosted on Vercel. Server logs are kept by Vercel under their privacy policy.
• No cookies for tracking. We may set a single first-party cookie to remember if you’ve dismissed a banner.
• No third-party analytics are required for the beta funnel.
• No advertising trackers. No social media trackers. No pixel trackers.

Provider API calls

ContextPilot does not proxy your model calls. Your agent continues talking directly to whichever AI provider you already use. We never see those requests or responses.

Your rights

Because we collect almost nothing, there’s very little to request. That said:

• Access: email us and we’ll send you everything we have on you (probably just an email + a license key).
• Deletion: cancel any subscription and email us. We delete account records within 30 days.
• Local data: completely under your control. contextpilot uninstall --delete-data removes the local ContextPilot state directory.

Children

ctxpilot is a developer tool not directed at anyone under 16. We don’t knowingly collect data from minors.

Changes to this policy

If we change anything material, we’ll update the effective date at the top of this page and post a notice on our changelog. Continued use after a policy change means you accept it. If you don’t accept it, you can uninstall — your local data goes with you.

Contact

Email privacy@ctxpilot.dev for any privacy question, data request, or security report. We aim to respond within 3 business days.