Privacy Policy

Last updated: [FILL: YYYY-MM-DD]

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 and explicitly do not collect your source code.

1. What we collect

Account information:

Email address (for login + account communication)
Hashed password or OAuth identifier
Agent token (issued by us, identifies your CLI / daemon to our API)

Workspace metadata:

Organization name and slug
Project / repo names
Branch and commit SHA references for context (we record SHAs, not the code at those SHAs)

Captured session activity (only what you explicitly capture):

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

Operational telemetry (when enabled):

Error reports via Sentry (stack traces; no captured-content payloads)
Aggregate, anonymized CLI usage counts (e.g., "explain was called N times this week")

[FILL: Confirm and adjust the above list against the actual collected data per engineering audit before publishing.]

2. What we don't collect

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

Source code — your code stays in your Git remote and on your machine. The CLI does not read or upload file contents to our servers except for the limited cases listed under Section 5 (third parties).
Files you have not explicitly captured — observations and decisions capture only the text you type, not the surrounding code.
Passwords, secrets, or environment variables — if you accidentally include these in a captured observation, the responsibility is yours; we do not actively scan for or extract secrets.
Telemetry payloads with user content — Sentry receives stack traces and error metadata, not the contents of decisions, observations, or learnings.

[FILL: Add explicit "we do NOT use your captured content to train AI models" here if that's the policy — this is a strong trust signal worth surfacing.]

3. How we use your data

Operate the service (sync your captured content across sessions and teammates)
Authenticate API requests (agent token validation)
Provide explain / search / recall / prime responses
Send service-related email (security alerts, billing, product updates if you opted in)
Detect and investigate abuse of the service
[FILL: Add any analytics, aggregated reporting, or product-improvement use cases.]

4. Where your data is stored

Cloud database — operated on [FILL: hosting provider, e.g., Vercel + Vercel Postgres or Neon, located in the 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 integrates with the following third parties. Each has its own privacy policy.

[FILL: Hosting provider, e.g., Vercel] — application hosting and edge delivery. [FILL: link to their privacy policy]
[FILL: Database provider, e.g., Neon / Vercel Postgres] — primary database. [FILL: link]
Anthropic — when an explain request lands on a cache miss, we send the relevant memory context (decisions / observations) to the Anthropic API to synthesize a WHY-summary. We do not send your source code. [FILL: link to Anthropic's privacy policy and confirm the no-training contractual stance applies to your usage.]
Sentry — error reporting. [FILL: link]
[FILL: Stripe / billing provider, when active] — payment processing.

6. Cookies & tracking

The CommitMind dashboard uses [FILL: which cookies — typically only first-party session cookies for authentication]. We do not use third-party advertising cookies.

[FILL: GDPR cookie banner language if applicable — required for EU visitors. If you ship a cookie consent banner later, link it here.]

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 [FILL: privacy@commitmind.dev]. We will respond within [FILL: 30 days for GDPR / 45 days for 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 [FILL: 30 days] of account closure. Aggregated, anonymized analytics may be retained longer.
Backups: automated database backups are retained for [FILL: 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 + revocable from the dashboard
[FILL: SOC 2 Type II / ISO 27001 status when applicable]

If you discover a security vulnerability, please report it to [FILL: security@commitmind.dev]. [FILL: Reference any responsible-disclosure or bug-bounty policy.]

10. Children's privacy

CommitMind is not directed at children under [FILL: 13 / 16 depending on jurisdiction]. We do not knowingly collect data from children.

11. International transfers

If you are outside the United States, your data will be transferred to and processed in the United States. [FILL: GDPR-required Standard Contractual Clauses or EU-US Data Privacy Framework certification language if applicable.]

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 [FILL: 30 days] before the changes take effect.

13. Contact

Questions about this Privacy Policy or how we handle your data? Contact our data protection contact at [FILL: privacy@commitmind.dev].