EveryToolsInstant
Zero-Upload Architecture

Privacy Policy

Our privacy claims are technically verifiable engineering facts, not decorative marketing promises.

Summary in Plain English

When you use EveryTools utilities (formatting JSON, converting CSV, diffing text, resizing images, splitting PDFs, generating passwords, or hashing files), your data is processed entirely within your computer’s web browser. It is never uploaded to, transmitted across, or stored on our servers.

1. Client-Side Execution Sandbox

Standard online converter tools require you to upload your files to a cloud server, where background workers process the file and return a download link. This architecture creates massive privacy risks: your company financial spreadsheets, proprietary code, and personal records sit on someone else's disk.

EveryTools takes the opposite approach. We write our utility engines in native TypeScript, WebAssembly, and standard browser Web APIs:

  • JSON, CSV, Text Diffs, and Regex: Computed via the browser's JavaScript V8/SpiderMonkey engine in volatile memory.
  • Image Resizing & WebP Conversion: Rendered and re-encoded using the HTML5 Canvas 2D and WebAssembly image codecs directly on your GPU/CPU.
  • Passwords & SHA-256 Hashes: Generated using the W3C Web Crypto API (window.crypto.getRandomValues and SubtleCrypto.digest), drawing true entropy from your local operating system kernel.
  • PDF Manipulation: Executed using client-side binary stream manipulation within your browser tab.

2. Data We Do Not Collect

  • We do not collect, view, log, or store your input text or code snippets.
  • We do not collect or store your uploaded image or PDF files.
  • We do not log or transmit passwords, keys, or cryptographic hashes produced by our tools.
  • We do not sell user data to data brokers or advertising networks.

3. Cookies and Local Storage

EveryTools uses minimal browser localStorage strictly to remember your preferences (such as dark/light mode and tool settings). These settings remain entirely on your device. We do not use persistent cross-site tracking cookies.

4. How to Verify Our Claims Independently

You do not need to take our word for it. You can inspect EveryTools execution directly:

  1. Open your browser Developer Tools (press F12 or Cmd+Option+I).
  2. Navigate to the Network tab.
  3. Select the Fetch/XHR or WS filter.
  4. Paste a dataset or convert a file in any EveryTools utility.
  5. Notice that zero HTTP POST/PUT requests or web-socket frames are initiated. All computation occurs in local memory.

5. Contact Us

If you have questions regarding our privacy architecture, reach out via our GitHub repository or contact team at everytoolsyouneed.com.