Plain-language policy
Privacy built into the product
Short version: for every local tool, your PDF stays on your device and localpdf.store does not upload, store, inspect, or share it. The optional Gmail scanner transfers attachments directly from Google to your browser and does not send them through or store them on localpdf.store.
How document processing works
When you choose a PDF, browser-based code reads and renders a working copy in the current tab. When you download, a fresh copy of the original document is updated locally. No upload endpoint or remote file-processing service is involved.
Gmail PDF scanner
The Gmail scanner uses Google's browser authorization flow and asks only for Gmail read-only access. Its short-lived access token is held in memory in the current tab, not in a cookie or local storage. Gmail message metadata and PDF attachments are requested directly from the Gmail API. PDF text extraction, OCR, matching, and results remain in the tab and are cleared when you disconnect, refresh, or close it.
Gmail authorization lets the tool read the messages and attachments needed for your scan. It does not allow localpdf.store to send, edit, or delete email. Google may separately record API access under your Google account according to Google's policies.
Optional AI summary pages
The sort-and-merge tool can create a basic summary index entirely in your browser. It also offers a separate, optional AI-assisted statement. Before that feature runs, the interface asks you to consent to sending PDF filenames, detected dates, and extracted document text to the localpdf.store backend and OpenAI. Original PDF bytes are not sent. The server uses the text only to return a structured draft, requests that OpenAI not store the API response, and does not save the request or generated summary.
AI-generated names, amounts, references, totals, and descriptions may be wrong. The draft is editable and must be reviewed against the original documents before download.
Information we do not collect
- PDF file contents or file bytes
- PDF filenames
- Form field names or values
- PDF protection passwords
- Placed text
- Copies of completed documents
Cookies and accounts
The local PDF tools have no login or payment flow. The Gmail scanner requires explicit Google authorization, but localpdf.store does not create an account or store a refresh token. The current version does not use advertising cookies or document analytics.
Network access
The local PDF libraries and worker are bundled with the site. The Gmail scanner additionally connects to Google Identity Services and the Gmail API after you choose Connect Gmail. The OCR engine may download its English language model when OCR is first needed; the PDF page being recognized is not uploaded to that model host. The optional AI summary connects through our backend to the OpenAI Responses API only after the consent control is selected.
Keeping control of your file
Closing or refreshing the tab clears the active editing, compression, merging, splitting, or protection session. Your original PDF is not changed; a new output file is created only when you choose Download.
Questions
This policy will be updated with a contact address when the final domain is selected. Until then, no personal information or document data is requested by the service.