Security and Privacy Report

How It Works: The "Sandbox" Approach

Most online tools require you to upload your files to their servers. This means your sensitive documents, personal photos, or financial statements leave your computer and travel across the internet to a stranger's hard drive. Even if they promise to delete it later, you have to take their word for it.

OfflineCompress is different.

We use advanced browser technologies like WebAssembly (Wasm) and the HTML5 FileReader API to bring the "server" to you. When you "upload" a file on our site, it never actually leaves your device. Instead, our website sends a small packet of code (the tool) to your browser, which then processes your file locally.

Technical Details for the Curious

1. The FileReader API

We use the standard browser FileReader API to access the bytes of the file you select. This API creates a secure link between your file system and the browser tab, strictly controlled by your user action (the specific click or drag-and-drop).

2. WebAssembly (Wasm)

For complex tasks like PDF compression or image resizing, we use WebAssembly. This allows us to run high-performance code (often written in C++ or Rust) directly in JavaScript. Libraries like pdf-lib and browser-image-compression run entirely within your browser's memory sandbox.

3. Ephemeral Memory

Once you close the tab or refresh the page, all data related to your files is instantly wiped from the browser's memory. We do not (and cannot) retain any copies because we never received them in the first place.

Why This Matters

• GDPR & CCPA Compliance: Since we don't collect data, we eliminate the risk of data breaches.
• Corporate Security: Safe for use with confidential business documents (NDAs, contracts).
• Personal Privacy: Your family photos and ID scans remain yours alone.

---