Security Architecture

Security claims on this page describe the implementation, not guarantees. The design minimizes remote exposure by keeping selected file contents in the browser session.

Browser-local processing

The static site has no upload endpoint, file-processing backend, database, remote storage integration or account system. Selected file bytes are read with browser APIs and processed locally.

Read-only file access

The application reads user-selected files. It does not overwrite or delete the originals. “Clear Workspace” releases application references and indexes; it does not delete device files.

Worker isolation and cancellation

Search, regex, diff and analysis run in dedicated workers. Regex operations have an execution timeout; long-running operations can be terminated.

Archive safeguards

Archive entry counts, expanded sizes, nesting depth and suspicious compression ratios are bounded. Traversal paths such as ../../system/file are rejected and archive symlinks are not followed.

Hostile content

Imported HTML, JavaScript and other source code is displayed as escaped text. The application never evaluates imported code, macros or shell commands.

Content Security Policy

Production headers restrict scripts, connections, frames and object content to the static same-origin application. The policy is included in _headers for Cloudflare Pages.

Verify network behavior yourself

1. Open browser DevTools.
2. Open the Network panel.
3. Add a private sample file.
4. Search for a distinctive phrase inside it.
5. Compare and analyze the file.
6. Inspect requests and confirm the file content does not appear in outgoing request payloads or URLs.