Privacy notice
Privacy policy
Who operates MetaPurify
MetaPurify is an independently operated web project. Privacy and support requests: privacy@merapurify.com.
The short version
Image files and extracted metadata are processed on your device during normal tool use. They are not uploaded by the tools. Ordinary page and asset requests still reach our hosting/CDN infrastructure.
When you select an image
The browser reads the selected file into memory. Local code and Web Workers inspect metadata, edit containers or decode and re-encode pixels, depending on the tool. Filenames, GPS, EXIF, XMP, IPTC, AI prompts, embedded credentials and outputs are handled locally. Codec and worker downloads retrieve program code; they do not send your selected file.
Results stay in the open page until you replace them, reset the tool or leave it. Links between tools may keep file references in page memory until consumed, evicted or the page closes. Downloads are saved only when you request them and remain under your control. Closing a page is not a secure erasure guarantee for browser or operating-system memory.
Information at a glance
| Information | Received by MetaPurify application? | May reach infrastructure? | Storage | Retention |
|---|---|---|---|---|
| Images, filenames, pixels, metadata, outputs | Browser code only; no server upload | No, in normal tool use | Device memory; requested downloads | No server copy; downloads remain until you delete them |
| IP address, time, page/asset path, browser and request headers | Requests reach the website server | Yes | Hosting/CDN request and security systems | Hostinger keeps server and security logs under its own retention practices. MetaPurify runs no analytics or log database of its own. |
| Tool handoff token | Browser memory lookup; URL may reach server | Yes | URL/history and possible request logs; no image content in token | Browser history under your control; infrastructure retention as above |
| Email you choose to send | Operator mailbox, outside the tool | Email providers | Correspondence | For handling the request and any applicable recordkeeping obligations |
Website requests and infrastructure
Requests deliver pages, fonts, styles, scripts, workers and codecs. Hosting/CDN systems may process IP addresses, request times, paths, browser headers and security events to deliver and protect the website and diagnose failures. The application sends a no-referrer policy for outgoing requests; an initial incoming request can still contain a referrer supplied by another site or browser.
Hosting: Hostinger. Content delivery: hCDN. Hostinger privacy information.
Cookies and browser storage
The application does not set cookies or use localStorage, sessionStorage, IndexedDB or Cache Storage. It has no service worker. Your browser may cache ordinary website assets and keep navigation/download history. Temporary image and download object URLs are released on replacement, reset or unmount; browser-managed caches and saved downloads have their own lifecycle.
Analytics, advertising and profiling
There are no application analytics, advertisements, behavioral trackers, account profiles or cross-context behavioral advertising integrations. No non-essential application cookie or storage feature is present, so the site does not display a cookie consent banner.
Sharing and service providers
Image content is not provided to a server or another service during normal tool use. Infrastructure processing involves the hosting and CDN providers. Hostinger and hCDN may use their own service providers, as described in Hostinger’s privacy policy.
Retention
Hostinger keeps server and security logs under its own retention practices. MetaPurify runs no analytics or log database of its own.
The application has no image database or cloud image storage. If you contact the operator, avoid attaching sensitive images or metadata: email is separate from the local processing workflow.
International processing
Infrastructure processing locations: wherever Hostinger and its CDN operate infrastructure, which can be outside your country. Website requests may cross borders. This does not mean that locally processed image content is transferred internationally by the tools.
Your rights and privacy requests
Depending on the law that applies to you and the operator, you may have rights of access, correction, deletion, objection, restriction or portability and a right to complain to a privacy authority. Contact the operator above. Applicable rights and necessary identity checks depend on the request and jurisdiction.
There are no user accounts, and the operator cannot retrieve or delete a locally selected file that the service never received. Infrastructure logs may not identify a particular visitor reliably; provide the approximate time and page involved without sending the image itself.
Children
MetaPurify is a general-audience image utility and is not directed to children. It does not create accounts or behavioral profiles.
Security and limitations
HTTPS, resource limits and local processing reduce exposure; they do not guarantee anonymity or security. Browser extensions, compromised devices, memory swapping, backups, saved downloads and files you subsequently share are outside the project’s control. Metadata removal cannot remove identifying details visible in the image or guarantee removal of every proprietary or malformed structure.
How claims are tested
Browser regression tests exercise tool actions with synthetic sentinel files and inspect network requests, storage and object-URL cleanup. Parser tests cover malformed input and resource limits. See transparency and testing scope; finite tests do not prove every possible input or browser safe.
Changes
Review dated 2026-09-21: clarified local image processing versus infrastructure requests, browser storage, providers and testing. Changes to data flows require another review and an updated notice.
Effective 2026-09-21 · Last reviewed 2026-09-21