What we keep, what leaves, and how to delete it

• Account

  Your name, email, and either a bcrypt-hashed password or your GitHub sign-in identity. Organization membership and roles.

• Repository metadata

  File paths, sizes, languages, and content hashes — enough to render reports and diff scans, nothing more.

• Audit results

  Findings, health scores, architecture facts (modules, routes, imports, models), fix plans, and generated reports. Secret-detection findings record the location and credential type — never the secret value itself.

• Billing

  Handled by Stripe. We store your subscription tier and Stripe customer ID; card numbers never touch our servers.

What we never keep: a copy of your source code. Each scan downloads a read-only snapshot into a temporary workspace, analyzes it, and deletes the workspace when the scan finishes — whether it succeeded or failed. Your code is never executed, and it is never persisted to our database.

• AI providers

  Audit reports are generated from architecture facts— module flow, routes, findings — never your raw source. One clearly opt-in exception: when you approve an automated fix PR, the contents of the affected files (at most 4 files, 48 KB each) are sent to your configured AI provider to generate the change. On Pro and above you can bring your own provider keys so that traffic stays in your own account.

• OSV.dev

  During the vulnerability check, the names and versions of your direct dependencies are sent to the OSV.dev database — never any code. This runs on every scan and cannot currently be switched off per organization; we disclose it here instead of hiding it.

• GitHub

  Issues, milestones, and pull requests that you ask CodeTruss to create appear in your repositories under your installation’s permissions.

• Stripe & Resend

  Stripe processes payments; Resend delivers transactional email (invites, verification, scan-complete notices).

That is the complete list. We do not sell your data, share it with advertisers, or run third-party ad trackers.

CodeTruss uses a GitHub App with least-privilege permissions: repository contents (read/write, for snapshots and fix-PR branches), pull requests (read/write), issues (read/write, for roadmaps), and metadata (read). Repo operations use short-lived installation tokens that expire after about an hour. You can revoke everything at any time by uninstalling the app from your GitHub settings — no support ticket required.

Deleting a repository from the dashboard removes its metadata, findings, scans, and reports. To delete your account or organization entirely, email sales@codetruss.com from your account address and we will remove your data from our production systems within 30 days.

If this policy changes in a way that matters — new data collected, new third parties — we will update this page and its date, and email account owners for anything significant.