Know where your PDF is processed and what leaves the device
PickPDF runs core document work on your device. This page separates that local path from store delivery, updates, support, model downloads, and AI endpoints that can use a network.
Open PickPDF Processing model
Core PDF operations run in the browser or installed application
PickPDF opens PDF bytes, renders pages, edits content, manages pages, fills forms, adds signatures, performs OCR, compares documents, and creates output files on the user’s device. The browser editor does not require an account. A native or browser file handle can support save-in-place; other browser flows download a copy.
Local processing limits the document route. It does not secure an unlocked computer, a shared browser profile, the destination folder, or a file sent through another service. Device access controls, storage encryption, retention rules, and approved sharing channels remain part of the user’s security process.
Network map
Some product services need a connection
| Service | Network use | Document-content treatment |
|---|---|---|
| Browser application | Loads application code and updates | Core PDF work runs on the device |
| Microsoft, Chrome, and Snap stores | Install, update, and listing services | Stores distribute the application package |
| OCR and built-in model files | Downloads required language or model assets | Recognition and built-in inference run on the device after assets load |
| Ollama or LM Studio | Connects to the endpoint configured by the user | The selected text context goes to that endpoint |
| OpenAI-compatible endpoint | Can be local, private-network, or remote | The configured endpoint receives the context sent with the request |
| Contact form | Sends a support message through email delivery | Users should not include confidential PDF content |
File access
The platform controls which files PickPDF can read or write
Browsers grant access through files or folders selected by the user. A writable handle can allow PickPDF to update the source. Without that handle, the browser downloads a new file. Desktop builds work through the operating system’s filesystem and account permissions.
Grant access to the narrowest folder needed for the task. Preserve an unchanged source for redaction, signing, page reorganization, protection, and archival work. Reopen the saved output from its final location and check that the intended file changed.
PDF-specific checks
A private editing route does not guarantee a safe output file
Redaction
Apply destructive redaction for supported page text and images. Search the output and inspect annotations, metadata, and attachments before release.
Signatures
A drawn, typed, or uploaded mark is a visible appearance. A P12 or PFX certificate signature provides a separate cryptographic path.
Passwords
Standard protection uses AES-256 PDF encryption. Store passwords apart from the file and test access in the recipient’s viewer.
Verification
Review the saved result before distribution
- Keep an unchanged source or controlled prior version.
- Open the output from its saved location in another supported viewer.
- Search sensitive terms and inspect metadata, annotations, links, forms, and attachments.
- Check page order, OCR figures, signatures, permissions, and visible layout.
- Share the file and any password through approved separate channels.
Organizations should test PickPDF with representative non-sensitive files and document their approved settings. Contact the team for product questions or deployment discussions without sending confidential PDFs.