← Back to RedactVault Home
INDEPENDENTLY VERIFIABLE SECURITY

Don't trust our privacy policy—verify 0 bytes uploaded in 10 seconds.

How RedactVault enforces zero cloud uploads at the browser level using Content-Security-Policy: connect-src none and Forensic Self-Audit verification.

Quick Answer

RedactVault enforces zero cloud uploads at the browser level using the HTTP header Content-Security-Policy: connect-src 'none' on /app/*. Even if JavaScript attempted an outbound fetch or XHR, the browser physically blocks it. Every exported PDF is also forensically re-parsed locally to prove 0 hidden text bytes and 0 metadata fields remain.

How It Works (100% Free & Offline · 0 Bytes Uploaded)

Open /app/, press F12 → Network Tab (or enable Airplane Mode), drop our sample W-2 PDF, and click Permanently Redact. Chrome and Safari physically enforce connect-src 'none' so zero bytes can leave your device.

  1. Open /app/ and inspect the HTTP response headers (or open DevTools → Network Tab) to confirm Content-Security-Policy includes connect-src 'none'.
  2. Disconnect Wi-Fi / enable Airplane Mode, drop any PDF (or click "Load Sample W-2"), and run a redaction.
  3. Confirm 0 bytes transmitted in the Network Tab and inspect the generated SHA-256 Forensic Zero-Leak Proof Certificate.
Open Free Offline Redaction Vault Now →

Frequently Asked Questions

What does Content-Security-Policy: connect-src 'none' guarantee?

It instructs the browser security sandbox to block all fetch(), XMLHttpRequest, WebSocket, and EventSource connections from the /app/ workspace, making silent file exfiltration technically impossible at the browser layer.

How does the Forensic Self-Audit verify zero leaks?

After flattening every page to pixels and rebuilding a fresh PDF with pdf-lib, RedactVault re-parses the output PDF bytes locally to verify 0 extractable text bytes and 0 Info/XMP metadata fields exist, then computes a SHA-256 digest of the clean file.