Where your pages go, in plain words.

1 · What happens to a document you open

In the web app, the file is read by the page in your browser. Its pages are decoded, rendered and held in that tab’s memory. Nothing is written to a server. When you close the tab, it is gone from memory; the original file is untouched where you keep it.

Export and Extract write a new PDF to your own download location. That file is assembled in the browser, not fetched from us.

2 · OCR on the web app — the one transmission

Text recognition is the only feature of the web app that sends page content off your machine. When you ask for OCR, the pages you selected are transmitted over TLS to our recognition service, processed, and the resulting text layer is returned to your browser. The transmitted page images and the derived text are deleted from the service once the response is delivered. They are not used to train anything, not indexed, and not shared with any other party.

If your obligations do not permit that transmission at all, you have three options: do not use OCR in the web app; use the Android tablet app; or use the Linux AppImage. In both of those, recognition is bundled and the page never leaves the device.

In the browser build, the recognition engine and its language data are also downloaded from the network the first time you use them.

3 · What we hold about your account

• Your email address, and a password stored only as a salted hash.
• Your plan, subscription status, renewal date and the seats on the account.
• Counters for the current period: PDFs exported or extracted, OCR pages used. Numbers only — never file names or contents.
• Licence key issuance records for the Linux AppImage.
• Ordinary server logs: IP address, timestamp, request path, user agent. Retained for a limited period for security and abuse investigation.

We do not hold your documents, your file names, your matter names, your clients’ names or your case numbers, because none of that is sent to us.

4 · Payments

Card details are collected and stored by our payment processor, not by us. We receive a customer reference, the last four digits, the card brand and the outcome of each charge. The full card number never reaches our systems. Google Play handles payment for the Android app entirely; we receive no card data from it at all.

5 · Encryption

All traffic to docketpdf.com and to the recognition service runs over TLS. Account data at rest is encrypted by the hosting provider. Since documents are not stored, there is no document store to encrypt — which is the strongest form of data protection available.

6 · Licence keys and the tablet unlock

Linux licence keys are validated against a one-way cryptographic digest, so a stored key cannot be read back out of the software. On the Android build the paid unlock is recorded by Google against the buyer’s own Google account; we never see it. That build also offers a rewarded-ad pass as a free path to exporting, and the ad feed is the only third-party content it fetches.

7 · Reporting a vulnerability

Write to support@docketpdf.net with enough detail to reproduce the issue. We will acknowledge within five business days, will not pursue anyone acting in good faith, and ask that you give us a reasonable window before publishing. Please do not test against other people’s accounts, and please do not send us anyone’s real documents.

8 · What we do not claim

DocketPDF™ holds no third-party security certification and makes no representation that it satisfies any particular professional, statutory or contractual security obligation you may be under. It is a small independent product. If your practice requires a signed data-processing agreement, an audited certification or a specific retention regime, ask us before subscribing rather than after — the honest answer may be that we are not a fit.