Your files
PDFy reads the folder you pick using the browser's File System Access API. The contents stay on your machine the entire time. Nothing is uploaded. The PDF is generated by your browser's print dialog, so even the final document never touches a server we run.
What's stored locally
So you can come back to a project without picking the folder again, PDFy keeps a few things in your browser:
- Recent project handles in IndexedDB. These are permission tokens, not file contents. The browser still asks before reading anything.
- Per-project state in IndexedDB: which files are in your print plan, custom titles, header / footer templates, table of contents settings.
- App preferences in localStorage: theme, font size, page size, etc.
All of this lives only in the browser you're using right now. Clearing site data wipes it all.
What goes over the network
Three things, all aggregate or static, none personal:
- Analytics. A self-hosted Plausible instance counts page views and a few interaction events
(e.g. "opened the tool"). No cookies, no cross-site tracking, no fingerprinting. IP
addresses are used to compute the visitor's country and then discarded. Plausible is
open-source and the instance runs at
plausible.axonotes.ch. - GitHub star count. The home page asks GitHub once for the PDFy repo's star count. No information about you is sent.
- The site itself. HTML, CSS, fonts and images are served from Vercel's CDN. Vercel may keep standard request logs (IP, user-agent, timestamp) for the usual operational reasons.
No accounts, no email
PDFy doesn't have a sign-up form, doesn't ask for an email, and has no notion of a user account. There is nothing to delete because there is nothing stored about you on any server.
If something changes
This page tracks what the app actually does. If the behaviour changes, this page changes with it. The date at the top of the page is the source of truth, and the full edit history lives in the GitHub repo.
Questions
Open an issue on GitHub, or reach the author at oseifert.ch.