Skip to main content

Seal Documents

Qpher Vault seals a document for your organization, so anyone can check it hasn't changed since. On a Personal account the seal is made with your own key.

What the seal proves — and what it does not​

A seal proves two things to anyone who checks it:

  • Where it came from — the seal was made with your organization's key (or, on a Personal account, yours).
  • Unchanged since sealed — any change to the document after sealing, even a single byte, makes the check fail.

It does not:

  • identify which member of the organization sealed the document — the seal is the organization's; the document's access log records which member did it;
  • act as an electronic signature of the kind you give to sign a contract, or verify anyone's identity. The dialog says so before you seal, and recipients see the same statement.

Seal a document on the web​

Documents you send from Send are sealed automatically (Seal: Automatic · tamper-evident seal). To seal a document you uploaded:

  1. Open the document from Documents and select Seal. The Seal this document dialog opens.
  2. Choose the Signature type: Composite Signature — ML-DSA-65 (the default for everyday documents) or Archive Signature — ML-DSA-65 + SLH-DSA-192s (two independent algorithm families; highest assurance, slower).
  3. Read the Acknowledgment — "I understand this seal proves the document hasn't changed since it was sealed. It is not an electronic signature and does not verify anyone's identity." — and select Continue.
  4. Verify it's you with your password or the code from your authenticator app, then select Seal.

If the document was already sealed, sealing it again replaces the earlier seal.

Seal a document on iPhone​

  1. Open the document page, tap ⋮ and choose Sign document (Sign again if it is already sealed).
  2. Tick I agree to digitally sign this document and tap Sign Now.
  3. Confirm with Face ID or your passcode.

When you encrypt a document on iPhone, Sign this document is on by default, so new documents are sealed as they are saved. On every plan except Free, the sheet's Signing Mode also offers Archive (SLH-DSA) and Composite (ML-DSA-65 + SLH-DSA-192s).

How anyone checks the seal​

  • A recipient who opens the document in the browser sees the result above it: Seal valid — "Sealed by organization. The content has not changed since it was sealed." — or Not sealed by the sender, or, if the content was changed, the document is not shown at all.
  • You, in Activity, see Seal valid, Not sealed or Seal could not be verified on each version.
  • A .qpher file carries the sender's seal; the recipient's Qpher checks it before anything is decrypted, and a changed file does not import. See Export & Import.
  • The Sealed badge in your document list on the web (Signed on iPhone) means a seal is on record; Qpher Vault does not re-check it each time you open the document.

Recipients can seal too​

A recipient who opens a document in the browser can Add your seal: the content stays as it is and their seal is added to the same document, so both parties have sealed the identical file. They can instead Reply with a revision — a changed file, sealed with their key and sent back as the next version. On iPhone, a document shared with you with download permission offers Counter-sign. See For recipients.

Organizations: a member joins or leaves

The seal is made with the organization's key. If the member who sealed a document later joins or leaves the organization, checking that seal through Qpher may fail.

How it works​

The seal is a post-quantum digital signature. The default is a composite signature built around ML-DSA-65 (NIST FIPS 204); the Archive type adds SLH-DSA-192s (NIST FIPS 205) from a second algorithm family. The organization's private key is generated and used only inside Qpher's isolated key service and is never exported. Checking a seal through Qpher needs the signing key to be active or retired; once a key is archived, Qpher can no longer check its seals. See Trust Model and Non-Exportable Keys.

Plans​

Sealing and countersigning work on every plan, including Free. The Archive type needs a paid plan.