Zero-Upload Privacy Policy

1. The Core Invariant: Client-Side Processing

At MetadataRemover.in, file confidentiality is grounded in our software architecture. All file inspection, metadata parsing, and binary sanitization operations execute strictly within an in-browser Web Worker sandbox on your local device.

Your photos and files are not uploaded to, processed by, or stored on remote servers or third-party cloud infrastructure.

2. Technical Execution Sandbox

When you select or drop a photo into MetadataRemover:

• Your browser allocates a local in-memory ArrayBuffer for the selected file.
• Ownership of this buffer is transferred directly to a background Web Worker sandbox without network transmission.
• The sanitized result is compiled into an in-memory Blob and downloaded directly to your local storage.
• All intermediate memory object references and URLs are promptly revoked.

3. Zero File Telemetry & Zero Tracking

We do not operate server upload endpoints for user files. We do not run third-party advertising pixels, behavioral trackers, or analytics scripts that monitor file names, dimensions, or embedded metadata contents.

4. Service Worker Role

Our Service Worker serves solely to cache static application code (HTML, CSS, JavaScript, and fonts) so that the utility remains functional offline. The Service Worker never intercepts, caches, or inspects user files.

5. Independent Verification Method

You can empirically verify our client-side processing architecture at any time using standard browser inspection tools:

1. Open your browser Developer Tools (F12 or Ctrl+Shift+I / Cmd+Opt+I).
2. Navigate to the Network tab.
3. Drop an image into the cleaner and click "Sanitize & Remove Metadata".
4. Observe that no POST, PUT, or binary upload requests are dispatched to any server.
5. Alternatively, disconnect your internet connection or enable Airplane Mode after loading the page — the cleaner continues to sanitize files locally.