Privacy Policy

Last updated: 2026-06-25

This policy describes what data CommitMind, Inc. ("CommitMind," "we") collects, how we use it, and the rights you have. CommitMind is a developer tool — we collect the minimum needed to operate the service. We do not collect your source code for normal operation; the limited, opt-in cases where AI features transmit a code diff are spelled out explicitly in Section 2 and Section 5.

1. What we collect

Account information:

• Email address (for login + account communication)
• Hashed password or OAuth identifier
• Tokens we issue to identify your tooling to our API:
  • an agent token — authenticates your CLI / daemon / MCP shells (per project)
  • a user access token and a rotating refresh token (cmr_…) — issued at login so you stay signed in without re-authenticating; the refresh token rotates on each use and is invalidated on detected reuse

Workspace metadata:

• Organization name and slug
• Project / repo names and Git remote URL
• Branch and commit SHA references for context (we record SHAs, not the code at those SHAs)
• If you connect a code host (GitHub), commit metadata (SHA, author, message, changed-file paths) we ingest to build your timeline — not the file contents at those commits

Captured session activity (only what you explicitly capture):

• Decisions you record via commitmind promote_decision or the dashboard
• Observations, learnings, rules, playbooks, specs, and capability docs you author
• Tasks, todos, and phase transitions you create
• Commit summaries generated from your captured activity

AI feature inputs (only when you use those features — see Section 5):

• The git diff of the change you are committing or reviewing, when you use AI commit messages, AI review, or the fix suggester. This is transmitted to generate the output and is not stored by us beyond the request.

Operational + billing data:

• Error reports via Sentry (stack traces; no captured-content payloads)
• Aggregate CLI usage counts (e.g., "explain was called N times this week")
• AI usage metering (which AI feature ran, token counts) used to compute billing — not the prompt content itself
• Payment information processed by our payment provider (we do not store full card numbers; see Section 5)

2. What we don't collect

CommitMind is designed to keep your code private. We do not:

• Read or upload your source code for normal operation — your code stays in your Git remote and on your machine. The CLI does not read or upload file contents to our servers, except the bounded git diff you choose to send when you invoke an AI feature (AI commit messages, AI review, or the fix suggester — Section 5). Those features are the only paths that transmit code, and only the diff of the specific change, not your repository.
• Collect files you have not explicitly captured — observations and decisions capture only the text you type, not the surrounding code.
• Harvest passwords, secrets, or environment variables — if you include these in a captured note or in a diff you send to an AI feature, that content travels with it; we do not actively scan for or extract secrets, so treat captured content and AI-feature diffs as you would any outbound data.
• Send telemetry payloads with your content — Sentry receives stack traces and error metadata, not the contents of decisions, observations, learnings, or diffs.

We do not use your code or captured content to train AI models. Diffs and memory context sent to AI features are processed under zero-data-retention / no-training terms with our AI gateway and model providers (Section 5), used only to produce the response you requested, and not retained by those providers to train models.

3. How we use your data

• Operate the service (sync your captured content across sessions and teammates)
• Authenticate API requests (token validation + refresh)
• Provide explain / search / recall / prime responses
• Provide the opt-in AI features you invoke (commit messages, review, fix suggestions)
• Generate and store embeddings of your captured content to power semantic search (Section 5)
• Meter AI usage and process billing
• Send service-related email (security alerts, billing, product updates if you opted in)
• Detect and investigate abuse of the service

4. Where your data is stored

• Cloud database — Neon (serverless PostgreSQL), hosted in the United States.
• Application + worker compute — Railway; web and landing surfaces — Vercel. United States.
• Local cachestore — a SQLite database on your developer machine that mirrors the cloud copy of your project's content for offline / fast-read access. We never have access to your local cachestore.

5. Third-party services

CommitMind relies on the following subprocessors. Each has its own privacy policy.

• Railway — application + background-worker hosting. https://railway.com/legal/privacy

• Vercel — web/landing hosting and the AI Gateway that routes our AI requests. https://vercel.com/legal/privacy-policy

• Neon — primary PostgreSQL database. https://neon.com/privacy-policy

• Anthropic and OpenAI — AI model providers reached through the Vercel AI Gateway. They power:

  • explain synthesis — sends your memory context (decisions / observations), not source code
  • AI commit messages, AI review, and fix suggestions — send the git diff of the change being committed / reviewed
  • embeddings of your captured content, to power semantic search

  Requests are processed under zero-data-retention / no-training terms; the providers do not retain this content to train models. https://www.anthropic.com/legal/privacy · https://openai.com/policies/privacy-policy

• Sentry — error reporting (stack traces + error metadata; no captured content). https://sentry.io/privacy/

• Stripe — payment processing for paid plans. We do not store full card details. https://stripe.com/privacy

• GitHub — when you connect a repository, we read commit metadata via the GitHub API to build your timeline. https://docs.github.com/site-policy/privacy-policies/github-general-privacy-statement

6. Cookies & tracking

The CommitMind dashboard uses first-party session cookies for authentication only. We do not use third-party advertising cookies.

7. Your rights

Depending on where you live, you may have the right to:

• Access — request a copy of your data
• Rectify — correct inaccurate data
• Delete — request deletion of your data (subject to legitimate retention obligations)
• Portability — receive your data in a machine-readable format
• Object — object to certain processing
• Withdraw consent — for processing based on consent

To exercise any of these rights, contact us at privacy@commitmind.dev. We will respond within the period required by applicable law (30 days under GDPR; 45 days under CCPA).

8. Data retention

• Active accounts: we retain your captured content as long as your account is active.
• Closed accounts: we delete your content within 30 days of account closure. Aggregated, anonymized analytics may be retained longer.
• Backups: automated database backups are retained for 30 days for disaster recovery; deletion requests are honored within backups on backup expiration.

9. Security

We protect your data with:

• TLS 1.2+ for all data in transit
• Encryption at rest for the cloud database
• Agent tokens scoped to project and revocable from the dashboard; user refresh tokens rotate on each use and self-revoke on detected reuse

If you discover a security vulnerability, please report it to security@commitmind.dev. We will acknowledge and investigate responsible disclosures in good faith.

10. Children's privacy

CommitMind is not directed at children under 16, and we do not knowingly collect data from them. If you believe a child has provided us data, contact privacy@commitmind.dev and we will delete it.

11. International transfers

If you are outside the United States, your data will be transferred to and processed in the United States.

12. Changes to this policy

We will update the "Last updated" date above when this policy changes. For material changes, we will notify you by email or in-product notice before the changes take effect.

13. Contact

Questions about this Privacy Policy or how we handle your data? Contact us at privacy@commitmind.dev.