Corrections and record discrepancies
Help identify a specific error with a supporting source.
Last updated · 14 October 2026
What to send
Email corrections@corpintel.io with the page URL, the exact field or sentence disputed, the proposed correction and a supporting official document or primary source. Include the document’s reporting or effective date where available.
Do not send passwords, payment details or unnecessary personal documents. A public source link and the specific disputed fact are preferable to a large document bundle.
What a correction can address
Reports can concern factual article errors, incorrectly rendered dates or amounts, a mismatched CIN or DIN, an outdated source observation, or an unsupported interpretation. Conflicting observations need dates and source evidence; an older entry may need historical context rather than deletion.
A missing field does not prove that the underlying event did not occur. If the official source differs from CorpIntel, provide that source so the discrepancy can be evaluated.
Response and publication
CorpIntel does not currently provide a professional content-review service or guarantee an acknowledgement or resolution within a fixed number of working days. Earlier fixed service-level promises have been removed. Reporting an issue does not certify that a correction has been accepted or completed.
Material article corrections carry a dated explanation and an updated content date. Those dates describe an actual content change, not professional review or verification of every linked company. The October 2026 corrections withdraw unsupported statistics and interpretations and correct outdated explanations.
Official records and other requests
CorpIntel can address its own presentation and collected records; this channel cannot change the official MCA register. A request concerning an official filing may require the process provided by the relevant authority.
For a privacy or removal request, use the contact and process in the privacy policy and terms. Public availability alone is not a promise that every request will be accepted or refused. Requests require assessment in their actual circumstances.
Read the data-source and accuracy limitations before relying on a directory observation.