Terms

Last updated: September 3, 2026

DeadlineScan is operated by Trevor Engen as a sole proprietor in the United States. These terms are written to be read once, in full, without a lawyer. If something here is unclear, ask before you buy: hello@deadlinescan.com.

The scanner

The DeadlineScan command-line scanner is free and MIT licensed. The licence text governs it, and it says what MIT licences say: you may use it, and it comes without warranty. Nothing on this page narrows the licence.

The scanner runs on your machine. It makes no network calls and sends no telemetry, so your code never leaves the machine while you are scanning. That is a property of the binary rather than a promise about our conduct, and you can verify it from the source.

What a paid deliverable is

Both paid services produce a draft for your review. A drafted migration pull request compiles, and your existing tests pass where tests exist. That is the standard it is delivered against, and it is not a warranty that the change is correct for your business, that every behaviour of the replaced call survived the move, or that your integration is finished.

You review, you test, and you decide whether to merge. Nothing we deliver is merged, deployed, or run against your production systems by us.

A runbook is a plan, not an outcome. It describes configuration to apply and decisions to make; applying them stays with you.

Access, and what we do with it

Any access you give us is voluntary and yours to withdraw. For a pull request there are two routes and the choice is yours. Opening a pull request on your repository needs collaborator (write) access — on a public repository, a fork works instead. Read-only access is enough for the other route, and only for that one: you send a patch-ready copy of the code and get a patch file back. Choosing the patch route does not change the price or the deliverable.

We use what you send only to produce the deliverable you paid for. We do not train on it, resell it, or share it with anyone outside the delivery of that work. What is kept, and for how long.

Delivery

Both services are delivered within 72 hours. The clock starts when everything needed to do the work has reached us: the scan report, and for a pull request the repository access or the code. If something is missing we will say so rather than let the clock run.

Scope is capped and stated on the services page: up to 10 call sites per pull request, one runbook per report. Larger estates are quoted by email before any payment.

If it goes wrong

If we miss the 72-hour delivery, or the deliverable is unusable and one revision does not fix it, you get a full refund. That covers the two fixed-price services on the services page; work quoted by email for a larger estate follows the same two rules unless the quote says otherwise in writing before you pay. The refund terms.

Accountability

Trevor Engen is the accountable human and reviews every paid deliverable. That is a statement about who answers for the work, and it is why the sentence above appears on every report the tool prints and on every page of this site.

Changes to these terms

The “last updated” date at the top of this page is the version marker. If these terms change, that date changes with them, and the version in force for a piece of work is the one carrying the date it bore when you paid. Ask for a copy at any time.