Understand how current PdfnMore PDF tools handle uploaded files, temporary processing data, service telemetry and future saved-document features.
Current production statement · Updated September 2026
Uploaded files are processed for the action you request. The current public core tools do not create a permanent My Documents library or silently add processed files to an account.
Some processors operate in memory, while others require request-scoped temporary files. Where temporary working directories are used, the application removes them when that processing request finishes.
Operating a web service can involve technical data such as request timing, IP-derived network information, browser or user-agent details, error information and abuse-prevention signals. This data is used to operate, troubleshoot and protect the service rather than to claim ownership of document contents.
The current public interface does not expose account authentication, so account-session cookies and a public saved-document workspace are not presented as active features.
Backend foundations exist for accounts, separate job-history metadata and explicitly saved documents. Those foundations remain behind the interface until authentication and private document access are complete.
When My Documents becomes public, normal tool processing will still not mean automatic permanent saving unless the user explicitly chooses to save or later enables a clearly described auto-keep preference.
Trust Center · Privacy · Security · File deletion · Help
No. Current core tool use does not create a permanent user document library.
No. The product architecture keeps lightweight job-history metadata separate from saved document bytes.
The backend now has foundations for those requests, but public account authentication and user-facing export/deletion controls are not live yet.