Claims ledger

Each claim, beside what makes it true.

A claim is on this page only if a proof holds it. Each row gives the claim as our pages print it, what makes it true, how you can check it yourself, and the date its proof last passed.

Check my firm What we do not claim

01 · What we claim

The claim, the reason, and your own check.

Every paid assessment is human-verified before release.

What makes it true: The release job holds every paid assessment until a person has cleared it. It has no path to release without that step.
How you can check: Your assessment page shows the date a person verified it.
How we test it: The sentence is matched to the page it is printed on, then to the code: the release job, the stored findings and the request that writes an email record are each run on a test record.
Proof: agents_page_proofs, G5
Last verified: 8 October 2026
Where we say it: Our agents

A finding with no evidence is not released.

What makes it true: A finding stored without its record stops the release, and an approval already given is withdrawn.
How you can check: Every finding in your assessment carries the record behind it.
How we test it: The sentence is matched to the page it is printed on, then to the code: the release job, the stored findings and the request that writes an email record are each run on a test record.
Proof: agents_page_proofs, G5
Last verified: 8 October 2026
Where we say it: Our agents

Every finding is kept with the record that proves it and a check you can run yourself.

What makes it true: Each finding is stored with the record it was read from, the check to repeat, and the date it was read.
How you can check: Run the check beside the finding, or hand it to your IT provider or your insurer.
How we test it: The sentence is matched to the page it is printed on, then to the code: the release job, the stored findings and the request that writes an email record are each run on a test record.
Proof: agents_page_proofs, G4
Last verified: 8 October 2026
Where we say it: Our agents

A change to your email records is made only when you confirm each step.

What makes it true: The request that writes a record is refused unless it carries your confirmation.
How you can check: Each step you confirm is listed on your dashboard with its date.
How we test it: The sentence is matched to the page it is printed on, then to the code: the release job, the stored findings and the request that writes an email record are each run on a test record.
Proof: agents_page_proofs, G6
Last verified: 8 October 2026
Where we say it: Our agents

No token is kept: it is used once and discarded.

What makes it true: The table that records a change has no field for a token, and none is written to any stored row.
How you can check: You can revoke the token at your DNS host as soon as the step is done.
How we test it: The sentence is matched to the page it is printed on, then to the code: the release job, the stored findings and the request that writes an email record are each run on a test record.
Proof: agents_page_proofs, G6
Last verified: 8 October 2026
Where we say it: Our agents

Our agents work from outside only.

What makes it true: The modules that do this work hold no way to sign in anywhere.
How you can check: Every limit is written down in the outside reading policy.
How we test it: The sentence is matched to the page it is printed on, then to the code: the release job, the stored findings and the request that writes an email record are each run on a test record.
Proof: agents_page_proofs, G8
Last verified: 8 October 2026
Where we say it: Our agents

They never log in, never install anything, and never touch your internal systems.

What makes it true: The same modules are searched for any sign-in call, and none is there.
How you can check: Every limit is written down in the outside reading policy.
How we test it: The sentence is matched to the page it is printed on, then to the code: the release job, the stored findings and the request that writes an email record are each run on a test record.
Proof: agents_page_proofs, G8
Last verified: 8 October 2026
Where we say it: Our agents

02 · What we do not claim

Five things we do not say.

Each of these is kept off our pages by a rule in the same proofs.

That anything is fixed without your approval.
That we act inside your systems.
That anything is watched in real time: checks run on stated schedules.
A promise that nothing gets through.
A count of customers, or a reference from one.

03 · How this page is kept true

It is built from the proofs.

Each claim here is copied word for word from the list a proof holds, and a row whose words no longer match is not shown.
A row is shown only while the page that makes the claim is being served.
The date beside a claim is the day its proof last passed, written down by the command that runs the proofs. It is never the day you open this page.
Where no run has been written down, the row says not yet recorded.