Docs first, as CLAUDE.md requires; the code follows in this branch. - 08: the manifest per target (two packages from one source, MV3 for both); Firefox's gecko id, data-collection declaration, floor 140 and source-code submission; Edge takes the Chrome package unchanged. - 02 §4, 03 §1/§3, 04, 05 §10: Firefox's GUID roots and fourth root, the Bookmarks Menu (`root: "menu"`, unmarked entries routed into it on Firefox); separators recognised by type, kept out of the file model and shown as untouchable lines in #edit; the move index sent by each browser's own rule and checked against the reply; addresses Firefox refuses dropped before planning; separators a file holds counted. - 06/07: the About link follows the install; three strings that blamed Chrome for what every browser does are reworded; new keys listed. - 11: a Firefox flavour of the fake, and a manual pass on real Firefox and Edge (including Edge signed in with sync) before the first submissions. - 12/13: three store jobs, each in its own environment with only its own secrets and a four-package install; CWS API v2 (v1.1 died 2026-10-15); AMO and Edge runbooks for the first, manual uploads. - 09/14 and legal/: three stores named; a clarification, not a LEGAL_VERSION bump. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5.0 KiB
Privacy Policy — BookmarkMagic
Terms version 1 · Effective 2026-07-26 · Last updated 2026-11-18
BookmarkMagic ("the Extension") is designed to work entirely on your device.
What we collect
Nothing. The Extension has no servers, performs no network requests, and contains no analytics, telemetry, or crash reporting.
What the Extension accesses, and why
- Bookmarks (permission:
bookmarks): read to display and export your bookmark tree; written when you import or edit. This data never leaves your device. - Local settings (permission:
storage): your language, theme, preferences, and the date you accepted these terms are stored locally viachrome.storage.local(Firefox calls the same storebrowser.storage.local). They are not transmitted anywhere and are removed by the browser when you uninstall the Extension. The Extension does not usestorage.sync, so even your settings stay off any vendor cloud.
The Extension requests no other permissions. It has no host permissions, no content scripts, and no background service worker. It contains no code that makes network requests, and its Content-Security-Policy additionally makes the browser refuse fetch, XHR, WebSocket, EventSource and beacon requests and remote images, fonts, media and frames from its pages.
- Diagnostics (no permission needed): while a BookmarkMagic tab is open, it keeps a short log of what it did — import steps, error codes, counts — in memory, so that you can copy it into a bug report from the About tab. It never contains titles, addresses or file names, is never written to storage, disappears when the tab closes, and leaves your computer only if you paste it somewhere yourself.
Files you import or export
Files are read and generated locally in your browser. They are never uploaded. Exported files are saved through your browser's normal download mechanism to a location you control.
Third parties
No data is shared with anyone, because no data is collected. The Extension installs no runtime dependencies; the few small MIT-licensed pieces its build compiles in (the Svelte runtime with its clsx helper, and WXT's browser shim — see THIRD_PARTY_NOTICES.md) contain no network code.
Two things happen outside the Extension and are worth knowing:
- The store you install it from — the Chrome Web Store (Google), Firefox Add-ons (Mozilla) or Microsoft Edge Add-ons (Microsoft) — distributes the Extension and its updates. Installing and updating it are governed by that store's own privacy policy, not this one, and each gives the developer only aggregate counts such as the number of users. On Firefox the Extension declares that it collects no data, in Firefox's own data-consent system.
- Opening a bookmark. When you open a bookmark from the Edit tab, your browser loads that page exactly as when you click any link: the request is the browser's, made on your instruction, to the site you chose. The Extension itself still sends nothing.
If you contact us
Everything above describes the Extension, which sends us nothing. This section describes what happens if you choose to send us something — reporting a bug, for example.
- Please do not send us your real bookmarks file. A bookmarks export is a
browsing history. Run
scripts/sanitize-bookmarks.mjsfrom the repository first: it replaces every address and title while keeping the file structure that a bug depends on, so the sanitized version still reproduces the problem. - Anything you attach to a GitHub issue is public and stays in the issue history. Attach only a sanitized sample. If you agree, a sample may be committed to the repository as a permanent test fixture under GPL-3.0 — the bug report form asks you explicitly, and never assumes it.
- Anything you email us is kept only as long as it takes to reproduce and fix the issue, and is then deleted. It is not shared with anyone, and it is never added to the repository unless you agreed to that.
Changes
Material changes will be published here and re-acceptance will be requested inside the Extension.
The section above was added on 2026-08-03. It is a clarification, not a change of practice: it describes handling of material you choose to send us, which was never part of what the Extension itself collects — which remains nothing. No re-acceptance was requested.
Clarified on 2026-11-18: the Extension is also distributed through Firefox
Add-ons and Microsoft Edge Add-ons. That adds no data flow — the Extension
still collects nothing — so no re-acceptance is requested (docs/14 §3.1).
Clarified on 2026-10-29: the diagnostics log, the Chrome Web Store, opening a
bookmark, and what the build compiles in are now described, and the contact
address changed. None of it changes what the Extension collects — still
nothing — so no re-acceptance is requested (docs/14 §3.1).
Contact
Privacy questions, and requests to remove a sample you sent: privacy@poli0981.dev — or open an issue at https://github.com/poli0981/bookmarkmagic/issues