Privacy Policy

What we don't collect

• We don't receive, store, or process the PDFs you upload. Parsing, detection, and redaction all happen locally in your browser using JavaScript.
• We don't have user accounts, so there's no name, email, or password of yours on file.
• We don't use tracking cookies, analytics pixels, or third-party advertising scripts.
• We don't use your documents or any part of them to train AI models, run analytics, or for any other purpose — because we never see them.

What does happen technically

Like any website, LockPDF is served from infrastructure operated by our hosting provider (currently Vercel). Standard web server logs — things like IP address, browser type, and request timestamps — may be recorded briefly by that infrastructure for security and reliability purposes, the same way any website on the internet works. This is separate from, and unrelated to, the content of any PDF you process — that content is never transmitted to our servers or our hosting provider in the first place, since redaction happens entirely client-side.

One exception worth naming explicitly: the PDF-rendering library we use (pdf.js) loads its background worker script from a public CDN (cdnjs.cloudflare.com). That request fetches library code only — never your document — but it does mean the CDN operator can see that a request for that script was made from your IP address, as with any third-party script a website loads.

Local storage

The app doesn't persist your files anywhere — not in a database, not in browser storage. Once you close or refresh the tab, everything related to your document is gone unless you've downloaded the redacted result yourself.

Changes to this policy

If this product grows to include accounts, payments, or optional server-side features in the future, this page will be updated to reflect that clearly before any such feature is turned on, and this policy will describe exactly what changes.

Contact

Questions about this policy? Reach out at lockpdfsaas@gmail.com.