Skip to content
DontTouch My Doc.
Colophon · §00

We built this because most PDF tools quietly upload your files. We didn't want to be another one.

Privacy · Enforced static · CDN zero servers open standards

The short version.

DontTouchMyDoc is a handful of PDF tools that run entirely inside your browser tab. Merge. Split. Organise. Compress. Redact. Strip line numbers. We don't have a backend. We never receive your files, because there's nowhere to receive them.

We built the site because we got tired of using the open-web equivalent of a copy shop where everyone behind the counter squints at your documents. "We'll delete it in 24 hours" is a policy. Not uploading at all is a fact.

Open source · MIT

Don't take our word for it — read the code.

The entire site is on GitHub. If you want to verify that nothing gets uploaded, the source is right there: every tool, every script, every network boundary. Open your browser's DevTools too while you're at it — you'll see the tool code load, and then silence.

github.com/NickPax/donttouchmydoc
Manifest · §01

Our promises.

  • Your files never leave your device.
    Not to us. Not to a third party. Not to anyone.
  • No sign-up, ever.
    No email, no password, no "unlock this feature".
  • No watermarks, no page limits.
    The output of the tool is the output. Nothing added, nothing nagging.
  • No tracking inside the tools.
    If we ever add analytics, we'll say so here, publicly, and use something privacy-preserving.
§02 · Privacy

Privacy, stated plainly.

This site is a static bundle of HTML, CSS and JavaScript served from a CDN. There is no application server, no database, no file-upload endpoint. When you drag a PDF onto a tool, the bytes move from your filesystem into your browser's memory. They don't go further.

Our tools use two open-source libraries — pdf-lib and pdf.js — bundled into the page. They run inside your browser's sandbox. We cannot read what happens there, and neither can anyone else.

We don't set cookies. We don't use localStorage. We don't run third-party scripts inside the tools. If we ever add analytics, it will be a privacy-preserving counter, and we'll say so on this page with the date we added it.

To earn the site its keep, we plan to serve a small number of contextual ads around the tools. Ads render in their own frames — they don't and can't peek at the PDF you're working on. If the trade-off isn't to your taste, uBlock is a perfectly reasonable response.

§02 · Procedure

How the site works.

Three steps. None of them involve a server.

  1. Step 01 1

    You open a page.

    Your browser loads a static bundle of HTML, CSS and JavaScript from a CDN. That's the whole site.

  2. Step 02 2

    You pick a file.

    The tool loads it into memory inside this tab. Our server never sees the bytes — there is no tool endpoint to hit.

  3. Step 03 3

    You download the result.

    The processed file is generated locally and saved via your browser. Close the tab, and every trace vanishes.

§04 · FAQ

About · FAQ.

Short answers. Anything missing? Tell us.

How can I verify you're not uploading?
Two ways. (1) Open your browser's DevTools and switch to the Network tab. Use any of the tools. You'll see the page load, the tool's code chunks load, and then — silence. No file uploads, no POSTs to an API, no background pings. (2) Read the source directly at github.com/NickPax/donttouchmydoc — every line of the tool logic is public.

Do you use cookies or localStorage?
No cookies. No localStorage writes from our tools. We don't need either to run, so we don't use them. No cookie banner required.

Do you track analytics?
Not at launch. When we do, we'll use a lightweight privacy-preserving counter (think Plausible or similar, self-hosted), and we'll say so here. No Google Analytics, no Facebook pixel.

Why does the site have ads?
Tools this useful aren't free to build and maintain. A small number of contextual ads keeps the lights on without adding a paywall. Ads never see your files — they're scoped to the page layout, not the tool.