Elucora turns a public source into a receipt that someone else can check. That claim is only worth anything if you know who is making it, so this page says who, and what the receipts do not prove.
Elucora is built and operated by one person. There is no team behind a company voice: the same person writes the code, answers support@elucora.com, and is accountable when something breaks.
That is a real constraint and it belongs on the page. It means fast decisions and direct answers, and it means no 24-hour support rota. If either matters for how you would use this, say so before you rely on it.
Code and contributions ↗Sources change. A cited page is edited, a vendor revises history, an announcement is deleted an hour after it moves a market. The work that depended on that source is left unprovable, and the argument becomes one person's memory against another's.
A screenshot is not evidence. A link is a promise the internet does not keep. Elucora preserves the bytes, pins the exact passage or field, signs it, and publishes the entry to a log anyone can inspect.
Questions about whether this fits your workflow, what it cannot do, or what it would take to make it work — all go to the same address, and get answered by the same person.