How PDFMK Processes Your Files

Start with the correct mental model

PDFMK is an online, server-processed PDF utility. Selecting a file in the browser does not immediately transmit it, but pressing the operation button does. At that point the browser creates an HTTPS request containing the document and the options you chose. The API reads the request, performs one operation, and returns a download response.

That distinction matters because phrases such as “works in your browser” are often misunderstood. The interface runs in the browser; the document transformation runs on the PDFMK server. HTTPS protects the connection in transit, while temporary-file cleanup limits how long working artifacts remain after a request. Neither fact turns an online tool into an offline tool, and neither is a reason to ignore a confidentiality policy that requires approved local software.

What each tool does behind the interface

The four tools use different PDF libraries and therefore do not all handle temporary data in exactly the same way. The relevant question is not simply whether a server is involved, but what the server must create to complete the job.

When cleanup happens

Merge cleanup runs in a finalization path, including when merging raises an error. Image-conversion cleanup is scheduled after the response and also runs directly on validation or processing errors. Split and watermark results are held in memory for the request rather than saved as a user library. A closed tab or failed download does not give PDFMK a future retrieval feature; you normally need to run the operation again.

Operational network and security logs are a separate category from document working files. Hosting infrastructure can record request time, IP address, URL, browser information, response status, and abuse signals. Those records help keep the service available, but they should not contain the body of an uploaded PDF. A filename can appear in processing context or a support report, so avoid putting secrets in filenames.

A practical sensitivity check

Before uploading, ask two questions. First, are you authorized to send this document to an external online processor? Second, would a temporary server copy violate a law, contract, client promise, or internal policy? If either answer is uncertain, stop and use a managed offline tool or ask the document owner.

Documents that often need extra care include medical records, identity documents, bank statements, legal material under privilege, student records, unreleased financial information, and files covered by a data-processing agreement. Redaction is only useful when it removes the underlying PDF objects, not when it places an opaque rectangle over visible text. Verify redaction with a dedicated tool before using any online processor.

• Work from a duplicate and keep the original unchanged.
• Remove unnecessary pages before uploading when policy allows it.
• Open and inspect the downloaded file before deleting your local working copy.
• For highly sensitive material, choose an approved offline workflow instead of relying on cleanup promises.

What advertising can and cannot see

PDFMK uses Google AdSense on site pages. Advertising technology can receive ordinary page and browser data and may use cookies or identifiers according to region and consent choices. PDFMK does not intentionally send the content of an uploaded document to Google for ad targeting, and ads are not inserted into the PDF output.

The safest privacy statement is a narrow, testable one: PDFMK receives the file to perform your requested operation, uses temporary processing rather than a permanent document library, and removes working artifacts through the tool cleanup paths. For the full policy, including logs, cookies, providers, and privacy requests, read the Privacy Policy and Cookie Policy linked in the footer.