PRIVACY / BROWSER PROCESSING
What “processed locally” means for a PDF workflow.
PDF SealBox is designed so common transformations can run in the browser. The page loads the application code, your browser reads the selected file, and the result is generated on your device when the workflow supports it.
Select
Your browser receives the file through the file picker or drop zone.
Process
Client-side code renders pages and applies the selected task.
Export
A new file is created for download without changing the source.
Local does not mean risk-free
Browser processing can reduce unnecessary upload exposure, but it does not replace your organization’s security policy. The browser, extensions, operating system and device still matter. Use a managed or offline device for highly restricted material.
Routine office files
Internal review copies, page numbering, presentation PDFs, image bundles and visible approval marks when your policy permits browser tools.
Restricted documents
Contracts, financial records, HR files, identity documents and regulated submissions may require a controlled offline workflow.
Privacy checklist
- Confirm you have permission to process the document.
- Close unrelated tabs and use a trusted device.
- Keep the source file and inspect the downloaded result separately.
- Do not treat a visible stamp as proof of signer identity or document authenticity.