Privacy

What CodeMD does with your code and data on codemd.dev. Last updated November 14, 2026.

In short

Your account

Payments

Stripe handles payments for CodeMD Pro. Your card details go to Stripe, never to us. We keep your Stripe customer ID and your subscription's status, plan and renewal date.

Repository analysis on codemd.dev

When you analyze a repository on codemd.dev, CodeMD downloads its code to build the analysis. The downloaded copy is working data on our servers and is not kept as a repository copy: the downloaded ZIP is deleted as soon as it is unpacked, and the unpacked files are deleted after 7 days without use. We keep what the analysis produces so you can come back to it, and that includes some text taken from your code:

Comments and documentation can contain anything you wrote in them, so don't put secrets there. If you run the analysis while signed in with GitHub, the results can be seen only by people who can see that repository on GitHub. Results for a public repository analyzed without signing in are kept in a separate private store, and are opened only through short-lived links the site creates. AI features, when you use them, send the code they need to an AI provider, as described under "Services we use" above.

You can delete a repository's analysis any time. With push access to the repository, press Delete analysis on your dashboard; otherwise email contact@codemd.dev and we'll delete it.

Services we use

These services process data for us, only to run CodeMD:

We may also share data if the law requires it, to protect CodeMD or its users from harm or abuse, or as part of a merger, acquisition or sale of CodeMD, where these promises continue to apply.

CodeMD PR Checks

The single CodeMD PR Checks GitHub App posts CodeMD Call-Path Security and CodeMD Impacted Tests on pull requests and supported pushes in the repositories you choose.

What the app can access

What happens to your code

What CodeMD keeps

Who sees the result

The check result is posted to GitHub, so anyone who can see the repository on GitHub can see it, including the function names and file paths it lists.

Stopping it

Uninstall the app, or remove a repository from it, in your GitHub settings. CodeMD then can't read that repository and stops checking it, and GitHub tells CodeMD, which deletes that repository's kept lists of risky functions and queue entries right away.

Limits

The check is free and shared, so each installation gets a limited number of checks per hour, large repositories aren't scanned, and checks may be skipped when too many are waiting. A skipped commit gets a neutral "not scanned" result instead of a pass or fail.

CodeMD Impacted Tests

The CodeMD PR Checks GitHub App posts CodeMD Impacted Tests on pull requests and pushes to the default branch. Free runs existing tests whose commands CodeMD can determine without AI. Pro can use AI to determine additional commands and create a test when a changed file has none.

What the app can access

Optional: enforce the branch limit in GitHub

A repository administrator can make GitHub reject any attempt by CodeMD to update another branch:

  1. Open the repository on GitHub, then go to Settings → Rules → Rulesets → New ruleset → New branch ruleset.
  2. Name the ruleset (for example, Protect branches from apps) and set its enforcement status to Active.
  3. Under Target branches, include all branches, then add an exclusion for codemd-test-runs.
  4. Under Bypass list, add only the trusted people, teams or repository roles that must be able to update those branches. Do not add the CodeMD GitHub App.
  5. Enable Restrict updates. We also recommend Restrict deletions and blocking force pushes.
  6. Save the ruleset. Use GitHub's rule insights or test with a non-default branch to confirm normal developer and pull-request workflows still work before relying on it.

This ruleset protects the default branch and every pull-request branch it targets while leaving codemd-test-runs available to CodeMD. Ruleset availability depends on the repository visibility and GitHub plan. See the detailed CodeMD installation and branch-lockdown guide, GitHub's documentation for creating a repository ruleset, and the available rules.

What happens to your code

What CodeMD keeps

Limits

Each installation can start a limited number of checks per hour, and each check runs a limited number of tests. A commit over the hourly limit gets a neutral "Hourly limit reached" result.

CodeMD Feature Impact

The CodeMD PR Checks GitHub App also posts CodeMD Feature Impact on pull requests. It is informational: it is always neutral and never fails a pull request.

What happens to your code

What CodeMD keeps

Website usage analytics

Keeping data safe

We use encrypted connections, limit who and what can reach stored data, keep access tokens out of our logs, and store them only encrypted or hashed. No service is perfectly secure, though, and we can't guarantee that data will never be exposed. If a breach affects your data, we'll tell you as the law requires.

Your rights

Children

CodeMD isn't for children under 13, and we don't knowingly collect their data. If you think a child has given us data, email us and we'll delete it.

Where data is processed

The services we use may process data in the United States and other countries, which may have different data protection laws from yours. Using CodeMD means your data may be processed there.

Changes

We may update this page. We'll change the date at the top, and for significant changes we'll give notice on codemd.dev.

Contact

Questions about your data, a request to delete it, or a security problem you found in CodeMD: email contact@codemd.dev or visit Support.