How do you prove an advice document was not modified after the meeting?
Updated on
Seal it when it is approved: compute its SHA-256 fingerprint, timestamp it and keep it. If the document is changed afterwards, even by a comma, its fingerprint changes and the comparison shows it.
Meetingize does this for each final document: the PDF footer carries a seal statement, a link and a QR code that opens a public verification page, without showing the document content.
What is a SHA-256 fingerprint?
SHA-256 is a standardised hash function (NIST FIPS 180-4): it turns any file into a 64-character hexadecimal string. Two different files give, in practice, two different fingerprints, and the file cannot be rebuilt from the fingerprint.
What the seal proves, and what it does not
| Question | Answer |
|---|---|
| Has the document changed since it was sealed? | Yes or no: this is exactly what the fingerprint comparison establishes. |
| When was it sealed? | The timestamp recorded by Meetingize when sealing. |
| Was the advice compliant? | No: the seal does not judge substance. It is a technical record, not a certification. |
| Is it an eIDAS qualified timestamp? | No. Meetingize does not currently provide qualified timestamps from a trust service provider. |
- No "guaranteed legal value".
- No certificate of regulatory compliance.
- No eIDAS qualified timestamp at this time.
Frequently asked questions
Who can verify a sealed document?
Anyone who has the document: the QR code in the footer opens the public verification page, no Meetingize account needed.
Sources (checked on 11 October 2026)
General information, current at the date shown; it is not legal advice.
Read next
Seal your next advice document.
Sealing is available in the web app.