Skip to main content
Your source document stays on your device
Built for paralegals, litigation support teams, FOIA and records officers, compliance and HR teams, and healthcare and research teams. Legal workflows can redact court productions and exhibits in a browser-processed workflow reviewed before release.

Redact documents without uploading them

Redact PDFs, Word, Excel, PowerPoint, and image files in your browser. Your source document is not uploaded to RedactVault servers during the redaction workflow.

Want proof? Open the demo and watch the Network tab: the source file is not posted to RedactVault for redaction.

Read The Details

The main product difference is simple: sensitive documents stay in your browser instead of being uploaded to external servers for processing. Read the security and limitations pages for the full explanation.

No upload for redactionProcessed in your browserReview before export
RedactVault detecting sensitive data in a documentRedactVault with redactions applied
Review workflow
PDF first; also supports Word, Excel, PowerPoint, and images
No document uploads in the core workflow
Review before export
For legal teams and other privacy-sensitive workflows

What This Means In Practice

RedactVault is built for teams that do not want to upload sensitive documents to a vendor server just to redact them. Legal is a strong fit, and the same workflow also suits other privacy-sensitive document work.

Processed In Your Browser

In the redaction workflow, sensitive documents are processed in your browser instead of being uploaded to external servers for processing.

Verified Before Release

After export, RedactVault re-checks the reviewed terms and shows a verification panel with pass, review-needed, or limited-verification results.

Certificate And Audit Record

Exports include a redaction certificate and hash-chained audit log so the source/output hashes, rule set, cleanup summary, and review record can be checked later.

Offline Verifier

The standalone verifier recomputes file hashes in the browser and can check certificate binding, output integrity, and audit-log tamper evidence without uploading files.

Why teams choose RedactVault

Legal teams are a strong fit, and the same benefits matter in other privacy-sensitive workflows where teams do not want to upload sensitive documents to a vendor server just to redact them.

No Uploads In The Core Workflow

In the redaction workflow, sensitive documents stay in your browser instead of being uploaded to external servers for processing.

Verify Before Release

The download-ready panel summarizes post-export checks, reviewed-term matches, metadata cleanup, and audit-log inclusion before you share a file.

Find Common Patterns Before Human Review

RedactVault uses more than one detection method to surface common patterns and candidate matches, then shows the results for review. OCR and detection can miss poor scans, unusual layouts, or context, so human review is still required.

Redact A Folder With One Rule Set

Paid plans can process selected files or folders with one rule set, including a representative-file review step before the full batch runs.

Keep A Record Of What Was Checked

Downloadable certificate and audit artifacts record hashes, reason-code counts, verification results, and metadata cleanup details, helping show what was checked before release. They do not certify that every sensitive item was found.

Check It Offline

The verifier page can run locally against the source file, redacted file, certificate, and audit log so the proof does not depend on our server.

No Per-Page Redaction Fees

Paid plans are priced by plan, not by page or by document, so costs are easier to predict.

How RedactVault differs from cloud redaction

Many redaction tools upload files to a vendor server before processing them. In RedactVault's redaction workflow, sensitive documents are processed in your browser without an external upload-and-process step.

Where does the file get processed?

Cloud: On the vendor's servers

RedactVault: In your browser

Do you have to upload the source file for redaction processing?

Cloud: Usually yes

RedactVault: No

Where are document contents handled during processing?

Cloud: In the vendor's systems

RedactVault: In your browser session

Vendor-side exposure to source document contents during processing

Cloud: Possible

RedactVault: Avoided by design

Does it work without connectivity?

Cloud: Usually no

RedactVault: Limited offline support in some paid active-session workflows

How RedactVault works

Open a file in your browser, review suggested redactions, make any manual changes, and export only when you are satisfied. In the core workflow, sensitive documents are processed in your browser, not on RedactVault servers.

1

Open Your File

Choose a PDF, Word, Excel, PowerPoint, or image file. In the core workflow, it is processed in your browser and your original file is not changed.

2

Find Sensitive Content

RedactVault looks for likely sensitive content and shows suggested redactions for review.

3

Review And Edit

Keep, remove, or add redactions so the result matches what you want to share.

4

Export The Reviewed File

Download the reviewed file only after you have checked the result.

What to know before you use RedactVault

The main promise is simple: in the core workflow, sensitive documents are processed in your browser without an external upload-and-process step. This section highlights the key limits and links to the pages with the full details.

Proof artifacts

