TechStack Data

Standards

Corrections policy

We publish confidence levels, evidence classes and file vintages on every page precisely so that disagreement with us can be specific. If something we have published is wrong, we want the correction more than we want the page.

How to report an error

Email corrections@techstackllc.io with:

What happens next

  1. Logged. Every request is recorded with its date, the page and the claim.
  2. Answered within two business days. You get a response even when the answer is that we are not changing anything, and that response says why.
  3. Traced. We re-read the source filing at the edition the page cited, and check whether the error is in the filing, in our reading of it, or in a linking rule.
  4. Resolved. One of the outcomes below, applied everywhere the value appears — not only on the page you reported.

Possible outcomes

Outcome When it applies
Corrected We misread a filing or mis-applied a rule. The value is fixed and the change is dated.
Reclassified The value stands but the evidence does not support the confidence we assigned. The band is lowered.
Marked disputed Your evidence and the filing genuinely conflict. Both readings are published; neither is chosen.
Unchanged The filing says what we reported it says. We will say so, and cite the filing and edition.

The most common case. A great many reports are that a filing itself is wrong — that a company was recorded as an owner when it was not, for instance. We cannot amend a government file. What we can do is mark the value Disputed, publish your position alongside it, and point to the agency's own correction process. We will always do that.

What we will not do

Scope

This policy applies identically to every TechStack Data property, including WhoOwnsCare and Business Buyer Check. Corrections addresses on those sites route to the same log.