Your documents stay on your device

PDFBurrow processes your documents in your browser, not on a conversion server. It does not upload document contents, filenames, previews, selections, settings, or generated outputs. It uses no app analytics or external error reporting.

Work lives in this tab

Inputs, previews, drafts, and outputs are not automatically persisted. Refreshing, closing, or losing the tab loses that work. Original files and downloaded copies remain unchanged. Clearing work releases app-held resources; it is not secure deletion or forensic memory erasure.

Downloads happen only when you request them. A download request does not confirm that your browser saved the file. Tool links contain no document data and cannot restore a draft.

Personal signing keys and proofs

Personal seal keys, passwords and proofs are processed locally and never automatically saved in browser storage. A reusable key is saved only when you explicitly download its password-encrypted backup. There is no key or password recovery service. The unlocked key lives in this tab until you reset, confirm tool navigation, refresh or close it.

Proof files contain a public key, exact document hash, byte count, approval statement, random nonce and signature, but not your password or private key. Public fingerprints can link proofs made with the same key. Share proofs intentionally and confirm signer fingerprints separately. These proofs do not independently verify identity, signing time or legal validity.

Your appearance preference

The light or dark theme choice is saved in your browser's local storage so it can be remembered on your next visit. This preference contains no document data and is not sent to a server. Clearing this site's local storage resets the theme to dark.

Website requests still happen

Your browser requests application code, local workers, and styles from the website's host. When hosted on GitHub Pages, GitHub receives these ordinary requests and may retain hosting or request logs. A self-hosted copy has the same document-processing boundary, but its host may have its own request logging policy.

Browser caching of application assets is different from document storage. PDFBurrow does not promise offline startup or PWA support. Clicking Source code explicitly visits the external repository; it does not upload your documents.

Development status

This is a development build. Complete browser/device, resource, and release privacy evidence remains pending. These boundaries describe the application's behavior, not a universal privacy guarantee about your device, browser extensions, or hosting provider.