100% Client-Side Architecture

How to Verify Zero-Upload Privacy

Don't just take our word for it. You can independently verify that SafeWebUtil never transmits your files across the network using standard browser developer tools.

Self-Verification Steps (Chrome / Edge / Firefox / Safari)

Open Browser DevTools

Press F12 or Ctrl + Shift + I (Cmd + Option + I on macOS).

Switch to the "Network" Tab

Navigate to the "Network" panel and check the "Preserve log" option.

Perform Any File Operation

Upload any PDF or image and run a compression, merge, or OCR extraction.

Inspect the Network Request Log

Observe the traffic: You will see exactly ZERO (0) POST, PUT, or PATCH requests containing file payload bytes.

Technical Guarantees

1. Zero Remote File Uploads

Files selected in any tool workspace are read directly into browser memory (ArrayBuffer/Blob) via the HTML5 File API.

💡 No POST / PUT requests are dispatched when selecting, manipulating, or downloading files.

2. Client-Side WebAssembly & Web Workers

PDF manipulation (pdf-lib), image compression, and OCR (Tesseract.js) execute within sandboxed browser Web Workers.

💡 Heavy processing runs on local CPU/GPU threads without blocking UI or sending telemetry.

3. No Server-Side Storage or Databases

SafeWebUtil is hosted on Cloudflare Pages static edge network with no backend database, no session cookies, and no file storage bucket.

💡 Cloudflare Pages serves pure static assets (HTML, CSS, JS, WASM).

4. Privacy-Safe Analytics Policy

We do not collect file names, file contents, image dimensions, extracted OCR text, or user input strings.

💡 Analytics events only record coarse page views and tool initiation counts.