Privacy policy
This policy covers Hard Keel Quantum Scan, on GitHub and on the command line, and this website. Updated November 20, 2026.
What the app does
Hard Keel Quantum Scan reads the code in repositories you choose. It finds encryption that quantum computers will break, weak encryption, and leaked keys or passwords. It reports what it finds on your pull requests and keeps an encryption inventory for each repository.
What the app can access
When you install the app, GitHub asks you to grant these permissions:
- Contents, read only: to read the code it scans.
- Metadata, read only: repository names and basic details, which GitHub grants to every app.
- Pull requests, read and write: to post a summary comment on pull requests.
- Checks, read and write: to post a pass or fail result on pull requests.
The app only sees repositories you install it on. You can change that list at any time in your GitHub settings.
What the app keeps
- Your installation: the GitHub installation ID, the account name and ID it is installed on, and the install date.
- Your plan: if you install through GitHub Marketplace, the account name and ID, the plan and the billing cycle GitHub sends us. We never see your payment details.
- The inventory scan: when the app is installed on a repository, it scans the whole repository once. It keeps the repository name, the commit it scanned, the number of files scanned, the encryption inventory and the findings.
Each finding records the file, the line number and that line of code, cut to 160 characters. Any key or password in a finding is masked to its first four characters before it is stored.
What the app does not keep
- Your code. The app reads it in memory to scan it, then discards it. Only the findings above are kept.
- Pull request scans. Their results go straight to GitHub as a comment and a check result, and are not stored by us.
- The event messages GitHub sends the app. They are processed in memory and not stored.
The command-line version
The command-line version runs on your own machine. Your code, the systems it checks and its results stay there. When you ask it to check websites or this machine, it says what it will touch before it starts, checks only what you approve, and writes a log of every connection and every file it reads.
Where it checks your network, it looks only at private address ranges on your own network. The addresses, names and page titles of your devices stay in the report on your machine.
The people and process checklist is optional. Your answers stay on your machine and are never sent to us.
Anonymized sharing
We collect anonymized, aggregated information about how our checks perform and what kinds of encryption they find. It never includes your code, keys, server names, IP addresses or company name. We use it to improve and build our products and to understand encryption trends across the industry. You can turn this off at any time, or run fully offline.
Each run sends one small summary:
- Checks: which checks found something, which were fixed since the last run, and which you chose to leave out, with counts rounded to bands such as 2-5.
- Encryption types: which kinds of encryption were found, from a fixed list, such as RSA or ML-KEM. Anything not on the list is sent as "other".
- Errors: the kind of problem only, such as a timeout.
- About the run: the tool version, the operating system, whether it ran in a pipeline, which areas were checked, and the day.
- A random ID: made on your machine and linked to nothing else.
- Industry and company size: only if you choose to give them.
We don't store the IP address a summary comes from. Summaries are deleted after two years. To see exactly what was sent, run quantum-scan config show-shared.
To stop sharing, run quantum-scan config sharing off, or set QUANTUM_SCAN_SHARING=off. To send nothing at all, use --offline. DO_NOT_TRACK=1 is respected too. To have your summaries deleted, email the random ID shown by quantum-scan config show to [email protected].
Report links
Each repository's encryption inventory and migration report has its own private link. The link is long and random, and anyone who has it can open the report without signing in. Share it only with people who should see it.
How long we keep it
Stored scans are deleted when you remove a repository from the app, and all stored scans and your installation record are deleted when you uninstall it. To have anything else deleted, email [email protected].
Who processes it
- GitHub: the source of the code and events the app reads, and where results are posted.
- Cloudflare: runs the app and stores the data above, including anonymized summaries, in its western North America region. Like any web host, it handles IP addresses to serve requests.
- DreamHost: hosts this website, behind Cloudflare.
- Google Fonts: this website loads its fonts from Google, which receives your IP address when you visit.
What we never do
We never sell your code or findings, use them for advertising, or use your code to train AI models. This website sets no cookies and runs no analytics or tracking.
Children
The app and this website are not directed at children under 13, and we do not knowingly collect their information.
Changes
If this policy changes, we will update it here and change the date at the top.
Contact
Questions about this policy go to [email protected].