Privacy Policy

This policy describes what happens to your files and your data when you use Online PDF Editing. It is written to be read, not to be survived.

The short version

Your PDF and image files are processed entirely inside your own browser. They are not uploaded to us, not stored by us and not seen by us. We collect a small amount of anonymous usage data about which tools are used, and that data never contains your file names or anything from inside your documents.

How your files are handled

Every tool on this site does its work on your device. When you drop a file onto a tool page, the browser reads it into memory on your computer or phone and the processing code runs there. No copy is sent anywhere.

Specifically, we do not:

• upload your files to a server;
• store your files, in any form, for any length of time;
• record your file names;
• read, extract or transmit the text or images inside your documents;
• save your files to your browser's local storage.

Files are held in memory only while you are working, and are discarded when you close or reload the page. There is no “delete my files” step because there is nothing on our side to delete.

What we do collect

We use PostHog analytics to understand which pages and tools people use, where the interface is confusing and where errors happen. The browser sends these analytics requests to this site's first-party `/relay` path, which forwards them to PostHog. This helps us improve the site without requiring accounts or uploads.

The events recorded are limited to:

• which tool page was viewed;
• that a file was selected or removed;
• that a tool was started, completed or failed;
• that a download was clicked;
• that a setting was changed.

Alongside those events we record only coarse, non-identifying details: which tool it was, how many files were involved, a rough size band such as “5–20 MB”, a rough duration band, and whether the device was mobile or desktop. Size and duration are recorded as bands rather than exact figures, because an exact file size combined with a timestamp starts to look like a fingerprint of one specific document.

PostHog may also capture general interaction events and session replay so we can see where people click, scroll and get stuck. Text and inputs are masked in replay. These analytics are about the page and the interface, not about the contents of your PDF.

We will never collect file names, file contents, text extracted from your PDFs, or any personal data from inside your documents. We do not use advertising trackers and we do not sell data.

Accounts

There are none. You do not create an account, give an email address or provide a payment method to use these tools, so there is no account data to protect or lose.

Cookies

We do not run advertising cookies. PostHog may use cookies or local browser storage to understand repeat visits and sessions on this site. Any storage used by the PDF tools themselves is limited to what is needed for the page to function.

Limits worth knowing

Browser-based processing has real constraints, and it would be dishonest to imply otherwise:

• Very large files are limited by the memory your browser is willing to allocate. A file that works on a desktop may fail on a phone.
• Password-protected and encrypted PDFs cannot be processed in this version.
• This site is delivered over the internet, so it is subject to the usual security of your own device, browser and network. Local processing protects your file from us; it cannot protect it from malware already on your machine.

If this changes

Should a future tool ever require server-side processing — for example, a job too heavy to run in a browser — it will be labelled clearly on that tool's page before you use it, and this policy will be updated to say exactly what is sent and why. The promise made on a tool page will always match what the code does.

Contact

Questions about this policy can be sent to contact@pdfediting.online, or raised through the contact page. Please do not attach your documents to that email: nothing on this site needs a copy of them, and describing the file is enough. See also our Terms of Service.