iLovePDF is a legitimate EU company with the broadest tool selection of any free PDF service, and for most of what people use it for the honest answer is: go ahead. This page is about the cases where that is the wrong answer, and it spends most of its length on something the usual privacy review skips entirely, which is what else is inside the file you are about to upload besides the pages you can see.
We build a browser-based competitor, so we have an obvious interest here. We have tried to write the parts you can check for yourself rather than the parts you would have to trust us on.
iLovePDF processes files server-side. Your browser sends the document over HTTPS, their software does the work, and you download the result. This is not a criticism; it is what allows a tool list that a browser could not host, including repair of damaged files, Bates numbering and a conversion stack heavier than anything that fits in a tab.
You can confirm the upload in about thirty seconds, on their tool or ours. Open developer tools with F12, switch to the Network tab, clear it, then run an operation. A server-side tool produces a request roughly the size of your file. A browser-only tool produces nothing after the initial page load. The stronger version of the test: load the page, turn off your network, and try to work. Local tools carry on. Cloud tools stop immediately.
What the retention policy, the encryption and the deletion window do is reduce how much risk that copy carries. What they cannot do is make the copy not exist. That distinction matters only for a specific class of document, and the rest of this page is about identifying which class yours is in.
A PDF is not only its pages. Every PDF carries an information dictionary, and usually an XMP metadata block, holding fields such as Title, Author, Subject, Keywords, the application that created the content, the software that wrote the PDF, and creation and modification timestamps. Most people have never looked at theirs.
The Author field is the one that catches people out. When you export a PDF from Word, Pages or LibreOffice, that field is usually filled in automatically from your operating system account name. Timestamps record when the document was really written, which is occasionally awkward when a document was supposed to have been prepared earlier. And the Producer field identifies your exact software and version, which is minor on its own and useful to anyone building a picture of you.
You can read all of this without any tool: in Acrobat or most readers it is under document properties. On a
command line, exiftool yourfile.pdf prints the lot. Do that once on a document you are about to
send to a stranger. It is a more instructive exercise than reading any privacy policy.
When you upload a file to any online tool, this travels with it. Whether that matters depends on the document, but it is worth knowing that the sensitive part of a PDF is not always on the page.
There is a trap here worth knowing about. exiftool -all= file.pdf appears to delete PDF
metadata, and the tool will then report the fields as gone. But exiftool writes PDF changes as an
incremental update appended to the file rather than rewriting it, so the original values are still present
in the earlier revision inside the same file and can be recovered. exiftool documents this itself. To
genuinely remove the metadata you have to rewrite the document afterwards, for example with
qpdf --linearize, or use software that rebuilds the file from scratch.
Which brings us to an honest disclosure about our own tool. RaptorPDF has no metadata editor, and we would not pretend otherwise. What it does have is a side effect: most of its tools, including merge, split, annotate, page numbering and compression, rebuild the document from a new empty PDF and copy the page objects across. The original information dictionary is not copied, so Title, Author and Keywords are dropped and the Producer field ends up naming the library we use. Two tools behave differently because they load the original document rather than rebuilding it: password protection and form filling both preserve the original metadata. So "merge a file with itself to strip metadata" works, and "password protect it to strip metadata" does not. That is a quirk rather than a feature, and if metadata hygiene is a real requirement for you, use exiftool followed by qpdf, or Acrobat, which has a proper interface for it.
iLovePDF is an EU company, and EU establishment means GDPR applies directly: a documented lawful basis for processing, data subject access rights, breach notification duties, and a published privacy policy. That is a meaningful baseline and better than none.
What it does not mean is that your file was never on their servers. GDPR governs how a processor handles data; it does not make the processing local. It also does not, by itself, give you a data processing agreement. Free tiers of consumer services generally do not come with one, and if you are handling someone else's personal data in a professional capacity, the absence of a signed agreement is usually the fact that settles the question before you have evaluated anything else.
When you do read a policy, four clauses carry the weight: the retention period expressed as a number of hours, the subprocessor list, the jurisdiction and cross-border transfer mechanism, and whether a processing agreement is available on your plan. Everything else is context.
Anything already public or with nothing personal in it: a published paper, a brochure, a government form, slides for a talk. Here iLovePDF's much larger tool list is a straightforward advantage, and choosing a local tool on privacy grounds would be choosing a worse tool for no benefit.
Contracts, internal reports, anything with a colleague's name in it. The vendor is very likely fine. Most organisations classify their data and restrict which classes may go to unapproved external services, and this is by far the most common way people get into trouble with online PDF tools. Check the policy, not the privacy page.
Patient records, client files held in a professional capacity, tax returns, identity documents, anything concerning a third party who has not agreed to the disclosure. The reason is not that a vendor is untrustworthy. It is that you are not the person entitled to decide where that data goes, and the upload is the disclosure.
The useful question is not "what is a good alternative" but "can the specific thing I came here to do be done without an upload." For a lot of iLovePDF's list, yes:
For local desktop options: Apple Preview if you are on a Mac, LibreOffice Draw if you need to edit existing text and can tolerate imperfect layout fidelity, and Acrobat if you need true redaction that removes content objects, certificate-based digital signatures, or PDF/A validation. None of those three have a free substitute.
Open the editor with your Network tab open. Then disconnect your wifi and keep working.
Open the editorFor documents that are yours to share, yes. It is an established EU company subject to GDPR, with a subscription rather than a data-monetisation business model. The unavoidable fact is that files are processed on their servers, which matters for specific categories of document rather than being a problem with the company.
They publish a short retention window in their privacy policy, and that policy is the only reliable place to read the current figure. The more important point is that the length of the window is not the issue when the upload itself was the thing you were not permitted to do.
Yes, almost always. PDFs carry an information dictionary and usually XMP metadata with Title, Author,
Subject, Keywords, creating application and timestamps. The Author field is typically filled in
automatically from your computer's account name when you export from a word processor. Run
exiftool on a file, or check document properties in your reader, before sending it to
anyone.
Note that exiftool -all= on a PDF writes an incremental update rather than rewriting the
file, so the old values remain recoverable inside it. Follow it with a rewrite, such as
qpdf --linearize, or use a tool that rebuilds the document. RaptorPDF has no metadata
editor, though its rebuild-based tools such as merge and split incidentally drop the original Title,
Author and Keywords.
No. HIPAA requires a business associate agreement with any provider handling protected health information, and free consumer tiers do not offer one. The upload is the disclosure, so deletion afterwards is not a remedy. Use local software.
Repairing damaged files, Bates numbering, optical character recognition at any real volume, image-level compression that leaves text as text, and an API for automation. Those all need a server. Merging, splitting, signing, form filling, watermarking and password protection do not, and can be done without the file leaving your machine.