How documents are sealed
When the last person signs, the fields are stamped into the PDF, a certificate is written and the file is sealed so any later change shows.
Within a minute of the last signature:
Every field's value, tick and signature image is stamped into the document, flattened so it is part of the page.
A certificate of completion is written: the documents and their hashes, every participant with how they were identified and when they acted, the timeline, and a verification code with a QR link.
The files are sealed: a digital seal with a trusted timestamp, in the long-term PAdES format, so the seal can be checked years later. The seal is renewed before its timestamp ages out.
Everyone receives the sealed PDF by email (attached when under 10 MB, otherwise a link) and the envelope keeps it.
What a sealed file proves
That it is the file we issued and that it has not changed since. Open it in Acrobat and the signature panel shows a seal; because our seal is self-issued at launch, Acrobat may say the validity is unknown. The authoritative check is the Check a signed document page on your signing site, where anyone can upload the file or enter the verification code. See verifying a document.
Before completion
Downloads before completion are watermarked not yet signed. What is signed is exactly what was previewed: a generated PDF is stored and hashed once and never regenerated.
Keeping files
Sealed files are stored write-once with their hashes and never overwritten. A renewed seal is stored as a new version beside the earlier ones.