Privacy
Last updated 2026-07-13
The free tool runs entirely in your browser
When you paste or upload a file list, it is parsed and analyzed with JavaScript on your own machine. It is never uploaded, and we never see it.
The paid API sees file paths and sizes — never file contents
When you connect the GitHub Action or pre-commit hook, it sends us a list of your file paths and their byte sizes so we can generate your config files and send them back. We never receive the contents of your files. We store only aggregate counts for each run — how many files, total bytes, how much was pruned, and which tool called — tied to your account for usage stats. We do not store your file paths or your file contents.
Signing in
You sign in with GitHub. We ask GitHub only to identify you — we never request access to your repositories. We store your account identifier and, if GitHub shares it, your email address.
Payments
Billing is handled by Stripe. Your card details go straight to Stripe and never touch our servers. We store your Stripe customer and subscription identifiers and your subscription status.
API keys
Your key is shown once, at creation. We store only a SHA-256 hash of it — we can't recover the key, and neither can anyone who reads our database.
Analytics
We use Vercel Web Analytics, which is cookieless. We record anonymous, aggregate events — that a manifest was analyzed, the sample was loaded, the savings counter was viewed, an upgrade was clicked, checkout was started — and page views. These never include your file paths, file contents, or any personal information.
Staying signed in
Your session is kept in your browser's local storage so you don't have to log in every visit. We don't use tracking cookies.
Your data
Deleting your account removes your account, keys, and usage records. To request deletion or ask a question, email support@contextpruner.app.