How Local Processing Works

File bytes are read into browser memory and transformed with local libraries. The app does not use a dedicated backend service to upload and process PDF content.

When the page is refreshed or closed, in-memory processing data is discarded. Downloaded files remain on your device according to normal browser download behavior.

Analytics can observe page interactions and route-level events, but not document payloads by design. Third-party browser extensions and network policies may still influence your environment.

OCR features rely on browser-side OCR libraries and language assets. Runtime performance and language support depend on device resources and available package assets.