Last updated: 2026-09-02
Privacy Policy — Bookmark Workbench
The extension collects nothing and sends nothing anywhere. All processing happens locally in your browser. There is no server, no account, no analytics, and no third-party code.
Bookmark Workbench is a Chrome extension published by Melchor Bungalso / HUGsoft (hug-soft.com). This policy explains what the extension does with your data.
What the extension accesses
For each kind of data: why it is touched, and where it ends up.
-
Your Chrome bookmarks (read and write)
- Why
- To list, search, edit, move, de-duplicate and delete them — the core purpose of the extension.
- Where it goes
- Stays in Chrome. Never transmitted.
-
Tags and notes you add
- Why
- A per-bookmark layer Chrome can't store itself.
- Where it goes
- Saved with
chrome.storage.localon your device only.
-
UI preferences (e.g. which folders are collapsed)
- Why
- To restore your view between sessions.
- Where it goes
- Saved with
chrome.storage.localon your device only.
-
Site icons
- Why
- Shown next to each bookmark.
- Where it goes
- Served by Chrome's built-in favicon cache; no external request is made by the extension.
-
Open browser tabs (the
tabspermission)- Why
- So clicking the toolbar button focuses an already-open workbench tab instead of opening a duplicate — Chrome only tells the extension which tab that is if it holds this permission.
- Where it goes
- Nowhere. The extension only ever matches its own page's URL. It does not read, collect, or store the URLs, titles, or contents of your other tabs.
Optional: the dead-link checker
The "Check links" feature sends a network request to each bookmarked URL to see whether it still resolves. This requires permission to read other sites, which the extension asks for only when you click "Check links" and not before. If you never use that feature, the permission is never requested.
When you do use it:
- Requests go directly from your browser to the bookmarked sites, exactly as if you had opened them.
- The extension records only the resulting status (e.g. "ok", "broken") locally.
- No URL, result, or any other data is sent to the developer or any third party.
You can revoke this permission at any time from Chrome's extension details page.
Backup, export and import
The backup and export features write a .json or .html file to your device. The import feature reads a file you select. All of this happens locally — no bookmark, tag, note or file is uploaded anywhere.
Data sharing and sale
None. No data is shared, sold, or transferred to anyone, and the extension loads no third-party code or embedded services.
The only outbound link in the interface is a normal "Buy Me a Coffee" link in the footer. Following it opens that third-party site, which has its own privacy policy — exactly like clicking any other external link. The extension itself sends nothing there.
Changes
Any change to this policy is reflected in the "Last updated" date at the top of this page, and the previous wording is superseded from that date. If you want to know what changed, ask us — we will tell you.
Contact
Questions about this policy: mbungalso@gmail.com, or use the Bookmark Workbench support form.