PDF processing stays in your browser.

What happens locally?

• Your selected PDF, JPEG, PNG, TIFF, and SVG files are read by the browser.
• Page previews are rendered in a browser Web Worker.
• Reordering and page removal happen in the browser.
• The merged PDF is generated locally and downloaded by your browser.
• No PDF contents, filenames, or document metadata are sent to igorek.net.

What is sent over the network?

The app can send bounded anonymous product events to understand aggregate usage and performance. These events may include a page path, referrer hostname, UTM source, coarse device and browser family, document/page counts, a file-size bucket, timing values, processing engine, and error category.

Telemetry does not include PDF bytes, filenames, document metadata, email addresses, account IDs, or IP addresses. You can turn anonymous telemetry off using the control in the merger footer.

Verify it yourself

Open your browser's Developer Tools, select the Network panel, and merge a document. You can inspect the requests yourself. The PDF processing workers do not upload your source files; the small telemetry request contains aggregate event fields only.

Local storage and cookies

The app uses one first-party cookie, igorek_locale, to remember your selected language for up to one year. It does not require cookies for any other purpose or an account. If telemetry is enabled, a random browser identifier and first-seen marker are stored in local storage to support aggregate new-versus-returning and recent-export statistics. The telemetry opt-out is also stored locally. PDF files and generated PDFs are not stored there.

Future payments

There is currently no payment or account system. If paid features are introduced later, payment details will be handled by the selected payment provider rather than stored by igorek.net. This page will be updated before that feature launches.