Features
Audit, compliance & verification
A signature is only useful if you can prove it later. AccordSeal records each event in a tamper-evident chain, seals the result, and lets anyone check it.
What it does, and what that is worth
Evidence
- Hash-chained, tamper-evident audit log
Each event includes the hash of the one before it. An integrity-verification endpoint re-checks the chain.
- PAdES seal on every final PDF and certificate
Any change to the sealed PDF invalidates the seal. Until the AATL certificate is in place, PDF readers will not show the seal as automatically trusted.
CAdES detached signature with DocMDP certification.
- RFC 3161 timestamp (DigiCert TSA)
An independent timestamp authority attests when the document was sealed.
- Audit-chain heads anchored by RFC 3161
At regular intervals the state of the whole audit chain is timestamped, so history cannot be quietly rewritten.
- API-initiated events recorded with the credential ID
Actions taken by an integration are attributed to it (actor type “api”), not to a person.
- AATL document-signing certificate
Adobe Acrobat and other AATL-aware readers show the seal as trusted, with no manual steps.
- PAdES LT / LTA (long-term validation)
Revocation data and archive timestamps are embedded, so a seal can still be checked decades later.
Verification
- Public verification portal
Check a document by verification code, by SHA-256 hash, or by uploading the PDF. No account needed.
- Evidence package (ZIP)
Sealed PDFs, the original, audit events with hash inputs, chain links, anchor tokens and SHA256SUMS.
- Data retention controls
Opt-in deletion of completed agreements' content after N years, purge of closed organizations, and dry-run reports before anything is removed.
Run your next agreement from draft to proof.
Start with the Free plan, or ask us to walk your team through AccordSeal with your own documents.