- Supported privacy metadata from the output copy
- Temporary in-memory references after reset or worker termination
- Object URLs after download timeout
PRIVACY MODEL
Your file stays on your device
KillMetadata is designed so that the safest data transfer is no data transfer. The static processor runs locally, and its application scope is cache-only before the file picker becomes available.
THE CLEANING PLAN
Remove what exposes you. Keep what makes the file work.
Every field is shown before the rewrite and classified by action and coverage.
- The untouched source on your device
- Only the functional and structural data the file needs
- Your choice to save or discard the result
- Browser download history
- Operating-system recent-file lists
- Cloud sync configured on your save folder
- Copies you previously uploaded elsewhere
WHY THE ENGINE MATTERS
No server API is in the processing path
The /app/ processor is a static PWA with a restrictive Content Security Policy, including connect-src none. Its service worker verifies the exact JavaScript, WebAssembly and worker allowlist, then serves the processor cache-only.
Every selected file is passed directly to a new Dedicated Worker. Neither input bytes, output bytes nor scan reports are written to browser databases, local storage or an application analytics/error service. Cloudflare may process ordinary page-request and network-security data, but never receives the selected file from the processor.
Explore the complete verification methodology →BEFORE YOU SHARE
A four-step privacy check.
Metadata cleaning is one part of a safe sharing workflow.
- 01Wait for “Offline protection active”
- 02Select one local file
- 03Review the metadata plan
- 04Save or discard the in-memory result
- 05Close or reset the workspace
QUESTIONS, ANSWERED
Know the boundary before you clean.
No vague “100% clean” claim.
Are my files uploaded?
No. The cleaner runs in your browser, has no upload endpoint, and only enables the file picker after its processor assets are available locally.
Is the original file changed?
No. KillMetadata reads the original and creates a separately named cleaned copy. It never overwrites the source file.
Does KillMetadata use analytics or cookies?
No application analytics, tracking pixels, advertising cookies or application-level telemetry/error SDK is part of the processor. Cloudflare may process ordinary delivery and network-security data as described in the Privacy Policy.
Can a saved file sync to the cloud?
Yes, if you choose a folder managed by iCloud, OneDrive, Dropbox or another sync service. That happens after the browser save and is controlled by your device.
Runs locally in your browserReady to inspect your file?
Inspect this file type The picker opens only after offline protection is active.