About Pagivo PDF
Your files are processed for the request, then released.
Pagivo PDF processes uploads on the server for the PDF operation you choose. One-off tool results are returned directly, and signed-in account workflows use temporary per-user storage for downloads and cleanup.
How it works
Upload, process, download. That is the whole flow.
- The upload is used only for the active PDF operation.
- The result is streamed back directly or saved to temporary per-user storage.
- Temporary files are removed by download handling and scheduled cleanup.
Privacy boundaries
The app avoids the common persistence paths that create risk.
- No public URLs are created for documents.
- Generated downloads use private, no-store cache behavior.
- Account files live under a per-user data directory instead of a shared public folder.
Technical guarantees
These rules are enforced in the Java application.
- PDF routes validate input and process files through server-side services.
- Downloads are served through controlled endpoints instead of static file hosting.
- Public SEO pages stay separate from private upload and download endpoints.