Privacy Policy

InstantPDFEdit (“we”, “us”) provides browser-based PDF tools at instantpdfedit.com. This policy explains what we do — and do not — collect.

The short version

For core PDF tools, your files are processed locally in your browser. We do not operate a file-upload pipeline for those tools, and we do not keep copies of your PDFs on our servers.

How tools handle your files

100% local / never uploaded

Most InstantPDFEdit tools (merge, split, compress, organize, annotate, sign, protect, OCR, and similar) read and process files entirely on your device in the browser. Bytes stay in page memory (and, if you use Recents, optionally in local browser storage on your device). They are never uploaded to InstantPDFEdit servers for processing.

Print / best-effort (still local)

Some flows use your browser’s print dialog, canvas export, or “best-effort” converters (for example PDF↔Office approximations). These still run client-side. Output quality varies; we label imperfect paths honestly rather than claiming pixel-perfect conversion.

Browser / device APIs (not our servers)

A few tools may call APIs provided by your browser or OS when available (for example the experimental Translator API for Translate). Those requests go to the browser vendor’s implementation — not to an InstantPDFEdit upload backend. If the API is unavailable, the tool falls back to a local/offline mode where documented.

External third-party services we do not use for PDFs

InstantPDFEdit does not send your PDF contents to paid cloud OCR, LLM, or e-sign backends for the shipped free tools. OCR, Summarize, Translate, and Ask PDF run on your device (or via APIs your browser itself provides). Nothing is uploaded to InstantPDFEdit for those tools. There is no optional cloud (BYOK) upload path today.

Browser storage

• localStorage / sessionStorage — preferences such as theme, install-prompt dismiss state, and similar UI flags.
• IndexedDB — optional “Recent files” cache on your device so you can reopen work quickly. You can clear site data in your browser to remove it.
• Service worker cache — app shell assets for faster loads / offline shell. User PDFs are not intentionally precached.

Server-side retention

For local tools there is no server-side retention of your documents: we have nothing to delete because we never received the file. Hosting logs from our CDN/host (for example Vercel) may include standard request metadata (IP, URL, user agent) for security and reliability — not your PDF contents.

Analytics

We do not currently ship a first-party product analytics SDK that tracks your document contents. If we add privacy-respecting analytics later, we will update this page. Platform-level metrics from our host or ad partner may exist independently of document processing.

Advertising (Google AdSense)

On the marketing website (not inside the installed PWA shell), we may show ads via Google AdSense. AdSense uses cookies or similar technologies as described in Google’s policies. We do not pass your PDF bytes to AdSense. If ad slots are empty or unfilled, we hide the sponsored chrome rather than leave large blank frames.

See Google’s advertising policies for how ads personalization works and how to control ad settings.

Third-party libraries

The app loads open-source libraries in your browser to do the work. Those libraries run locally with your file bytes unless a specific tool documents a browser API call.

Support expectations

We provide documentation pages and a contact path (see Contact). There is no ticket portal or human review of your PDFs — please do not email confidential file attachments unless you accept email transport risk and we have asked for them.

Children

InstantPDFEdit is a general-purpose utility, not directed at children under 13. Do not use the service to upload or process data about children in ways that violate applicable law.

Changes

We may update this policy as the product evolves. The “Last updated” date at the top will change when we do.

Contact

Privacy questions: see Contact.