Security Sandbox Blueprint

100% Client-Side Processing Architecture

Traditional online tools upload your files (such as confidential legal PDFs, client invoices, or raw images) to remote web servers. This introduces leakage risks.

Toolchi utilizes W3C Client-Side File APIs. When you select a document:

1. Your browser loads the file bytes directly into isolated tab memory (RAM) via a FileReader stream.
2. Calculations (like resizing image pixels, stripping EXIF tags, or merging PDF streams) are processed using local Javascript libraries (such as pdf-lib) and HTML5 Canvas contexts.
3. The output file is compiled dynamically and made available for instant download using sandboxed blob paths (URL.createObjectURL).

Local RAM Buffer Isolation

Because all calculations occur strictly in active tab RAM, closing the browser tab automatically terminates the memory allocation. The operating system immediately reclaims the RAM, leaving zero trace of your documents, code inputs, or private graphics on the local hard drive or the internet.

Disconnecting the Internet (Offline Audit)

You can verify this architecture yourself. Load the Toolchi Workspace, turn off your device's Wi-Fi connection, and run any file conversion or compression task. You will notice that everything compiles successfully without any network requests.