LOCAL PROCESSING

Are Files Really Not Uploaded?

Your input files are handled as browser File objects. Tool code reads them locally instead of sending them to a conversion server.

Last updated: October 2, 2026

What happens when you choose a file

  1. The browser gives the page access only to the files you explicitly choose or drop.
  2. JavaScript reads the selected File or Blob in the tab.
  3. Conversion runs in the page, a Web Worker or bundled WebAssembly.
  4. The result becomes a Blob URL and is downloaded or stored in the browser Work Tray.

What goes over the network

The browser requests the page, JavaScript, CSS, fonts if configured, bundled workers/Wasm, and the machine-readable tool catalog. Input and output file bytes are not posted to a SHIAGENT conversion API because no such API is used by these tools.

As with any website, the hosting server may receive ordinary request logs such as IP address, time, browser information and requested URL. See the Privacy Policy.

Work Tray storage

The image/SVG Work Tray and PDF Work Tray use IndexedDB, a database inside your browser that can store files and blobs. Language and custom-workflow preferences use localStorage. Clear a tray in the UI or remove SHIAGENT site data in browser settings to delete them.

How to verify

  1. Open browser developer tools and select Network.
  2. Clear the list, then process a test file.
  3. Filter for Fetch/XHR. You should see no request containing the selected file.
  4. Use Application/Storage to inspect local IndexedDB entries.

Browser extensions, enterprise proxies and modified deployments are outside SHIAGENT's control; verify the deployed origin and HTTPS certificate.