What the product records after export

  • Source document contents are not uploaded to RedactVault servers for redaction processing
  • The export verification panel re-extracts the output and reports whether reviewed terms still appear
  • The certificate records input/output hashes, engine details, verification results, and metadata cleanup
  • The hash-chained audit log makes later edits to the review record detectable
  • The offline verifier can recompute file hashes locally without uploading the files
  • Accounts, billing, analytics, and support still rely on normal web services
  • You still review the result before sharing a file

Redaction certificate

Downloaded with exports as JSON, including file hashes, rule-set hash, app/engine versions, verification state, and metadata-cleanup summary.

Verification panel

Shown after export with reviewed-term checks, sensitive-looking text counts, cleanup channels, and limited-verification warnings when applicable.

Hash-chained audit log

Records review actions with previous-hash and entry-hash fields so an audit log loaded into the verifier can be walked for tamper evidence.

Offline verifier

Runs from a static page, recomputes hashes in the browser, and checks the certificate against the source and redacted files.

Verify the workflow in DevTools

This recording shows the Network tab while a sample file is processed and exported, with no document-content upload request in the redaction workflow.

Account, billing, support, and analytics can still use normal web services. The proof point here is that source document contents are not posted to RedactVault servers for redaction processing.

Built for

Strong fit

Legal Teams

Review productions, exhibits, and client materials without uploading sensitive documents to a vendor server for processing.

Litigation Support

Work through discovery and case files in a workflow where sensitive documents are processed in your browser, not sent to an external processing service.

Also useful for

Records & Compliance

Prepare public records, internal review files, and compliance documents without uploading sensitive documents to a vendor server for processing.

HR & Operations

Review employee, vendor, and internal records without uploading sensitive documents to a vendor server for processing.

Other teams

Finance

Review statements, onboarding files, and customer records without sending sensitive documents to a vendor server for processing.

Healthcare & Research

Prepare sensitive records for sharing, review, or publication in a workflow where sensitive documents are processed in your browser, not sent to an external processing service.

Legal wedge

Legal is the clearest current use case

Use the dedicated legal pages if you want a tighter workflow fit and a clearer decision-stage comparison.

Legal workflow page

See the legal redaction fit directly

Read the page built for legal ops, paralegals, litigation support, and firms that want a privacy-sensitive redaction workflow without narrowing the whole homepage into legal-only copy.

Decision-stage comparison

Compare RedactVault with Adobe Acrobat

Use the comparison page if your team is already choosing between a general PDF platform and a redaction-focused workflow.

Common questions

Straight answers on files, limits, and plans

In the redaction workflow, sensitive documents are processed in your browser and are not uploaded to RedactVault servers for processing. Accounts, billing, analytics, and support still rely on normal web services, so the security and processing details explain those limits separately.
RedactVault supports PDF, Word (.docx), Excel (.xlsx), PowerPoint (.pptx), and image files including PNG, JPG, GIF, and TIFF. File-specific limits vary, so check the product, security, and limitations pages for details.
RedactVault is designed to make exported redactions permanent, not just visual overlays. For PDFs, the export is verified and either removes matched content natively or converts fallback pages to images so hidden text is not left behind. For Word, Excel, and PowerPoint files, redacted text is replaced in the document package and verified. For image files, redactions are written into the exported image pixels and metadata is stripped. You should still review the exported file before sharing it.
Yes. AI redaction runs in your browser on your device, not on our servers. Because it uses your own hardware, it can take longer on slower machines or larger files, and you can cancel the run at any time.
Professional and Business users can keep using core processing offline if they sign in while connected and keep the app loaded. Offline use is limited to an active session, so a fresh app load or cold browser restart without connectivity is not supported. Accurate and Face detection are unavailable offline, and stats, sync, and billing-related features resume when you reconnect.
Detection is there to help review, not replace it. Accuracy depends on document quality, file type, OCR conditions, and the kind of content being searched, so you should review detections before export.
You can review suggested redactions, reject them, add manual ones, and adjust the result before export. Custom detection patterns and sensitivity tuning are not available yet.
Yes. New accounts get a 2-month free trial on the Personal tier with basic redaction features and up to 3 documents per month, no credit card required. When the trial ends, upgrade to Professional to keep processing. Professional and Business also offer a paid trial, but starting that requires Stripe Checkout and payment details.
In the core workflow, sensitive documents are processed in your browser instead of being uploaded to RedactVault servers for processing. RedactVault still uses web services for accounts, billing, analytics, and support. Review the trust pages for those details before use.
RedactVault is a web app built for desktop Chrome and Edge. Mobile browser support is still in development, so it is best used on a computer today.

Redaction guides

Read before you redact

Plain explainers on what proper redaction does to a file, where common tools quietly fail, and how to check a document is safe to share.

All articles

Ready to reach first export?

Start with the security and processing details, then move into the product. No credit card for the free plan.