Certified redaction for legal and HR teams
A tamper-evident certificate, PII preflight, and permanent redaction for exhibits, discovery PDFs, and client exports, without routing files through a converter cloud to get there.
Stop routing sealed exhibits and discovery PDFs through free cloud converters. Vault PDF keeps core processing in the browser and gives your team proof to share.
PDF processing runs entirely in your browser using permissive open-source libraries (pdf-lib, PDF.js, qpdf). We do not use AGPL-licensed processing modules. Your files are never uploaded to our servers for core PDF tools.
- Step 1
PII preflight
Scan text locally for common PII patterns. OCR step available for scanned PDFs on Compliance plans.
- Step 2
Permanent redaction
Mark and commit redactions in the PDF editor. Uncommitted marks are blocked before export.
- Step 3
Finish and certify
Strip hidden metadata, download the redacted PDF, and generate a tamper-evident certificate.
Before you share a redacted PDF
- Search the exported final PDF for known sensitive strings
- Try copy/paste near redacted areas
- Confirm metadata and hidden layers were stripped
- Spot-check headers, footers, and repeated table rows
Certified redaction FAQ
Common questions from legal and HR teams using Vault PDF.
No. Black boxes or highlights can leave recoverable text in the PDF structure. Certified Redaction uses committed PDFium redaction that removes underlying content, then strips metadata and issues a certificate.
No. Vault PDF stores workflow metadata only: timestamps, safe client labels, PII category counts, and a SHA-256 fingerprint of the exported file. Filenames, redaction text, and document content are not stored.
It proves the workflow ran in the browser with permanent redaction steps, metadata stripping, and PII preflight metadata. It includes an output integrity fingerprint. It does not certify that every sensitive item was found.
Compliance plans include an OCR preflight step for image-only PDFs. OCR adds searchable text you must still redact manually before export.