Evidence
Check an evidence pack without opening it
Every evidence pack Declara produces carries a verification code in its footer. Anyone holding the document can check that code here — a regulator, an auditor, an acquirer’s counsel — and confirm the pack is genuine without being shown a single thing it contains.
No pack of your own yet?
Open the sample evidence pack — the same document the product issues, rendered by the same code — read the verification code in its footer, and check it above. It is SAMPLE-PACK, and the result says plainly that it is a sample rather than a customer’s.
What the check proves
That the pack was issued by this service, when it was issued, what it covered, and how many audit entries sit inside the range it certifies. Every action in a workspace is recorded and hash-chained to the one before it, so a removed or altered entry breaks the chain and stops reproducing.
What it deliberately does not show
Nothing about the vulnerability, the product, the company or the filing. A code is a receipt, not a key. Somebody guessing codes learns only that a pack exists, which is why the page can be public at all.
Why a chain rather than a signature
Because the question an authority asks is not “is this file unmodified” but “is this the whole story, in order, including the parts you would rather not show me”. A chain answers that: each entry commits to its predecessor, so a decision cannot be quietly removed from the middle of a case after the fact. Stated precisely, this makes tampering detectable rather than impossible.
The audit trail is what Article 14 compliance is demonstrated with, long after the incident.Art. 14
More on how the chain is built and what the database refuses to do to it is on the security page.