About Pagivo PDF

Your files stay in memory for one request, then disappear.

Pagivo PDF keeps one-off uploads in server memory only. The file is processed, returned as a download, and then released. Nothing is written to disk and no public link is created.

How it works

Upload, process, download. That is the whole flow.

  • The upload lives only for the active request.
  • The result is streamed back directly.
  • When the request ends, the temporary copy is released.

Privacy boundaries

The app avoids the common persistence paths that create risk.

  • No disk storage for one-off tools.
  • No public URLs for documents.
  • No shared caching for generated downloads.

Technical guarantees

These rules are enforced in code.

  • Routes use FormData buffers and do not write files.
  • Downloads are served with private, no-store cache headers.
  • Responses include noindex headers.