How Docubird keeps documents safe and signatures provable
Signing is a serious act. This page explains how Docubird checks who is signing, protects documents, and proves what happened. Items in [brackets] are details your team must confirm before publishing.
Checking who signs
Every request is sent by emailed link. For more certainty, add an access code you share another way, or a one-time code Docubird emails when the link is opened.
Proving what happened
Each person agrees to sign electronically before filling in anything. Docubird records each view, consent, approval and signature with its time and device.
When the last person signs, the PDF is sealed and a certificate page is added with an independent timestamp. Any change to the file afterwards breaks the seal.
The activity record for each request is chained, so a missing or altered step is detectable.
Controlling who sees it
You choose who can download the signed PDF: everyone involved, your team only, or only people you grant access to.
Links stop working after the time you set.
Where data is stored
[Hosting provider and region, e.g. UK or EU data centres.]
[Encryption in transit (TLS version) and at rest.]
[Backups: frequency and retention.]
How we run the service
[Access controls for staff, and how access is logged.]
[Penetration testing and certifications, if any.]
[Incident response: how and when customers are told.]
Reporting a problem
Found a security issue? Email [[email protected]]. We’ll reply within [timeframe].
Questions
Can Docubird staff read my documents?+
[Confirm the access policy before publishing.]
Can someone check a signed document without an account?+
Yes. The QR code on every certificate page opens a public Check this document page.