Privacy and file handling
How PDFResult handles your files and preferences.
Files stay in your browser
PDF editing runs in a background worker on your device. Image export, text extraction and optional previews parse the PDF in a separate local worker; Canvas rendering and output assembly run in the page with cancellation and resource limits. They do not upload file contents to a server. Your original files are not modified. Downloaded results remain on your device until you delete them.
Opening, printing and sharing results
Opening a PDF for printing gives the generated file to a separate browser viewer, without uploading it to this site. Printing is controlled by your browser and printer. Where supported, Share file opens your device's share menu and hands the file to the application you choose; that application may send or store it under its own rules. We do not create a public download link. Clearing this workspace cannot remove downloads, copies opened in other tabs, print jobs or files handed to another application.
Selections are temporary
The app does not save your files, document contents or results in browser storage. Switching operations inside the workspace retains originals, the active input and the latest result in memory. Clear workspace, reloading or leaving the workspace releases these references. Original source files are capped at 60 MiB in total; this is not a decoded-memory limit. Cancel stops active processing; it does not promise immediate memory reclamation or secure erasure by your browser.
A remembered theme
The app uses local browser storage for your light or dark theme preference. Clearing this site's browser data resets it. There is no application account, saved workspace or free-text feedback form.
Public website
This site is publicly accessible without an account and its tool pages may appear in search engines. File processing remains local to your browser; the site does not store your documents or create public links to them.
Connections and measurement
The browser requests pages, scripts and assets from Cloudflare, our hosting provider. Cloudflare receives connection metadata, including your IP address. Local file processing does not mean offline use. On approved public domains, selected tool operations send minimal usage signals to our Cloudflare collector: site, tool and task identifiers, language, software release, action, Useful / Needs work feedback and a coarse error category. We retain daily counters for 90 UTC calendar days, not raw event histories, filenames, document contents, entered text, IP columns or user/session identifiers. Release identifiers are validated but not retained in counters. Cloudflare still receives connection metadata. Collection does not set cookies and is best-effort: blocked or failed requests are not retried. We discard signals from the EEA, UK, Switzerland and unknown locations, and respect browser Do Not Track and Global Privacy Control signals. Add ?measurement=off to the page address to disable operation collection in that workspace; this does not change separate Web Analytics. These counters do not identify unique people or prove a file was saved. No Web Analytics script is loaded. No advertising network script is loaded.
Check the result
Keep your originals and check a sample before processing important documents. Check the downloaded document, including page order and content, before using it. Password-protected PDFs are not supported. Displayed input limits are not a guarantee that a file will fit in your device's memory. An operation stops after two minutes; smaller files may help if it fails.
Support
Email support is separate from local tool processing. If you send a message, your email provider and our Gmail mailbox handle your sender address and message content. Tool files are not attached automatically. Do not send passwords, access codes or sensitive documents.
[email protected]