Privacy Policy

How PDF Meta Editor handles files and website requests

Last updated: September 2, 2026

Summary

PDF Meta Editor reads, edits, removes, arranges pages, rotates pages, converts images to PDF, builds image collages, verifies, and prepares downloads locally in browser memory. The current service has no file upload endpoint, account system, payment flow, or cloud file storage. Optional site feedback is stored separately from file processing.

Files and Tool Data

Selected PDF or image bytes, parsed metadata, image previews, field edits, and generated outputs stay on your device. Image-to-PDF tools read JPEG, PNG, and WebP dimensions, redraw supported images in the browser, and prepare a new PDF without sending the source file to this site. Refreshing or closing the page clears the in-memory tool state, subject to ordinary browser behavior.

Your browser may save a downloaded result when you choose the download control. That local download is controlled by you and your browser settings.

Website Requests

Hosting and network providers may process ordinary request data needed to deliver and protect the site, such as IP address, request time, requested URL, user agent, and security events.

Site Feedback

If you send feedback from the site, we store the selected type, the message, the page path, the page language, a short browser or device note, and an optional reply email. Network address is used only as a short-term abuse limit and is not stored with the message. File bytes, file names, metadata values, image previews, and other tool inputs are not attached to a feedback submission.

Cookies and Analytics

On pdfmetaeditor.com, Google Analytics 4, Microsoft Clarity, and Plausible measure website use. Google advertising storage stays denied. In the EEA, United Kingdom, and Switzerland, analytics storage remains denied until you allow it. In other regions, analytics storage is enabled by default unless you decline or withdraw. While analytics storage is denied, providers may send limited cookieless measurements such as page visits, basic interactions, browser and device information, and IP-derived information. Plausible uses no analytics cookies and receives a sanitized page URL that keeps standard UTM campaign parameters while removing other query data.

Product-usage events such as file loaded, process success, process error, download, and metadata tool mode changes use stable tool, operation, stage, and error-code names. Rotate events may also include page-scope and rotation-delta enums. File names, PDF or image bytes, parsed metadata values, image dimensions, preview URLs, page-range text, settings combinations, and full error messages are not sent. File interaction areas are masked in session replay. Use Privacy choices to allow, decline, or revisit analytics cookies; changes apply immediately.

The service does not use analytics to create accounts or process payments. Essential infrastructure may also use security and delivery mechanisms required to serve the website.

Security and Limits

Local processing reduces file disclosure, but no browser environment can be guaranteed completely secure. Keep your browser updated and independently review sensitive outputs.

Changes

This policy may change when the service adds features or data flows. The date above identifies the current version.

Contact

Questions can be sent to support@pdfmetaeditor.com.