Trust

Privacy-first metadata removal

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.

Analytics boundary

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

How we keep file cleanup private

Browser-only file handling

Selected files stay in this browser only while we inspect metadata and create clean copies.

No account or database

We do not require login, file storage, or a database for the metadata remover workflow.

Consent-aware analytics boundary

Optional analytics stays separate from file processing and does not receive file-derived data.

Clear audit-only warnings

We report risky hidden content and signed-file concerns so users can review files before sharing.

Related pages

Continue with a browser-only metadata workflow

These pages connect the privacy promise to the actual metadata tools and file-type limits we support right now.

Privacy questions

Questions people ask before trusting a metadata remover

Are selected files uploaded?

No. We process selected files through browser APIs, and this build does not include a backend upload endpoint, account system, or file database.

What does browser-only processing mean?

It means the file bytes are read and cleaned in this browser session. The clean copy is generated for you to download locally.

Can analytics see my file details?

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.

Why do we show review warnings?

We show review warnings when hidden or active content needs human attention instead of pretending every risky item can be safely removed automatically.