For legal, company secretarial and finance teams
When someone disputes what was agreed or decided, show the version as it was.
Which version of the contract was signed? What did the board actually resolve, and was it before or after the announcement? Disputes about agreements and decisions come down to versions and dates.
- When it is tested
- A contract dispute; a shareholder challenging a board decision; an auditor’s or an investigator’s review; disclosure in litigation.
- What you will be asked for
- The exact text agreed or decided, and its date: the signed contract and its annexes, minutes and resolutions, the version of a policy in force at a given time.
- What goes wrong today
- Versions multiply across email and document tools, and a file called final_v7_signed.pdf proves nothing about when it was made or whether it was the final one.
- What changes
- Seal each version when it is agreed, approved or signed. Anyone can later check that a document is the sealed version, and when it was sealed, without seeing any of your other documents.
Sealing shows that a record existed unchanged from a given moment; whether your records are enough is yours to judge. A seal is not an electronic signature and does not replace one; it proves a file existed unchanged from a moment.
Try it in two minutes
- Choose a real file of your own: a signed contract, a set of minutes or a resolution. It is read in your browser and never uploaded.
- Seal it on Seal a file. A free sandbox key is issued on the page; only a salted fingerprint reaches the log.
- Make a copy, change one character in it, and check both against the receipt at Check. The copy fails; the original passes.
From your own systems it is one API call per record. Integrate · Other industries