Privacy
Excel to PDF privacy without file uploads
Excel to PDF privacy starts with where the spreadsheet is processed. Create PDF from Sheet has no file-upload endpoint: JavaScript reads the file from disk, converts it in browser memory and writes the PDF locally. The application does not receive the spreadsheet contents.
How to verify this yourself
Don't take our word for it — this is one of the rare privacy claims you can check in under a minute.
- 1Open your browser's developer tools and switch to the Network tab.
- 2Convert a spreadsheet as you normally would.
- 3Watch the request list. There is no POST or PUT carrying your file — only the page's own code, fonts and styles, all fetched before you added anything.
- 4For an even blunter test: load this page, disconnect from the internet, then convert. It still works.
What we do collect
The application does not include an analytics service, advertising tracker or file-upload endpoint. The hosting provider may retain ordinary request logs for page and asset delivery, but spreadsheet names, contents and sheet data never enter those requests.
There are no accounts, so there is no email address, password or profile. Nothing about your conversions is persisted between sessions — close the tab and the data is gone from memory.
Cookies
No advertising or tracking cookies are set. Your converter settings stay in the page's memory for the length of your visit only.
Regulated and confidential data
Spreadsheet processing happens entirely on your device, so the application does not receive the file contents. Your organisation may still regulate which websites and software you can use. Ask your privacy, security or compliance team to approve the workflow for regulated or confidential data.
Changes
If local-only processing ever changes, it will be stated plainly at the top of this page and on the converter itself before you upload anything — not buried in a revision note.