Privacy & statistics

In short: your files don't leave your device, we have no cookies and we don't know who you are. We only count aggregate numbers so we know which tools are used.

Your files

All tools except "Word to PDF" and "PDF to Word" run in your browser (JavaScript and WebAssembly). The file is loaded into the page's memory, processed and offered for download — not a single byte of it goes to our or anyone else's server.

How you can check this yourself

• The "Sent to a server" counter on every tool adds up every byte the page sends. For in-browser tools it stays at 0 B.
• Open the developer tools (F12) → Network and watch the requests while you process a file.
• Turn off your internet after the page loads — the tool still works.
• The source code is open under the MIT license.

Digital certificate

When you sign with a .p12/.pfx certificate, the certificate file and password are read only in the page's memory; the private key is imported into the browser's WebCrypto as non-extractable and disappears when you close the page. None of it is sent. If you choose "Remember on this device", only the certificate and that non-extractable key stay in the browser (IndexedDB) — not the file and not the password; they're removed with "Forget" or by clearing the site data. The same goes for signature verification: revocation is deliberately not checked, because that would mean sending certificate data to other servers.

The exception: Word to PDF and PDF to Word

These two tools need LibreOffice, which can't run in a browser, so the file is sent to our server. There it's written to a temporary folder, converted and deleted right after the conversion, together with the result. We keep no copies and log neither file names nor contents. These tools are clearly marked and the counter shows the exact number of bytes sent.

Statistics: what we count

To know which tools are useful, we keep aggregate statistics per day. They contain nothing that identifies a person or a device:

• the number of views of each page,
• an estimate of the number of distinct visitors per day,
• the page language (Latin, Cyrillic, English) and the rough device type (phone, tablet, computer),
• the domain of the site you came from (e.g. google.com), without the rest of the address,
• which tool was run, whether it succeeded and with how many files — without file names, sizes or contents,
• how many times LokalPDF was installed as an app.

How we count visitors without tracking

To estimate visitors, the server computes a one-way fingerprint (SHA-256) from the IP address and browser string with a random key that changes every day and is never written to disk. The fingerprints exist only in memory until the end of the day; only their count is kept. Because of this we cannot link two visits on different days, nor recover anyone's IP address from the statistics.

What we don't do

• We have no cookies, neither ours nor third-party.
• We don't write IP addresses to the statistics or the application logs.
• No Google Analytics, no ads, no third-party scripts — the page's security policy (CSP) only allows our own scripts.
• We don't build profiles and don't share data with anyone.

Do Not Track and Global Privacy Control

If "Do Not Track" or "Global Privacy Control" is enabled in your browser, we don't count you at all — neither page views nor tool usage.

What is stored in your browser

• Your theme choice (light/dark) — in localStorage.
• A file you pass to the next tool ("Continue with") or share from your phone — in IndexedDB, until the next tool picks it up.
• Pages, scripts and OCR models for offline use — in the browser cache (Service Worker).

All of this stays on your device and you can delete it by clearing the site data in your browser settings.