Data corrections

Email hello@varamir.com with as much of the following as you have. The first two are enough to start.

You do not need an account, and you do not need to be the company in question. A reader who spots a bad entity match is doing the same useful thing an issuer's IR team is.

• The claim is traced back to its stored source: for a relationship, that is the filing and the verbatim sentence it was extracted from.
• If the source does not support the claim, the claim is removed. Extraction errors are deleted outright rather than annotated: a wrong edge left standing with a caveat is still a wrong edge on a public page.
• If the source does support the claim but the underlying fact has since changed, the claim stays with its original filing date attached, because that date is what it was always asserting: what a company disclosed, and when. See methodology on dates and staleness.
• If the error came from how the pipeline reads filings rather than from one filing, the gate that let it through gets fixed, which usually corrects other companies at the same time.

• A company's own announcement outranks an estimate. This is already automatic for earnings dates: a date confirmed by the company wins over an estimated one wherever the two disagree, and the interface says which kind it is showing.
• A filing outranks everything else. A relationship exists on Varamir because a company put it in writing to a regulator.
• Where a counterparty's filing and a subject's filing describe the same relationship differently, both are shown from their own side, labelled with who disclosed which, rather than being silently merged into one claim neither party actually made.

Corrections are about factual errors in published data. Two things fall outside that, and are better raised directly:

• Removal requests for accurate filing-sourced data. A correctly extracted, correctly cited disclosure from a company's own public filing is a matter of public record. Write to the address above if you believe there is a reason it should not appear, and it will be read; but accuracy is the standard applied, not preference.
• Account, billing and access questions. Same address, and they are handled straight away rather than going through this process.

There is no guaranteed response time and no formal appeals process. A specific, sourced report of a wrong claim is the most useful message this project receives, and it gets acted on.