Privacy Policy

Information you provide

When you use a processing tool, the application receives the file or files you select and the options you submit, such as page selections, text, or a password. The server uses this information to perform the requested operation and return an output.

The site has no account or contact-message database in this project. A contact form is not implemented. If an email address is configured on the Contact page and you choose to email it, your email provider handles the message.

Uploaded files and retention

The conversion endpoint streams uploaded files into a unique temporary directory on the server, processes them in a worker thread, and streams the output back. The application does not save files to a user document library or database.

The application attempts to remove a job directory after an error or when the output stream closes. It also checks for PixelPDF job directories older than four hours at startup and periodically. This is best-effort cleanup, not a guarantee: a host, backup, crash, or storage layer may have separate retention behavior.

The application sends password fields to the processing worker as request data and does not intentionally write those field values to logs. Do not upload files or enter information unless you are authorized to do so.

Technical information and logs

The application code writes a generic server-side error entry when a conversion worker fails; it records an error name rather than the uploaded document or password. The app code does not define an analytics event pipeline, advertising tags, or a user account system.

The hosting platform, network provider, or infrastructure may independently process connection details such as IP address, request time, browser information, or security logs. The repository does not identify the production host's exact log fields or retention period; consult that provider's privacy information.

Cookies, analytics, and third parties

No analytics, advertising, or cookie-consent integration is configured in the application code reviewed for this page. This does not establish what cookies or logs a production host, browser, or future deployment integration may use.

File processing uses third-party open-source packages installed with the application. The conversion code processes HTML input locally and does not fetch arbitrary remote URLs for the HTML-to-PDF workflow. Hosting and infrastructure services remain subject to their own terms and practices.

Security and your choices

The application uses temporary job directories, file-signature and size checks, server-side worker processing, and response headers intended to prevent caching of generated files. These measures reduce certain risks but do not guarantee that data is completely private or secure.

You can choose not to upload a document, remove the local source from your device, and avoid entering confidential details. Legal privacy rights depend on your location and the service deployment. No user-account or in-product data-request mechanism is implemented here.

• Read the security overview ↗
• Contact options ↗

Policy changes

This policy should be updated when the application's data flows or hosting configuration changes. The review date above is the date this page was prepared, not a promise that every deployment detail has been independently audited.