OxygenPDF door Rohman Mahir

The extension fetches the PDF you are looking at using your own browser session, hands it to a new OxygenPDF tab, and stops. The file never reaches a server, ours or anyone else's.

What it reads. The address of the tab you used it on, and the PDF at that address — including a PDF on your own machine, if you turn on your browser's file-access switch. Nothing else on the page, and nothing until you ask.

Where the file goes. Into your browser's own storage for the seconds it takes to reach the OxygenPDF tab, then it is deleted. Anything a handover leaves behind is cleared within ten minutes.

What we collect. Nothing. No analytics, no counters, no account, no error reporting. The extension makes no request to us at any point.

What it remembers. The tools you pin in the popup, stored on this machine. Not synced, not sent anywhere, and gone if you remove the extension.

What it never does. It does not run on pages you have not used it on, and it never reads what you are browsing.

Permissions, and why each one is asked for:

• activeTab — Read the address of the tab you used it on, so it knows which PDF you mean.
• contextMenus — Add one item to the tab's right-click menu.
• scripting — Look for a PDF on the page you used it on, and show the result there.
• storage — Hold the PDF for the few seconds it takes to reach the OxygenPDF tab.
• alarms — Delete anything left behind if a handover never completes.

A PDF that only exists for your signed-in session has to be read from that site. The extension asks the first time it needs to, and names the site it is asking about. Turning it down leaves everything as it was.

Opening a PDF that is already on your machine needs your browser's own file-access switch, which is off by default and can only be turned on by you. The extension points you at it and reads nothing on disk until you do.