Last updated: 15 August 2026 · applies to Advanced Bookmarks v1.2.0 and later
Advanced Bookmarks collects no data. It contains no analytics, no telemetry, no error reporting and no network code of any kind. Nothing you do in the extension is recorded, stored off-device or transmitted anywhere.
| Permission | What it is used for |
|---|---|
bookmarks |
Read your bookmark folder tree so it can be searched, and create, update, move or delete bookmarks when you ask it to. All of this happens through Chrome's own bookmarks API, entirely on your device. |
activeTab |
Read the title and URL of the tab that is active when you open the dialog, in order to pre-fill the Name and URL fields. This value is used to populate the form and nothing else. Chrome grants this access only for the tab you are on, and only because you opened the dialog; the extension cannot see any other tab, and cannot see anything at all when the dialog is closed. |
The extension requests no host permissions, so it cannot read or modify the content of any web page.
None. The extension makes no HTTP requests, opens no sockets, loads no remote scripts, fonts or images, and bundles no third-party libraries. It has no background service worker. Everything runs in the popup, using only browser APIs.
The extension does not use chrome.storage or any other persistence
layer. The only thing it writes is the bookmarks you explicitly save, which live in
your browser's own bookmark store exactly as they would if you had used Chrome's
built-in dialog.
There are none. No data is sold, shared, or transferred to anyone, for any purpose.
The extension is open source under the MIT license and is a few hundred lines of dependency-free vanilla JavaScript. You can read every line of it at github.com/bcollard/chrome-advanced-bookmarks.
You also do not have to take on faith that the source you are reading is the code you installed. Every release is built by GitHub Actions from a tag and carries a signed build provenance attestation, and the build is reproducible, so the published artifact can be checked against the source byte for byte:
gh attestation verify advanced-bookmarks-1.2.0.zip \
--repo bcollard/chrome-advanced-bookmarks
python3 scripts/verify-reproducible.py advanced-bookmarks-1.2.0.zip
Full instructions are on the
landing page. This matters because the Chrome Web Store
signs the .crx itself from a .zip the developer uploads:
without reproducibility and attestation, nothing links the bytes you install to a
commit.
If a future version ever needs to handle data differently, this page will be updated before that version ships, and the change will be called out in the release notes on GitHub.
Questions or concerns: open an issue on GitHub.