Chrome Extension

Privacy Policy — BookSync Manager

Controller: Marcin Frątczak Labs, ul. Warszawska 40/2A, 40-008 Katowice, Poland, NIP 6252163911

Contact: gdpr@booksync.link

Last updated: September 24, 2026

In short

BookSync Manager has no account, no server of its own and no analytics. Your bookmarks, tags, notes and AI suggestions are stored in your browser and are never sent to me. The network requests the extension makes are listed below. Only one of them can carry bookmark titles and addresses — the optional Jev engine, which is off until you add your own TypeSafe API key.

What is stored, and where

  • Your bookmarks — read and changed through Chrome’s own bookmarks API. They are Chrome’s bookmarks; if you have Chrome sync turned on, Google syncs them as it always does, independently of BookSync.
  • In chrome.storage.local, on your computer only: tags, descriptions, preferences, the trash, the cleanup log and review state, when you last opened a bookmark, AI category suggestions and the taxonomy they use, the search index for semantic search, and the results of link checks.

Removing the extension deletes everything in chrome.storage.local. Your bookmarks stay in Chrome.

AI features

By default everything runs on your device. Suggestions and folder names use Gemini Nano, the model built into Chrome (the Prompt API). It runs locally: bookmark titles and addresses go to the model inside your browser and nowhere else. Chrome downloads and updates the model itself, under Google’s terms for Chrome’s built-in AI; BookSync only asks Chrome whether it is available.

Semantic search uses the open-source model all-MiniLM-L6-v2. The first time you use it, the model files (about 25 MB) are downloaded from Hugging Face (huggingface.co) and then kept in your browser’s cache. That download is an ordinary file request — Hugging Face sees your IP address, as any website does — and it contains nothing about your bookmarks. The search index is computed and kept on your computer.

Jev by TypeSafe — optional, off by default. If you paste your own TypeSafe API key in Settings → AI and Chrome grants access to api.typesafe.ai, Jev takes over two decisions: which of your tags fit a bookmark, and which of your existing folders a loose bookmark belongs in. For the bookmarks it is asked about, it receives their title and address, plus your tag and folder names and a few example titles from each tag or folder. Requests go from your browser straight to TypeSafe under your key and your agreement with TypeSafe (typesafe.ai); TypeSafe handles that data under its own terms and privacy policy. The requests never pass through me, and I never see your key. The key is stored only in the extension on your computer. Switching Jev off or removing the key stops all of this immediately.

No bookmark data is used by BookSync to train any model.

Network requests the extension makes

  • Website icons — https://www.google.com/s2/favicons, with the domain of a bookmark (not the full address), so Google can return its icon. Google receives the domain and your IP address.
  • Link check — only when you run it, and only after you grant access to websites when asked. BookSync requests each bookmarked address (a HEAD request, with a GET fallback that stops after the status line) to see whether it still exists. Each site sees an ordinary request from your browser. Results stay on your computer.
  • Semantic search model — the one-time download from Hugging Face described above.
  • Jev — only with your own key switched on: requests to https://api.typesafe.ai as described above.

There is no other traffic: no analytics, no error reporting, no advertising, no remote code.

Permissions and why they are needed

  • bookmarks — to show, search, tag, move and clean up your bookmarks.
  • storage, unlimitedStorage — to keep tags, notes, suggestions and the search index locally; the index can outgrow the default quota.
  • Host access to https://www.google.com/s2/favicons* — to load website icons.
  • Optional access to http://*/* and https://*/* — requested only when you start a link check (for the checked sites) or save a Jev key (for api.typesafe.ai only), and used only for that. You can revoke it at any time in chrome://extensions.

BookSync Navigator

If you also use BookSync Navigator, the two extensions can talk to each other through Chrome’s externally_connectable messaging, only to share tags and descriptions. The exchange happens inside your browser; nothing leaves it.

What I do not do

I do not collect, receive, sell or share any of your data (with Jev on, data goes directly from your browser to TypeSafe under your own account, never to me), and I do not use it for advertising, credit decisions or anything unrelated to the extension’s single purpose — organising your bookmarks. The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Your rights

Because the data never reaches me, it is fully under your control: you can view, edit and delete it in the extension, export your bookmarks from Chrome, and remove everything by uninstalling. If you have a question about privacy, or want to exercise a right under the GDPR, write to gdpr@booksync.link. You can also lodge a complaint with the President of the Personal Data Protection Office (UODO), ul. Stawki 2, 00-193 Warsaw, Poland, or with the supervisory authority where you live.

Changes

If the extension starts handling data differently, this page is updated before that version is published, and the date above changes. The terms of use are at booksync.link/terms.