Skip to main content
Updated: August 2026
Zero-Trust Browser Execution

Security Architecture & Data Isolation

GainUtility is engineered around memory isolation principles. By executing all document, spreadsheet, and image manipulations locally on your client machine, we eliminate the primary attack vectors associated with cloud file storage.

Client-Side Memory Sandboxing

Files loaded into GainUtility are parsed directly in your browser's dedicated V8 JavaScript heap or WebAssembly sandbox. When you close the tab or click 'Reset', the memory is instantly garbage-collected by your browser.

Strict MIME & Magic Byte Validation

All file pickers inspect binary file headers (magic bytes) to verify true file signatures, preventing malicious disguised file execution or payload tampering.

Content Security Policy (CSP)

The platform is built with strict Content Security Policy directives to block unauthorized third-party scripts, unauthorized eval() calls, and unauthorized outbound data exfiltration sockets.

No Remote Log Buffering

Our server-side edge layers act purely as static asset delivery nodes (HTML, CSS, JS bundles). No application logs containing customer data, filenames, or calculated results are ever buffered on servers.

Verifying Client-Side Execution in DevTools

You don't have to take our word for it. You can independently verify that zero data leaves your machine by inspecting your browser's Developer Tools:

  1. Open GainUtility in your browser (e.g. Chrome, Firefox, Safari, or Edge).
  2. Press F12 or Cmd + Option + I to open Developer Tools.
  3. Navigate to the Network tab and check the 'Preserve Log' option.
  4. Upload an Excel file, compare PDFs, format JSON, or convert images.
  5. Observe that 0 POST, PUT, or WebSocket network requests transmitting your file data occur. All operations happen instantly on the client thread.