Privacy proof

This tab right now

Requests since this page loaded

–

Browser reports

–

How to verify

1. 1.

   Watch the Network tab

   Open your browser's developer tools, choose the Network tab, then redact a file on the home page. No request appears while the file is processed. The only requests this site ever makes are for its own pages and scripts.

2. 2.

   Read the response headers

   In the same Network tab, select any page request from this site and open its response headers. The Content-Security-Policy below is sent with every response, and the browser enforces it: scripts on this site cannot connect anywhere except this site.

3. 3.

   Go offline and try it

   Load the home page, then turn off Wi-Fi or switch the Network tab to Offline. Redaction still works, because nothing about it needs a server.

4. 4.

   Read the engine

   The redaction engine is a separate package with a build-time boundary test: it cannot import browser networking, DOM or platform code. Its version is printed below so you can match it to the source.

Headers this site sends in production

Content-Security-Policy

default-src 'self'; script-src 'nonce-t3i+cAZ+C7zmk1V27Xfy1Q==' 'strict-dynamic' 'wasm-unsafe-eval'; worker-src 'self' blob:; connect-src 'self'; img-src 'self' blob: data:; style-src 'self' 'unsafe-inline'; font-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'

The script-src nonce is a fresh random value generated for every page load, so no attacker can predict it. It admits only this site’s own scripts; connect-src still allows this site alone, which is the guarantee your files stay in this tab.

Cross-Origin-Opener-Policy

same-origin

Cross-Origin-Embedder-Policy

require-corp

Signing in adds exactly one permitted origin, our authentication and account service; the redaction itself never uses it.