seekey Privacy Policy

Last updated: July 5, 2026

seekey handles user data only to provide its keyboard-first local search and navigation features.

Data handled

seekey may process:

• Bookmarks, including bookmark titles and URLs.
• Open tabs, including tab titles, URLs, and last accessed times.
• Optional browsing history, including page titles, URLs, visit counts, and last visit times.
• Past Google search terms parsed from the user's browsing history when history permission is enabled.
• Extension settings, including the search leader key, display language, history settings, and direct shortcut bindings.

How data is used

seekey uses this data to build and rank local search results, show direct shortcut results, and open the selected page or switch to the selected open tab. All search, fuzzy matching, and frecency ranking runs locally in the browser.

Storage

Settings and direct shortcut bindings may be stored in chrome.storage.sync so they can follow the signed-in Chrome profile. Bookmark and history data is read from browser extension APIs when needed and may be cached in extension memory for performance. Open tab data is read the same way each time the palette opens and is not stored. Device-local UI state, such as the last selected search view, is stored in chrome.storage.local and is not synced.

Data sharing

seekey does not send bookmarks, open tab information, history, search terms, settings, shortcut bindings, telemetry, or analytics data to a developer server. seekey does not sell user data, use it for advertising, or share it with third parties.

History permission

History permission is off by default and is requested only when the user enables it in the options page. If history permission is not granted, seekey searches bookmarks and direct shortcuts only.

Users can disable history search from the options page, remove the history permission from the browser's extension settings, edit or delete direct shortcuts, or uninstall the extension to remove its local extension data.