Can your e-signature company read your contracts?
With most e-signature services, yes: they describe encryption in transit and at rest, not end-to-end encryption, so their systems can decrypt and read your documents. Attest is different: every document is encrypted in your browser before upload and can be opened only by the people you send it to, so Attest can't read it.
By DataHubz · Updated October 12, 2026 · 5 min read
Why most services can read your documents
Most e-signature services describe their protection as encryption at rest and in transit. That means two things:
- In transit: your document is encrypted while it travels between your browser and their servers (HTTPS).
- At rest: it is encrypted on their disks, usually with AES-256.
Both are good practices, and with both, the service holds the keys. It can decrypt your document whenever its software needs to, for example to convert it or render it for viewing, as Adobe's security overview describes. Encryption at rest protects against a stolen hard drive. It does not keep your document away from the company that stores it, or from its staff with the right access.
Three kinds of encryption, side by side
| Encryption in transit | Encryption at rest | End-to-end encryption | |
|---|---|---|---|
| Where the document is encrypted | On the connection to the service (HTTPS) | On the service's disks | In your browser, before upload |
| Who holds the key | The service, at its end of the connection | The service (DocuSign also sells customer-managed keys as a premium add-on) | Only the people you send it to |
| What it protects against | Someone intercepting the connection | A stolen disk or backup | The service reading stored documents, and a breach of its servers |
| Can the service read your document? | Yes, once it arrives | Yes, whenever its software needs to | No |
What DocuSign, Adobe, Dropbox Sign and PandaDoc say
As published on their own pages on October 11, 2026:
- DocuSign: "Documents are encrypted in transit and at rest using industry-standard AES-256 encryption". Customer-managed keys are available only through its premium Security Appliance add-on.
- Adobe Acrobat Sign: "All data is encrypted in transit over HTTPS ... Any data stored by Acrobat Sign is encrypted at rest using AES 256-bit encryption", and its document processing service handles "encrypting and decrypting files".
- Dropbox Sign: "All documents are stored and encrypted at rest using AES 256-bit encryption".
- PandaDoc: "Data is encrypted when traveling and at rest".
None of the four describes end-to-end encryption, so their services can decrypt the documents they store. We compared 21 e-signature services in October 2026, Attest and 20 others, and Attest was the only one that end-to-end encrypts every document, for every signer, by default. That comparison quotes what each of the 21 says about encryption.
What end-to-end encryption means
End-to-end encryption means a document is encrypted on your device and can be decrypted only by the people it is meant for. Nobody in between holds a key that opens it, including the company that runs the service.
On Attest, it works like this:
- When you upload a PDF, your browser encrypts it (AES-256-GCM) before it leaves your computer or phone.
- The key that opens it is locked separately for each person you send it to, so only that person can unlock it, with their passkey or recovery phrase.
- Attest stores and delivers the encrypted file. It never has a key that opens it.
- Each signer's browser decrypts the document, and they read it, fill in their fields and sign with their passkey.
Before your browser locks the key to someone, it checks their public key against Attest's public key directory, so not even a key swapped in by Attest would be used.
Only fingerprints go on the public blockchain: short codes calculated from the signed record, which includes the document's own fingerprint, and from the signed pages. A fingerprint identifies exactly which document was signed, and nobody can rebuild the document from it.
What Attest still handles
To deliver a document and prove it was signed, Attest handles the information around the document, as every signing service does: the title, file name, size and type, your note to the signers, your account email, the signers' names and email addresses, where fields are placed and when each step happened. The contents of the document, the text of your contract, stay between you and the people you send it to.
The agreement's certificate shows the title, the file name, the verification code, the fingerprints of the document, the signed copy and the signed state, each signer's name and signing time, the blockchain anchor and each signature's evidence, never the document, and it shows signers' email addresses only to the parties. What each signer's passkey signs carries their name and, in place of their email address, a salted commitment to it (a fingerprint of the address and a secret value Attest gives only to the parties), so the signature evidence carries no email address and the signed copy names signers only by name. The certificate is public by default, so anyone with its link, code or the document's fingerprint can check it, and the sender can make it private, so only the parties see it and anyone else checks a zero-knowledge proof a party shares instead.
Why it matters
Contracts hold prices, salaries, terms, plans and personal details. When a service can read them, your confidentiality depends on that company's internal access controls, its subcontractors and its security, for as long as it keeps your files.
Breaches happen at well-known services too: in 2024, unauthorized access to the Dropbox Sign production environment exposed account details and the names and email addresses of people who had only received or signed a document, and Dropbox reported no evidence that documents themselves were accessed (what an e-signature breach exposes). With end-to-end encryption, the documents stored on a service are unreadable ciphertext, so a breach of the service's servers does not expose what your contracts say.
End-to-end encryption also answers a question that is hard to answer otherwise: whether a service uses your documents to train AI. A service that can't read your documents can't train on them.
How to sign privately with Attest
- Sign in at attest.datahubz.com with your email and set up your signing key with a passkey and a recovery phrase.
- Upload your PDF. It is encrypted in your browser before upload.
- Add the people who need to sign and place their fields.
- Each signer opens their link and approves with a passkey only they control, unlocked with Face ID, a fingerprint or the device PIN. They don't need an account or a password, and they never pay.
- Everyone receives the same sealed copy, which carries its own evidence and a verifier, so anyone can check it for free.
Your first 2 documents are free, in total. After that, the Signing plan is $5 a month for 20 documents.
Questions people ask
- Does encryption at rest mean the company can't read my documents?
- No. Encryption at rest protects the stored files on the company's disks, but the company holds the keys and can decrypt the files whenever its service needs them. Only end-to-end encryption keeps the keys away from the company.
- Can Attest read my documents?
- No. Documents are encrypted in your browser before upload and decrypted only in the browsers of the people you send them to, so Attest stores your document only as ciphertext it can't read. Attest does see the information around it, such as the title, the file name and the signers' email addresses.
- If Attest can't read my document, how does it prove what was signed?
- Each signer's passkey signs a statement that names the document's fingerprint and everything they entered. The signed record, which includes that fingerprint, is anchored on a public blockchain, and anyone holding the document can recompute its fingerprint and check that it matches.
- Do the people I send documents to need special software?
- No. They open their link in a normal browser on their phone or computer, and their browser decrypts the document. They set up a passkey in one step, and they don't need an account or a password.
- Can I keep the fact that I signed an agreement private too?
- Yes. The sender can make an agreement's certificate private, so only the parties see it. A party who signed can still prove that they signed it, and the date it was completed, with a zero-knowledge proof, without revealing the document.
Sources
- Docusign platform safety, Docusign, read October 11, 2026
- Docusign Security Appliance, Docusign, read October 11, 2026
- Adobe Acrobat Sign Security Overview (June 2026), Adobe, read October 11, 2026
- Dropbox Sign features, Dropbox, read October 11, 2026
- PandaDoc AI policy, PandaDoc, read October 11, 2026
- A recent security incident involving Dropbox Sign, Dropbox, read October 11, 2026
- Dropbox, Inc. Form 8-K (May 1, 2024), U.S. Securities and Exchange Commission, read October 11, 2026
Read next
- Which e-signature services can read your documents?
What 21 e-signature services say about encryption, in their words, and which can decrypt your documents. Only Attest end-to-end encrypts them all by default.
- Do e-signature providers train AI on your documents?
What DocuSign, Adobe, PandaDoc, Dropbox and others say about AI and your documents, quoted from their own policies, and why encryption settles it.
- What if your e-signature company shuts down?
What happens to signed documents and their proof when an e-signature vendor shuts down or deletes data, what vendors' terms say, and how to protect yours.
- Document signing
Electronic signatures with a passkey: no account or password for signers, documents encrypted in the browser, and a signed copy anyone can verify.