Legal & Privacy · Zero Document Uploads

Privacy Policy

How InBrowserPDF handles local documents, browser storage, public processing engines and support messages.

Last updated: 4 November 2026

  • No document-upload endpoint: PDFs, passwords, signatures, and extracted text stay in your browser.
  • No advertising cookies, behavioral analytics scripts, or mandatory user accounts.
  • Public WebAssembly engines cache locally; private documents are never stored in browser databases.

Documents are processed on your device

InBrowserPDF.app reads the files you select in your browser. PDF operations run in temporary Web Workers, using JavaScript and WebAssembly. The application has no document-upload endpoint and does not send document contents, extracted text, passwords, signatures or AI prompts to a processing server.

This applies to the on-device OCR and AI summarizer as well as conversion, editing and security tools. The AI model runs locally; document text is not submitted to an external AI API.

Network connections and hosting

Your browser requests this website and its public application, font, model and processing-engine files. The hosting infrastructure necessarily receives connection information such as IP address, requested URL and browser headers. These requests do not contain your selected documents.

The application does not include advertising, analytics trackers or account registration. Hosting-provider logging and retention must be described by the operator when production hosting is selected; this policy does not promise that infrastructure has no access logs.

Storage and retention

Selected documents and working results are held in the current browser workspace. Navigating to another tool, resetting, refreshing or closing the page clears application references and stops active jobs. This is not a secure-erasure guarantee for browser or operating-system memory.

Downloaded results remain wherever your browser saves them. Your theme preference is saved in localStorage under inbrowserpdf-theme. Public processing assets may remain in the browser HTTP cache; the Office engine also caches public engine parts in CacheStorage. The app does not save private documents in IndexedDB or CacheStorage. You can clear site data through your browser settings.

Support and your choices

If you email support@inbrowserpdf.app, your email provider and the support mailbox handle the message and any information you choose to include. Do not attach confidential PDFs unless a separate support arrangement explicitly requires it. We cannot retrieve documents that remain only in your browser.

Depending on applicable law, you may have rights concerning personal information supplied in support messages. Send requests to support@inbrowserpdf.app. Browser-local workspace data can be cleared directly on your device.

Changes to this policy

This policy describes the current application. Adding accounts, analytics, advertising, server processing or other data collection requires an updated policy and any notices or choices required by applicable law. The version date below identifies the current text.