Tabmark – Multisearch (Chrome extension) · Last updated: July 2, 2026
Tabmark – Multisearch ("Tabmark", "the extension", "we") replaces Chrome's New Tab page with a multi-engine search dashboard and a set of browser widgets (Pinned Shortcuts, Recent History, Most Visited, Bookmarks Bar). This page explains exactly what data the extension reads, what it does with it, and what it never does.
The short version: Tabmark reads your browsing history, top sites, and bookmarks locally, inside your own browser, to build the widgets on your New Tab page. That data is never sent to us or to any server we control. The extension has no ads, no analytics, and does not sell or share your data with third parties. Signing in with Google is entirely optional and only used to back up your own settings to your own Google Drive.
Tabmark requests the following Chrome permissions. Each one is used only for the feature described — never for tracking, advertising, or analytics.
| Permission | What it's used for |
|---|---|
history |
Reads your browsing history from the last 7 days to populate the "Recent History" widget, and to power the history-based autocomplete suggestions when you type in a search box or add a Pinned Shortcut. Read locally on-demand; never uploaded anywhere. |
topSites |
Reads Chrome's own "Most Visited" list to populate the "Most Visited" widget. |
bookmarks |
Reads the folder you use as your bookmarks bar to populate the "Bookmarks Bar" widget. |
storage |
Saves your search engine list, layout preferences, theme, pinned shortcuts, and search counter, either in chrome.storage.sync (so they follow you to other devices signed into the same Chrome profile, via Chrome's own built-in sync) or chrome.storage.local (for larger data like a custom background image). |
identity |
Used only if you choose to click "Continue with Google" in the Profile panel. See section 3 below. |
None of the data read through these permissions is transmitted to Tabmark's developer, to any analytics service, or to any advertiser. It is read into the New Tab page and rendered directly in your browser.
A few features need to contact an outside service to work. Here is the complete list — nothing else leaves your browser.
| Service | What is sent, and why |
|---|---|
Google Favicons (google.com/s2/favicons) |
The domain name of a search engine, history entry, top site, or bookmark (e.g. github.com) is sent to fetch its small site icon for display. No page content, full URLs, or personal data are sent — only the bare domain. |
| Google Suggest & DuckDuckGo Suggest | If you type in the Google or DuckDuckGo search rows, the text you've typed so far is sent to that engine's official autocomplete endpoint to show live suggestions, the same way it would if you typed into that engine's own search box. |
| Wikipedia OpenSearch API | Same as above, for autocomplete suggestions when typing in the Wikipedia search row (if added from the engine catalog). |
Open-Meteo (open-meteo.com) |
If you grant the browser's location permission, your approximate coordinates are sent to this free, keyless weather API to show the current and next-day forecast. This only happens if you actively allow location access when prompted; the weather row stays hidden otherwise. Open-Meteo does not require any account or API key and, per its own policy, does not require registration or store personal data. |
Google Fonts (fonts.googleapis.com) |
Loads the "Inter" typeface used in the interface. This is a standard font-stylesheet request; no personal data is attached to it beyond what any browser normally sends when requesting a resource (e.g. IP address, as with any web request). |
| The search engine you use | When you search from any row, your query is sent to that engine (e.g. Google, YouTube, Amazon) exactly as if you had typed it directly into that engine's own site — the same way any search engine works. |
Signing in is never required — every feature of Tabmark works fully offline and signed out. If you choose to click "Continue with Google" from the Profile panel:
openid, email, and profile OAuth scopes, shown to you on Google's own consent screen before you approve anything.drive.appdata scope, which only grants access to a private, hidden application-data folder tied to this extension — not your regular Google Drive files. This folder is not visible in the normal Google Drive interface, and Tabmark cannot see or touch any other file in your Drive.chrome.storage, or to any server. Signing out revokes the token immediately.All local data (settings, pinned shortcuts, search counter, custom background) is stored using Chrome's own storage APIs and is removed automatically the moment you uninstall the extension. If you signed in with Google and created a Drive backup, you can delete it at any time by revoking Tabmark's access at myaccount.google.com/permissions, which also removes the associated app-data folder.
Tabmark is a general-audience browser utility and does not knowingly collect personal information from children. It has no account system of its own, and any information involved in the optional Google sign-in is handled entirely by Google under Google's own policies.
If this policy changes, the "Last updated" date at the top of this page will be revised. Material changes will also be reflected in the extension's Chrome Web Store listing.
Questions, concerns, or feedback about privacy or anything else in Tabmark can be sent to a@eyyubovs.com.