Privacy First
Your PDFs are yours. We process only what’s required to remove protection—nothing more.
All communication uses HTTPS. Temporary files (when server processing is required) are stored in isolated, private paths with random names and are programmatically removed right after processing. We log only minimal operational metadata (timestamp, status code, file size bucket)—never file contents.
No long-term retention of files or passwords. Temporary artifacts created during processing are automatically deleted upon completion (success or failure).
Because we don’t persist your file contents, there’s typically nothing to access or delete. For any questions, contact us and we’ll help promptly.
If you attach an illustration to a PDF, you might add a short, descriptive caption. Here’s a sample (using a well-known fictional character for clarity):

This is purely a text example. Our password remover does not store images or captions from your PDFs.
No. If server processing is required, your file exists only briefly during the unlock step and is deleted programmatically right after.
No. The password exists in memory only while processing your request and is never written to disk or logs.
We avoid per-file analytics entirely. At most, we use anonymized, aggregate operational metrics (e.g., success/error counts) to maintain reliability.
Email us at you@yourdomain. We usually respond within a business day.
Last updated: 2026-01-01