How automatedpdf.tools handles your files, what runs locally vs. on a server, and what to verify before production use in legal, tax, and accounting workflows.
Every tool runs entirely in your browser tab. We load Pyodide (Python in WebAssembly) and the necessary engines (pypdf, cryptography, JSZip) from a public CDN, then execute the workflow against your local file. Your file bytes never leave the device.
Downloads are constructed in the browser and saved with a normal Save file dialog. There is no upload step.
Payment: subscription checkout uses Stripe. Stripe receives your billing details and emits a license token after a successful charge. We do not store card numbers.
License token: stored in your browser's localStorage so the tools know your subscription is active. You can paste the same token on another device using the Restore license flow.
Aggregate analytics: standard page-view counts; no per-file metadata.
Do not treat this site as a system of record. Keep your own retention, audit, and access controls in your firm workflow and document management stack.
Files you upload to the page exist only in the active tab's memory. Closing the tab or reloading clears them.
For regulated matters, e-discovery productions, court filings, or client contracts with specific handling terms, validate output with your internal review process before relying on it.
Specifically: redactions made by the Redact PDF tool draw rectangles over content; depending on policy, formal redaction with text removal may still be required for production deliverables.
Use least-privilege access to source files, run QA checks before filing or delivery, and preserve originals when generating derived PDFs.
For encrypted PDFs you process here, store unlocked working copies on controlled drives only and re-encrypt finals with Add password to PDF if policy requires it.