Extension privacy policy

The short version

There are no analytics, no telemetry, no accounts, and no servers of ours involved at any point. This page covers the browser extension; the website has its own policy saying much the same thing about the tools themselves.

The extension itself is on the Chrome Web Store.

What the extension actually does

When you right-click an image or a PDF link and choose a Toolbench tool, the extension reads that one file inside your own browser and hands it to the tool page at toolbench.tools, where it is processed entirely on your device. The tools are client-side by design: no file is ever uploaded anywhere.

The only network request the extension ever makes is the request for the file you right-clicked — made by your browser, from your session, to the same address the page already loaded it from. Nothing is added to that request, and the file travels from that site to your browser and no further.

Data handling, point by point

• Images and files — held in memory only for the seconds the hand-off takes, then discarded. Never written to disk by the extension, never sent to any server.
• Browsing activity — not observed. The extension has no access to the pages you visit; its content script runs only on toolbench.tools.
• Site permissions — some sites do not allow their files to be read without permission. In that case Chrome asks you to allow that one site; the grant is stored by Chrome itself, is visible in the extension’s popup, and can be removed there at any time. The extension keeps no record of its own.
• Cookies and credentials — never read, never stored. When a granted site requires your session to serve a file, your browser attaches your own cookies to that one request, exactly as it does when the page loads the file — the extension never sees them.
• Downloads — choosing “Download image as…” converts the image on your own device, using the browser’s canvas, and saves it through Chrome’s normal download shelf. The file goes from its site to your disk — through no server of ours, ever.
• Personal information — none is collected, so none is retained, shared, or sold.

Third parties

There are none. No analytics providers, no advertising networks, no error reporters, no CDNs of ours.

Changes

If a future version ever changes any of the above, this policy will be updated before that version ships, with the date above revised.

Contact

Questions: via the contact page.