Why Your E-Discovery Vendor Cannot Prove Non-Tampering (Yet)

Published: April 2026 | 7 min read

E-discovery vendors (Relativity, Logitech, Everlaw, etc.) hold your litigation documents. They promise compliance, security, and audit logs. But here's the uncomfortable truth: they cannot cryptographically prove that a document in their vault has not been tampered with. They have audit logs (who accessed the document, when), but audit logs can be forged by privileged insiders. They have checksums (file hashes), but checksums prove only *current* state, not historical non-tampering. They cannot prove a document sat unchanged in their vault for the past 18 months.

This gap matters in high-stakes litigation. Opposing counsel can always argue: "Your e-discovery vendor's database was compromised. Documents could have been altered and re-hashed. We have no independent proof."

The Current E-Discovery Model

Today's workflow: You produce documents to your e-discovery vendor. They ingest, index, and de-duplicate using SHA-256 hashing. The hash becomes the document's fingerprint. If the document changes, the hash changes—in theory, this is non-repudiation. But the vendor controls the hash. They can:

• Modify a document and recalculate its hash in-database.
• Keep audit logs showing only authorized access (because the modifying user has admin privileges).
• Produce a "forensic image" showing the document was never tampered with (because they control the forensic tools and the data).

This is not a security failure—it's a structural limitation. The vendor has both the data and the proof mechanism. They cannot be truly independent.

The Cryptographic Solution

Sovereign Receipts introduce independent cryptographic proof. Here's how:

At intake: Your documents arrive at the e-discovery vendor and the Clearing House simultaneously. The Clearing House calculates the document's hash (SHA-256) and signs it with ML-DSA-65. The signed hash (the receipt) is stored on an immutable ledger and published to a public bulletin board. The vendor receives a copy of the receipt.

During litigation: If the vendor's integrity is questioned, you produce the Sovereign Receipt. Your auditor can verify: (1) the receipt is signed with the Clearing House's public ML-DSA-65 key (cryptographic proof the Clearing House issued it), (2) the receipt contains the document's hash at intake, (3) the receipt is timestamped, and (4) the receipt is on the public ledger. Now you ask the vendor: "Does the current hash of this document match the receipt hash?" If yes, the document is provably unchanged. If no, the vendor has been caught tampering—and the burden of proof shifts to them.

Why Audit Logs Are Not Enough

Audit logs record claimed history. A compromised vendor (or a vendor pressured by a malicious insider) can modify audit logs after the fact. Cryptographic receipts record mathematical history. The math cannot lie without breaking lattice-based cryptography, which would require solving the Learning With Errors problem—a problem that even quantum computers cannot solve efficiently.

So audit logs are necessary but insufficient. Cryptographic receipts are the gap-filler. Together, they form a two-layer proof: "The audit log says this document was never accessed by untrusted users, AND the cryptographic receipt proves the document hash has never changed."

Implementation in Your E-Discovery Workflow

You don't need to replace your e-discovery vendor. You augment them:

Step 1: When you ingest documents, simultaneously ingest to the Clearing House. All documents are hashed and receipt-signed.

Step 2: Store the Sovereign Receipt IDs in your litigation hold database, linked to the document's Relativity ID (or Logitech URN, etc.).

Step 3: In privilege logs and production records, cite the Sovereign Receipt ID. Opposing counsel can independently verify.

Step 4: If integrity is ever questioned, you produce the receipt. The opposing party can verify offline against the Clearing House's public key. No portal, no vendor involvement, no trust required.

Costs & Overhead

Adding cryptographic receipts to e-discovery adds negligible cost: a few hundred MB of storage for hashes and receipts on the Clearing House, plus an API call per ingested document. The computational overhead is minimal (SHA-256 + ML-DSA-65 signature = milliseconds per document). For a typical litigation with 500K documents, the added cost is zero to the vendor (you're offloading to the Clearing House) and a small API cost to you (thousands of dollars, not millions).

The benefit: independent cryptographic proof of non-tampering, admissible in court, verifiable offline by your auditor or opposing counsel's expert.