Unit09 · Lumipdf

Lumipdf Privacy Policy

Last updated: July 26, 2026

Lumipdf is a PDF toolkit that runs inside your browser. This policy explains what it stores, what it never does, and why it asks for each permission.

The short version

Your documents never leave your computer. Lumipdf has no server. There is no account to create, nothing to sign in to, and no analytics, advertising or crash-reporting code anywhere in it. Every tool (merging, splitting, signing, compressing, converting, capturing) runs in the browser tab, on your machine. You can disconnect from the internet and the extension still works, which is the simplest way to check this claim for yourself.

What Lumipdf stores, and where

All of it lives in your browser's own storage on this computer, in the extension's private area. None of it is synced to any account and none of it is transmitted.

• Your documents: the PDFs you import or create, held so the library can show them again.
• Text read out of your PDFs: so that searching finds words inside a document and not only in its file name. The text is extracted in the tab, by the PDF engine bundled with the extension, and stored beside the document.
• Your arrangement: names, folders ("binders"), sections, favourites and tags.
• Permission to write to your files: when you open a PDF from your own folders, the browser gives Lumipdf a handle to that file so it can save your edits back to it rather than leaving copies in Downloads. The handle is stored; the folder around it is not readable through it.
• The capture tray: anything you have collected while browsing and not yet turned into a PDF.
• Undo history: so a document you were editing can be stepped back through the next time you open it.
• Your settings and signature: theme, page size, and the signature or initials you drew, if you drew one.

Deleting a document and emptying the Trash removes it. Removing the extension, or clearing your browser's data for it, removes everything above permanently. There is no copy anywhere else, including with us.

What Lumipdf sends

Nothing. No document, no page, no file name, no extracted text, no usage statistic, no error report and no identifier is transmitted to Unit09 or to any third party. There is no endpoint to send it to.

Lumipdf does make network requests, and it is worth being precise about which: it fetches a file you have pointed it at. If you ask it to open the PDF you are currently reading, right-click an image and send it to Lumipdf, or open a PDF by link, the extension downloads that file from the site it is already on, the way your browser would. That request goes to that site, carries no data of yours beyond the ordinary request for the file, and happens only when you ask for it. Nothing travels in the other direction.

Permissions, and why each one is asked for

Lumipdf requests as little as it can and asks late. It is granted no access to any website when you install it.

Granted on install

• Storage / unlimited storage: to keep the library described above on this device. A document library does not fit in the default quota.
• Active tab and scripting: to read the page you are on at the moment you capture it, for that one action. Not used at any other time.
• Context menus: to add the "Send to Lumipdf" entries to your right-click menu.
• Side panel: so Lumipdf can run docked beside the page you are reading.
• Offscreen: rendering and assembling a PDF needs a page to draw on; this gives the extension one of its own, invisibly, on your machine.

Asked for only when you use the feature, and never before

• Access to a website: requested at the moment you capture a page, for the site you are on.
• Tabs: requested by the side panel, to show the title and address of the tab it is docked beside. It does not read that page's contents.
• Downloads: requested only if you choose to save a result to your Downloads folder.
• Debugger: used by one feature, "Save page as PDF", which drives Chrome's own print-to-PDF pipeline to produce a real PDF with selectable text instead of a picture of the page. Chrome shows a banner while it is attached. It is requested only if you use that feature, used only for that page, and detached afterwards.
• Camera: requested only if you use a webcam capture, to photograph a page. The video is processed in the tab and never recorded or sent.

You can review or revoke the optional permissions at any time on Lumipdf's details page in chrome://extensions.

What leaves your computer when you choose to send it

Saving, downloading or sharing a PDF hands the file to whatever you chose: your own disk, or another application. From that point the file is governed by wherever you sent it, not by Lumipdf.

Tools that are not built yet

Lumipdf's tool screen lists a few features marked "In development", including three that would use an AI model. None of them are built, none of them run, and clicking one does nothing but explain itself. If any of them ships, it would work by sending text to an AI provider you choose, using an API key you supply, and only when you ask it to. This policy will be updated to say exactly what is sent before that version is published. Today, no such code exists in the extension.

Children

Lumipdf collects no personal information from anyone, including children.

Changes to this policy

If a future version changes how data is handled, this policy will be updated and the "Last updated" date revised before that version is published to the Chrome Web Store.

Contact

Questions about privacy: rnd@unit09.app