Privacy Policy
Applies to SiteDrawer 2.0 for Firefox and Chrome. Last updated 24 October 2026.
SiteDrawer collects nothing. There are no accounts, no SiteDrawer servers, no analytics and no telemetry. Nothing about you, your Spaces or your browsing is ever sent to us, because there is nowhere for it to be sent.
The rest of this page is the detail behind that sentence: every permission the extension asks for, why it asks, and the handful of cases where your browser fetches something from a third party so that a tile can have an icon.
What is stored, and where
Your Spaces, the sites in them, their names, colours, any icons you upload, and your settings are held in your browser's own extension storage on your own machine.
If you have browser sync switched on, that data syncs through your browser account, the same way your bookmarks do. It travels between your own devices via Mozilla or Google, under whichever privacy policy already covers your browser account. It does not pass through us, and we could not read it if we wanted to.
Some Launchpad settings, such as which buttons are in the toolbar and how large your tiles are, are deliberately stored on the machine you set them on rather than synced, because they describe that particular window rather than your collection.
Export writes a complete backup to a file you choose. Import reads one back. Both are entirely local.
Permissions
Browsers show permissions as a terse list at install time. Here is what each one is actually for.
Requested at install
| Permission | What SiteDrawer does with it | Browser |
|---|---|---|
storage | Saves your Spaces and settings, and syncs them through your own browser account when sync is on. | Both |
unlimitedStorage | Lifts the small default storage quota so a large collection, and any icons you upload, still fit. | Both |
tabs | Reads the current tab's address and title when you click Add, opens your saved sites, and shows a marker on tiles whose site is already open. Tab addresses are read at the moment you act and are never recorded. | Both |
contextMenus | Adds the right-click "Add link to SiteDrawer" entries. | Both |
tabGroups | Places tabs into a tab group when you choose "Open all in Group". | Both |
search | Powers the optional search box on the Launchpad. On Firefox it lists the search engines already installed in your profile so the picker can name them, and runs your query through the engine you chose. Nothing is queried unless you type something and press enter. | Both |
contextualIdentities, cookies | Opens your saved sites in a Firefox Container that you pick. Used only to read the list of containers you already have and to open tabs in one. No cookie is ever read or written. | Firefox |
sidePanel | Lets SiteDrawer open in Chrome's side panel. | Chrome |
Asked for only if you use the feature
| Permission | What SiteDrawer does with it |
|---|---|
bookmarks | Reads your bookmark tree when you run Import Bookmarks, so it can offer to turn folders into Spaces. It is read-only: SiteDrawer never creates, edits or deletes a bookmark. If you decline, the rest of the extension is unaffected. |
Access to svgrepo.com, brandlogos.net and logodix.com | Only for the optional logo search described below. Requested at the moment you ask for it, and only then. |
When your browser talks to someone else
SiteDrawer never sends anything to a server of ours. It does not have one. But a few features ask your browser to fetch a picture from somewhere, and you should know which and when.
Tile icons
By default SiteDrawer asks each saved site for its own /favicon.ico, directly. That request goes to the site itself, exactly as if you had visited it.
When a site has no usable icon, SiteDrawer falls back to an icon service, icons.duckduckgo.com, which is sent the site's domain name and nothing else. This is the setting called Allow looking up missing icons from public icon services. On Firefox, this lookup is off until you allow it: turning on Site Icons in Settings makes Firefox ask for your permission, and you can withdraw it in Settings or in Firefox's Add-ons Manager. On Chrome it is on by default and can be turned off in Settings. With the lookup off, SiteDrawer is fully local: sites with no icon simply get a coloured letter tile instead.
Logo search
When you deliberately search for a logo while editing a tile, SiteDrawer sends the words you typed to a set of public logo and icon sources so it can show you results. Those sources are the BrandBird public asset bucket on storage.googleapis.com, Simple Icons via cdn.jsdelivr.net, the icon services at icons.duckduckgo.com, www.google.com/s2/favicons and unavatar.io, and, if you grant the optional permission, the search pages of svgrepo.com, brandlogos.net and logodix.com. This happens only when you press the search button, and only with the text you typed.
The Launchpad search box
If you switch on the Launchpad's search box, your query goes to the search engine you selected, and to nobody else. On Firefox it is handed to the engine through the browser's own search API, so your existing settings for that engine are respected. SiteDrawer does not see, log or keep your queries.
Add from Popular Sites
The starter catalog ships inside the extension as a local file. Choosing a region does not contact anyone: the region is guessed from your browser's own language setting and time zone, never from your IP address, and you can override it at any time. Once you build Spaces from it, the resulting tiles fetch their icons the same way any other tile does.
IconCat
SiteDrawer answers messages from one other extension, IconCat, and from nothing else. A message from any other sender is ignored without a reply. IconCat can ask two things: whether SiteDrawer is there, and for the graphics SiteDrawer draws, meaning its own logo, the icons on its pages, and the icon of each tile you have saved. The exchange happens inside your browser and goes nowhere else. Turning a tile's icon into a picture IconCat can show sometimes means fetching that icon, which is the same request described under Tile icons above and goes to the same places.
What SiteDrawer never does
- No account, no sign-in, no email address required.
- No analytics, no telemetry, no crash reporting, no usage statistics.
- No advertising, and no data sold, shared or brokered. There is no data to sell.
- No reading of your browsing history.
- No content scripts. SiteDrawer does not run code on the pages you visit.
- No remote code. Everything it runs ships inside the extension package and is reviewed by the store before you get it.
Children
SiteDrawer is a general-purpose tool that collects no personal data from anyone, of any age.
Changes to this policy
If a future version of SiteDrawer changes what it accesses, this page is updated before that version ships, and the date at the top changes with it.
Contact
Questions, or something here that does not match what you observe: admin@sndcats.com. SiteDrawer is MIT licensed and the complete, unminified source is what is published to both stores, so every claim on this page can be checked against the code.