Browser-only file handling
Selected files stay in this browser only while we inspect metadata and create clean copies.
Trust
We do not include an upload endpoint, account system, database, or backend file processing path in this build. We read file bytes through browser APIs, process them locally, and release them when the page state is cleared.
We keep analytics consent-aware and separate from file processing. We do not send file names, hashes, metadata, dimensions, GPS values, document properties, or file-derived error data.
Privacy principles
Selected files stay in this browser only while we inspect metadata and create clean copies.
We do not require login, file storage, or a database for the metadata remover workflow.
Optional analytics stays separate from file processing and does not receive file-derived data.
We report risky hidden content and signed-file concerns so users can review files before sharing.
Related pages
These pages connect the privacy promise to the actual metadata tools and file-type limits we support right now.
Privacy questions
No. We process selected files through browser APIs, and this build does not include a backend upload endpoint, account system, or file database.
It means the file bytes are read and cleaned in this browser session. The clean copy is generated for you to download locally.
No. We keep analytics separate from file processing and do not send file names, hashes, metadata, dimensions, GPS values, document properties, or file-derived error data.
We show review warnings when hidden or active content needs human attention instead of pretending every risky item can be safely removed automatically.