How OnePDFs handles files and account data
A plain-language processing map for local PDF tools, server conversions, Smart Redact, analytics, advertising, and accounts.
Last updated: 2026-07-14
The short version
Most OnePDFs tools process the PDF inside your browser, so the document is not sent to our PDF processing service. PDF to Word, PDF encryption, and password removal are exceptions and send the file over HTTPS to a processing service.
Smart Redact downloads a machine-learning model to your browser when needed, but the PDF analysis itself remains on the device. The table below is the source of truth for these differences.
PDF and site data processing map
Check the row for the feature you plan to use before opening a sensitive document.
| Feature | Where it runs | Data involved | Storage or retention |
|---|---|---|---|
| Reader, editor, annotations, signatures, page tools, compression, images, watermarks, and batch tools | Your browser | The PDF and generated output stay on the device for these workflows. | Browser memory or local browser storage used for the active session; clear site data to remove local caches. |
| Smart Redact | Your browser; model downloaded from a model host | The model download exposes normal network metadata to the model host. PDF detection stays on the device. | The model may remain in browser Cache Storage until the browser or user removes it. |
| PDF to Word | OnePDFs processing service | The PDF is uploaded over HTTPS and converted into a DOCX file. | Input and output files are deleted after the one-hour post-completion retention window. Expired orphan files are scanned on startup and every five minutes. |
| Encrypt PDF and remove PDF password | OnePDFs processing service | The PDF and password are sent over HTTPS and used only to complete the requested operation. | A randomly named temporary output is used while the download is streamed and deleted when the response finishes. If a transfer is interrupted, periodic orphan cleanup removes it after the one-hour retention window. |
| Account and optional cloud files | OnePDFs account database and object storage | Email, name, authentication data, and files you explicitly choose to save while signed in. | Kept while needed to provide the account or saved-file feature, or until deletion is requested or performed. |
| Analytics, infrastructure logs, advertising, and consent | Self-hosted Umami, hosting providers, Cloudflare analytics when enabled, and Google AdSense on eligible public pages | Page URL, referrer, browser/device information, performance events, approximate network information, ad or consent signals. PDF contents are not analytics events. | Controlled by the applicable service configuration and provider policy. Regional consent controls are shown where required. |
Cookies and local storage
OnePDFs uses browser storage for settings, document sessions, model caches, language and theme preferences, and authentication. Advertising and consent providers may use cookies or similar identifiers according to your region and consent choices.
Security and data minimization
Server features use HTTPS in transit. No online service can promise absolute security, so avoid server-processed tools for material that you are not authorized to upload, and remove unnecessary sensitive pages before conversion when practical.
Operational logs may record request time, route, status, IP address, and browser information for reliability and abuse prevention. We do not intentionally put PDF contents or passwords into analytics events.
Your choices and requests
You can use most tools without an account, clear browser site data, decline non-essential consent where the control is offered, and delete saved files from the product where available. For access, correction, deletion, or privacy questions, contact xuezaigds@gmail.com.
Do not email a confidential document with your request. A URL, task time, account email, and a description of the issue are usually enough to start an investigation.
Changes to this notice
We update this page when the processing architecture or data practices materially change. The date at the top identifies the current version.