Your files.
Your browser.

What happens to your documents

When you choose or drop a file, the browser reads it locally. Portfolio discovery, PDF and image previews, page merging, and originals ZIP creation run in the browser. This app has no document-upload endpoint and does not send your file contents to a conversion service.

Working file data remains in this tab’s memory until it is released by clearing the workspace, a new operation, or closing the tab. This is not a claim of secure erasure from device memory. Your source files and anything you download remain on your device, under your control.

What this preview remembers

Export presets can be saved in your tab’s session storage. They contain only settings such as sort order and index options, not document names or contents. The app does not save your documents in persistent browser storage.

Your Light, Dark, or System appearance preference is saved in local storage so it can apply before the page appears on your next visit. This stores only the theme choice, independently of analytics. If browser storage is unavailable, theme switching still works for the current page.

Closing the tab ends the preset session; your browser’s site-data controls can also remove stored preferences. Downloads are not removed when you clear the workspace or site data.

Network requests and hosting

The browser still loads the application’s HTML, JavaScript, styles, and processing libraries from the site’s host. The host may receive ordinary connection information such as your IP address, browser request headers, and the requested URL. That is separate from the contents of files you choose.

Google Analytics is enabled automatically when this production site loads. It does not include advertising, remote fonts, payment processing, or an account backend. A local preview may make development-server requests. While analytics is disabled, the browser’s content-security policy restricts app requests to the same origin. A deliberately configured analytics build permits only the listed Google tag and measurement endpoints when analytics is enabled; document processing has no upload endpoint.

Usage analytics

On the configured production site, the Google tag loads automatically. You can turn analytics off using Analytics settings in the footer; all converter features remain available. We use manual, allowlisted events for real-file versus sample use, coarse input/count/duration ranges, parse/export outcomes, selection actions, and download initiation. A download click does not prove a file was saved.

Our events do not include file names, paths, document text, hashes, document links, email, full referrers, search strings, or raw error messages. URLs are limited to fixed app routes without query strings or fragments. Google can still receive standard connection/browser information such as IP address and an analytics identifier when analytics is enabled.

Your analytics on/off preference is stored locally for up to 180 days when analytics is configured. Analytics settings in the footer lets you turn it off. Turning it off blocks future app events and disables analytics; it cannot retract requests already sent. A build without active analytics configuration does not create that preference record.

Your device is part of the picture

Browser extensions, operating-system services, other software on your device, or settings that synchronize downloaded files are outside this app’s control. Use a trusted device and browser for sensitive documents. Do not assume local processing provides a compliance certification or eliminates every privacy risk.

Before you share an export

Review the generated PDF, the export report, and the originals ZIP. An originals ZIP can contain every extracted attachment, including documents that you did not select for the reading copy. Make sure its contents are appropriate for the recipient.

Read the processing limitations and digital-signature notes before using exported files in an important workflow.