How privacy works
DoYourPDF is a set of tools that run inside your browser. Files are opened, edited and saved right on your computer or phone, so we have nothing to store, scan, leak or delete.
Right now: 0 Bof your files sent to servers so far
What happens to a file
When you choose or drop a file, your browser reads it into this tab's memory. The tool works on that copy with JavaScript and WebAssembly running on your device, builds the result in memory, and hands it back to you as a download.
Close the tab and the copies are gone. Nothing is written to a server, because nothing is sent to one.
What uses the network
Loading the site. Your browser downloads the app, fonts and engines (PDF.js, pdf-lib, Tesseract OCR and its language data) from this site. These are downloads only; nothing of yours goes up.
Optional AI answers. If the site owner has enabled an AI service, Chat with PDF and the Summarizer offer AI answers. Only text is sent, never the file, and only when you choose AI mode: in Chat with PDF, your question, the passages that match it (for a summary question, the text of the first pages) and your last few questions; in the Summarizer, the document's text, up to about 55,000 characters. The local mode sends nothing.
Optional audio. Transcribing a recording or downloading an MP3 of a PDF sends that audio or text to the speech service, when enabled. Live dictation relies on the speech recognition that comes with your browser, and some browsers send that audio to their maker's servers. Reading a PDF aloud uses the voices your browser offers; a voice your browser lists as online (PDF to Audio marks it “online”) sends each sentence to the online speech service behind it.
Counting visits. On this site, Plausible counts page views. It receives the page address (never anything after the # sign, where share codes live), the page you came from, how long you stayed and which outside links you clicked. When a tool finishes a job, or stops with an error, it also receives one word, Done or Failed, and the short name of the tool (for example, create-pdf). That is all it adds: never a file name, a size, a page count, any of your text or the error message. It sets no cookies, keeps no IP addresses and never sees your files. The meter lists these requests separately, as the visit count.
P2P Share and the whiteboard. A public connection broker (PeerJS) and Google's STUN server, which tells each browser its public address, help two browsers find each other. Your files and drawings then travel between the devices through an encrypted WebRTC channel, directly when the networks allow it, otherwise through a relay server that only passes the encrypted data on. Add a password and files are also encrypted end to end with AES-256 before they leave your device.
What is stored
Some tools remember things for you in this browser's local storage: saved signatures, your business details for invoices, a resume draft, saved workflows and your theme. They stay on this device and you can clear them with your browser's site-data settings.
There are no accounts, no cookies and no advertising trackers.
Check it yourself
The meter. The counter in the top bar wraps every way a web page can send data (fetch, XHR, beacons, WebSockets and WebRTC) and adds up the bytes. Its main number is what was sent of your files; the visit count is shown on its own line. Click it to see each request.
Developer tools. Open your browser's developer tools, choose the Network tab, and run a tool. You will see downloads of the app's own files, and no uploads.
Go offline. Open a tool, let it load, then turn off Wi-Fi. Most tools keep working, because they never needed the internet to do the work.