Supported PDFs, PNGs, and JPGs are opened and processed in the browser workflow.
Processing boundary
Local processing boundary
Local processing means the current core PDF workflow is designed to use browser APIs and client-side workers for document prep instead of uploading the document bytes to a PrivateLocalPDF server.
Start basic local import, page edits, and exports without a PrivateLocalPDF login.
Basic local PDF exports are not branded or held behind a watermark.
The Local License handoff uses license metadata, not PDF bytes or document-derived data.
Core local paths
- Open supported PDFs, PNGs, and JPGs from the browser file picker.
- Preview, reorder, rotate, delete, and select pages in the browser workspace.
- Add visual text, signature-style, and checkmark overlays.
- Try local compression presets and fail clearly when a target is not reachable.
- Export a PDF Blob and download it from the browser session.
Outside the core local boundary
- Stripe Checkout for Local License payment.
- License validation or restore using a license key and provider metadata.
- Opt-in PostHog analytics when a launch build is explicitly configured to send the fixed anonymous app_loaded event.
- Public site hosting, static assets, and normal browser requests for routes.
- Any future OCR, AI, cloud storage, optional upload, or server-processing feature unless it is explicitly labeled and reviewed.
Claims not made
PrivateLocalPDF should not claim zero risk, compliance certification, anonymity, encryption, redaction, certificate-backed e-signatures, or guaranteed file-size reduction from the current local-processing boundary.
A browser-local tool can still be affected by browser extensions, device security, operating system storage, browser memory, networked assets, and user sharing choices.
Verification expectation
Public local/no-upload claims should be checked with synthetic QA fixtures, browser-visible verification, and network evidence before launch. Real user product analytics should not collect network traces, local-processing label views, or document-derived proof from document sessions.