Privacy
Effective November 15, 2026. This is a plain-language notice for the product, not a lawyer's opinion.
What you give us
An error message or a short description, the AI tool you pick, and optionally a public GitHub URL. If you sign in, we store your email. If you buy credits, Stripe processes the payment. We do not see your full card number.
Secrets
Do not paste passwords, API keys, or .env files. Before a diagnosis is stored or sent to a model, we replace obvious keys, tokens, private keys, and database passwords with a redaction mark. We still ask you to clean the paste yourself, because a cleverly formatted secret can slip past a pattern.
GitHub
We only read public repositories, and only a bounded set of files: common config files and files named in the stack trace. We skip .env files, private keys, and lockfiles. We never write to a repository and we never ask you to install a GitHub app.
The model
When an AI key is configured, the redacted error and any public files we fetched are sent to the model provider through the Vercel AI Gateway, or not at all if no key is set. In that case a built-in explainer writes a labeled sample diagnosis on the server. We do not use your errors to train our own model.
Cookies and accounts
A visitor cookie remembers whether this browser has used the free diagnosis. A session cookie keeps you signed in. Both are httpOnly. We also keep a hash of the network address for rate limits, not the raw address in the credit ledger.
How long we keep it
Diagnoses stay on your account so you can reopen them. You can ask us to delete an account by emailing the address you used to sign in, once a support inbox is published. Until then, delete requests can be sent to the operator of the deployment.
Selling data
We do not sell personal information.