Pic2PDF privacy

Your pictures stay in the workflow, not in a conversion queue.

Pic2PDF is built around browser-side processing. The files you choose are read into the browser for preview and PDF generation.

The statements below describe the intended core tool workflow. Site analytics, advertising or external resources can have their own policies and should be reviewed separately.

Image files

Pic2PDF does not use a remote Pic2PDF conversion endpoint for the core image-to-PDF operation. Images are loaded from your device into browser memory, previewed locally and passed to the local PDF worker for processing.

Browser memory

Selected images may remain in browser memory while the tool is open so that you can reorder them or export again. Closing the page releases the application-held object URLs and worker resources.

Downloads

Generated PDFs are created in the browser and exposed through a temporary browser object URL for download. The PDF is not intentionally uploaded by the Pic2PDF converter.

Third-party resources

Pic2PDF may load external libraries from public content delivery networks. A third-party resource can have its own network and privacy characteristics. The application should not be represented as controlling those providers' policies.

Analytics and advertising

RuntimeHub tools may use privacy-respecting analytics or advertising infrastructure to understand traffic and fund the free service. Any such service is governed by its own configuration and policy.

Your responsibility

Do not use a browser utility as your only copy of an important source file. Keep originals when preservation matters.