← unbrkn.co

Privacy

Version 1, 12 September 2026. Unbroken Truth, the company behind Unbreak.

Unbreak fixes failing dependency-update pull requests. The fix runs inside your own GitHub Actions on your own Anthropic account. This page says what reaches us, what never does, where we keep it, and who to ask.

What we store

• Installations. The GitHub installation id, the account it is on, which repositories it covers, and the plan.
• Pull request metadata. For a failing dependency PR: repository name, PR number, commit SHAs, the package and versions bumped, the names of the failing CI jobs, and the first lines of their output as GitHub's Checks API exposes them (annotations and the tail of the job log). This is what triage reads, and it is sent to Anthropic's API on our own account, with the model asked to rate fixability. Nothing else of yours goes to that model from our side.
• Runs and reports. Who pressed the button, when, and the report the workflow posts back when it finishes: test counts before and after, regressions, the names of changed files with a one-line reason each, API cost and time, the outcome. The same report is on the PR as a check run and a comment.
• Outcomes. For each run, a summary of what was changed and whether it worked, used to make the next fix of the same kind better. Your repository is not identified in that corpus unless you opt in, and there is no opt-in yet.
• Billing. An invoice item per green fix and a credit per failed attempt, on a Stripe customer named for your GitHub account, with the email GitHub publishes for it. Card details never reach us; Stripe holds them.
• Web analytics on this site. Cloudflare Web Analytics, cookie-free, no personal identifiers, injected by Cloudflare at the edge; this page's source loads no script.

What we never store

• Your code. The workflow checks your repository out on your runner, with a token scoped to that repository. Our servers receive the report, not the tree, not the diff.
• Your Anthropic credential. The workflow reads it from your repository's variables or secrets and talks to Anthropic directly. It is never sent to us.
• Logs and transcripts. The agent's transcript and report.json are uploaded as an artifact in your own Actions run and stay there. We do not receive the transcript.
• Anything from the runner beyond two calls. One to get a repository-scoped token for pushing the fix, one to post the report. Both authenticated with the job's OIDC token.

Where it runs

• The App backend runs on Fly.io in the United States (Virginia). The database is Neon Postgres in the United States. Durable jobs run on Inngest. Payments on Stripe.
• Your fix runs in your own GitHub Actions runner and calls Anthropic's API from there, under your account and Anthropic's terms.
• The proprietary skill the agent fetches for an upgrade path is served from our backend to the running job and appears in full in the transcript on your runner.

How long, and how to remove it

• Installation and run records are kept while the App is installed and for the period billing and dispute handling need after that. Uninstalling the App stops every event; email us to have the records deleted.
• Public demo runs on our own repositories are published on purpose and stay public.

Who to ask

The engineering side at eng@unbrkn.co. Security reports go to security@unbrkn.co (also in security.txt). Write to us about your data and we will answer, and delete on request.