Privacy Policy

The short version

The browser tools process supported image files and PDF document properties on your device. Your files are not uploaded to a Metadata Remover processing API, and you do not need an account to inspect, clean, re-scan, or download them.

File processing

• Selected, dropped, pasted, and sample files are read by code running on your device.
• Image cleaning uses a browser worker and encoder. PDF property processing uses qpdf WebAssembly in a browser worker.
• Cleaning creates a new local copy. It does not overwrite the original file.
• Verification re-scans the new copy on your device.
• Downloads are created directly by your browser. We do not receive or retain the file or its metadata.
• Refreshing or closing the page clears the current in-browser workbench session.

PDF tools are limited to the standard Info dictionary and catalog-level XMP. Encrypted PDFs are rejected, and signed PDFs require explicit consent because rewriting invalidates the existing signature. This policy does not describe PDF sanitization or hardening because the current tools do not provide those features.

If we later introduce an optional server-side or account-based file-processing feature, we will describe that behavior before you use it and update this policy.

Site and operational data

Our hosting provider may process standard request information such as IP address, browser type, requested URL, timestamp, and security events to deliver and protect the website. We use Pageview and Google Analytics 4 for aggregate page-traffic measurement. These services may receive the requested page URL, referrer, timestamp, approximate location derived from network information, and browser or device information.

Google Analytics is initialized with analytics and advertising storage denied, Google signals and advertising personalization disabled, and ad-data redaction enabled. When you select, drop, or paste a local file, the page also disables Google Analytics before subsequent file-workflow interactions. We do not configure either analytics service to receive file contents, file names, metadata values, file hashes, cleaned-file download names, or report contents.

We do not sell personal information. V1 does not require payment details or an account to use the cleaner.

Browser storage and cookies

The file tools do not need cookies to process files. Google Analytics is configured without analytics or advertising storage. The site may store a language or theme preference on your device. Essential security or hosting features may also use limited browser storage where required.

Third-party services

The website relies on Cloudflare for hosting and security, Pageview for pageview measurement, and Google Analytics 4 for aggregate traffic measurement. Those providers process the limited site-request or measurement information described above under their own policies. Files selected in the workbench are not sent to these providers by the tools.

Security and your choices

Keeping file processing local reduces transfer and storage exposure, but no browser or device can be guaranteed perfectly secure. Use a trusted, up-to-date browser and a device you control. You can leave the page at any time to clear the current session and can choose not to download a cleaned copy.

Changes

We may update this policy when the product or its data practices change. The date above identifies the latest version.

Contact

A privacy contact address will be added before public launch. Until then, this page describes the current development build and is not a substitute for launch-specific legal review.