Security
Security for a browser utility starts with a narrow product promise: selected files should stay in the browser unless a page clearly says otherwise.
Current security posture
Browser-side workflow
The current tools use browser APIs and client-side JavaScript libraries to process selected files locally.
Minimal third-party code
The tool pages avoid unnecessary third-party code so the main document task stays fast, clear, and easier to test.
Practical document safety
Browser-side processing reduces unnecessary upload exposure, but it does not remove every risk. Users should still keep originals, review outputs, and avoid processing sensitive files on shared or untrusted devices.
- Keep original files until the output has been checked.
- Use a private device for personal, legal, school, medical, tax, or financial files.
- Do not modify signed, encrypted, or official certified PDFs unless the receiving party allows it.
- Report broken downloads, suspicious behavior, or file-handling bugs through the contact page.
User safety checklist
- Keep original files until output is verified.
- Do not process files you do not have permission to use.
- Avoid sensitive documents on shared or untrusted devices.
- Report bugs or security concerns through the contact page.