A local engine built for metadata cleanup
The metadata engine used by MetaRemove was developed specifically for browser-based cleanup workflows. It reads the selected file in the browser, inspects known metadata structures and writes a cleaned copy locally.
- The file is read from your device through the browser file picker.
- Metadata cleanup runs client-side instead of through a server upload workflow.
- The cleaned output is created as a new browser download.
What is not collected from your files
When a tool is running locally, MetaRemove does not need the original video, image or document content to process it on a server.
- We do not store the selected media file.
- We do not need to view the file contents.
- We do not retain cleaned copies of locally processed files.
Site analytics are different from file data
Like most web apps, MetaRemove may collect basic product analytics such as page views, locale, browser type and subscription events. That is separate from the private file content you select for local processing.
- Analytics help understand page performance and product usage.
- File content and file metadata are not the same as website analytics.
- Sensitive files should still be handled according to your organization policy.
Limits of metadata removal
Metadata removal reduces exposure of common file metadata. It should not be described as absolute anonymity or a forensic guarantee.
- Visible content, audio, watermarks and context inside the media are outside ordinary metadata fields.
- Some formats can contain uncommon private tags or proprietary structures.
- For highly sensitive cases, combine metadata removal with your own operational security review.