Privacy by architecture

Your documents stay on your device

PDFDock uses your browser to process documents locally. You do not upload a PDF to us before you merge, compress, sign, convert, or OCR it.

The document workflow

A local workflow from start to finish

1

Choose a focused PDF tool

Select the task you need—from merging and compression to signing, conversion, or OCR.

2

Work in your browser

Your browser reads and transforms the document on your own device. PDFDock does not receive the PDF, its filename, or its contents.

3

Save the result locally

When the task is complete, download the result directly to your device. There is no server-side document storage or cleanup queue.

We do not receive

Your document data

  • ×
    PDF contents

    Pages, text, images, and generated results remain in your browser.

  • ×
    File names or document metadata

    These are used locally to complete the task, not sent to PDFDock.

  • ×
    Your document-processing history

    We do not create a server-side library of your PDFs or processing results.

We use the minimum needed

To operate your workspace

  • Account and session data

    Your verified email and secure session keep your workspace and monthly allowance available.

  • Usage and setting metadata

    We record task counts and parameter-only presets—not source documents or filenames.

  • Billing data for paid plans

    Stripe handles payment details; PDFDock stores only subscription metadata needed to grant access.

A useful detail about OCR

The first OCR run may download a language asset—not your document.

OCR recognition still happens locally in the browser. The initial language download helps the browser recognize text; PDF pages and extracted content remain on your device.

Visit the Help Center

Use PDF tools without the
upload-and-wait step.

Start with 10 Free local PDF tasks each month. Your documents stay on your device on every plan.