FilePilot.inBrowser File Utilities
Privacy-First Architecture

Privacy Policy

Last updated: October 2026 • Effective immediately

The FilePilot Promise: We believe your documents, invoices, legal contracts, and personal photos belong exclusively to you. All core file operations across FilePilot run entirely within your local browser sandbox.

1. How File Processing Works

Unlike typical online converter websites that transfer your files to a cloud database or processing server, FilePilot executes transformations locally using browser APIs:

  • Images: Decoded, transformed, resized, cropped, and re-compressed using the HTML5 Canvas 2D and Blob APIs directly in your local GPU/CPU memory.
  • PDFs: Parsed, combined, rotated, and split using WebAssembly and client-side JavaScript via pdf-lib.
  • Zero Network Transfer: Your file bytes are never dispatched over HTTP/HTTPS to our servers or any third-party infrastructure.

2. How You Can Verify This

You do not have to take our word for it. Any user can easily verify our client-side architecture using standard developer inspection tools:

  1. Open your browser's Developer Tools (F12 or right-click and choose "Inspect").
  2. Switch to the Network tab.
  3. Drag and drop a file and click "Compress", "Merge", or "Convert".
  4. Observe that zero POST or PUT network requests with file payloads are dispatched.

3. Information We Collect

We collect the absolute minimum data required to serve static web assets and monitor general site reliability:

  • Standard Web Server Logs: Standard anonymous web traffic telemetry (IP address, user agent, requested static file URL, referring page) collected automatically by our hosting CDN (Cloudflare) to detect abuse and protect against DDoS attacks.
  • No File Telemetry: We never log file contents, file metadata, names, dimensions, or thumbnail previews.
  • No User Accounts: We do not store email addresses, passwords, or personal profiles.

4. Cookies and Local Storage

FilePilot does not use persistent tracking cookies, fingerprinting scripts, or cross-site tracking beacons. If any local storage is used, it is solely for remembering temporary UI preferences (such as your chosen default compression quality).

5. Memory & Browser Limitations

Because your files exist solely in active device memory, closing your browser tab or clicking "Reset" immediately clears any in-memory references and releases system memory. Object URLs generated for downloads are programmatically revoked.

6. Questions & Contact

If you have questions regarding this privacy policy or suggestions for enhancing browser security, please visit our Contact page.