Privacy

Last updated: September 3, 2026

Short, because there is not much to say.

The scanner

It runs on your machine and phones home never. It opens no sockets and issues no HTTP requests — not for updates, not for telemetry, not for lookups — and the mapping table is compiled into the binary. Nothing is collected, so there is nothing to opt out of, and your code never leaves the machine.

That is a property of the binary rather than a policy, which means you do not have to take our word for it: the source is MIT licensed and you can read it.

This website

It sets no cookies and runs no analytics. There is no tracking script, no tag manager, no embedded video, no third-party font. The pages are static files. The host logs requests, as hosts do; we run no analytics of our own and build no profiles from them.

If you email us

We keep the email, because that is how a conversation works and how we honour a refund later. We do not add you to a mailing list, and there is no mailing list to add you to.

Paid work

To deliver a paid service we need what you send us: your scan report, and for a pull request the repository access or a copy of the code. We keep it only as long as it takes to deliver the work and to handle a revision or a refund if you ask for one, and we delete it on request.

We do not train models on your code, resell it, or share it with anyone outside the delivery of your own work. Any access you grant is yours to withdraw at any time.

Payments

Payments are not yet open. When they are, card details will be handled by the payment provider and never by us. This page will be updated to name the provider before any payment is taken.

Ask

Anything about the above, or a deletion request: [email protected]. Trevor Engen is the accountable human.