Privacy Policy
Last updated 21 October 2026
What we store
- GitHub identity: your GitHub user id and username, and the ids of the app installations you can manage. Kept in a signed cookie in your browser; we don’t store your GitHub sign-in token.
- Installation data: the account or organization name, the names and ids of the repositories you selected, and whether each is private.
- Upgrade records: for each attempted upgrade, the package and versions, its status, the pull request link, and, when an attempt fails, an excerpt of the error output (which can include short snippets of your code or build logs).
- Billing: your Stripe customer and subscription ids and trial dates. Card details are handled by Stripe and never reach us.
How your code is processed
To attempt an upgrade, your repository is cloned into a temporary, isolated container on our worker, where your install, build and test commands run. The copy is deleted when the job ends. When a check fails, we send the error output, the upstream release notes, and the relevant source files (up to roughly 120 KB per attempt) to an AI model provider to generate the fix. We don’t use your code to train models.
Who processes data for us
- GitHub: access to your repositories, through the permissions you grant the app.
- NVIDIA (NIM) and Groq: AI model inference for generating code fixes.
- Supabase: database for the records above.
- Vercel: hosting for the website and API.
- Stripe: payments.
Cookies
We set one session cookie when you sign in with GitHub and a short-lived cookie during sign-in to prevent request forgery. No advertising or tracking cookies.
Retention and deletion
Uninstalling the app on GitHub deletes your installation, repository and upgrade records from our database. Stripe keeps billing records as required by law. To ask for deletion or a copy of your data, email support@jamiepulls.com.
Changes
We will update this page when our practices change and notify paying customers of material changes by email.