Last updated: October 1, 2026
SearchJumper processes page content in your browser to show search tools, match engines, and highlight words. It also makes network requests for the features and resources described below. “Stored locally” does not mean that every feature works without network access.
Extension storage or the userscript manager stores your engines, preferences, saved highlighting rules, recent engine choices, and optional WebDAV connection details. Saved rules can contain page URLs and words. Icon caches and some recent search or highlighting state are also stored locally. Temporary image actions in the extension use session storage. SearchJumper does not add its own encryption to these stores.
Saved WebDAV passwords are used by the extension background or userscript environment. Configuration pages receive the server, username, directory, and whether a password is saved; they do not receive the saved password. Newly entered passwords pass from the form to that environment. Full configuration backups exclude the WebDAV password. Old backups containing a password remain importable.
| Feature and timing | Recipient and data |
|---|---|
| Searches, image searches, and custom engines or APIs, when triggered | The configured destination receives the query and any configured parameters, such as a selected link, page URL or title, image, request body, or headers. Login cookies and authentication needed by those features may be used. |
| Search suggestions, when enabled, after an input pause of about 200 ms | The selected provider (Google, Bing, or Baidu) receives text before you submit a search. Public suggestion requests omit cookies and unnecessary referrer information. New installations default to disabled; upgrades preserve existing choices, including the previous language default when an old configuration lacks this setting. Disabling suggestions stops new suggestion requests. |
| Engine icons and font icons, when displayed or cached | Icon hosts, configured icon services, or the font CDN receive resource requests. Turning off icon caching stops persistent caching, not all downloads. Icon requests no longer explicitly attach the full URL of the page you are visiting. |
| Background images and daily Bing backgrounds, when configured | The image host or Bing receives the request. Custom CSS can also load resources from addresses you specify. |
| WebDAV synchronization, after you configure an account and when loading or changing synchronized data | Your chosen server receives authentication, engine configurations, saved highlighting rules, and a modification timestamp. Connection checks may create directories. Other preferences are not part of this synchronization. A failed download does not authorize overwriting the remote data. |
| Optional account and sharing services, when you request an account or use their controls | search.hoothin.com and webdav.hoothin.com process the account and sharing operations, including usernames, entered service fields, shared engines, share titles, and share passwords. The account service supplies a WebDAV account; it is not contacted to register an account automatically. |
| Configuration and welcome pages, when opened | Hosted pages contact their hosting service. The welcome page opens on first use and can load third-party resources, including advertising, under those sites' own policies. The configuration page downloads a sponsor image from search.hoothin.com and displays it as an image. Its links open only when selected. The extension bundles the configuration application's JavaScript and dependencies. |
| Userscript dependencies and updates, when installed or updated by your userscript manager | Greasy Fork supplies the default configuration dependency. Its reviewed revision is pinned. Update checks follow your manager's settings. The extension uses its bundled default configuration. |
Network recipients can observe ordinary connection information, including IP address and request time. Their storage and retention practices are governed by their own policies. Engine configurations and exported backups can still contain API keys, custom headers, URLs, or other values you entered; excluding the WebDAV password does not remove those values.
The extension's local configuration page uses native extension messages. Hosted userscript or custom configuration pages use a restricted bridge. Management requests are limited to exact built-in or explicitly configured page addresses; ordinary websites are not given a full configuration message when an engine is added.
Access to websites and cross-origin requests supports selection tools, icons, image searches, custom APIs, and arbitrary user-selected WebDAV servers. Storage, menus, and notifications support the corresponding local features. These permissions are retained so that existing custom engines and servers continue working.
Split search adjusts frame and request headers for its workspace tabs. Cookie access supports compatible sign-in, including X. For supported split sites, the extension may remove service worker registrations for those origins; those registrations are shared with ordinary tabs. This operation does not clear cookies or caches. Split behavior is not a general removal of site protections in all tabs.
You can disable suggestions, change resource URLs, stop using remote backgrounds, or disconnect WebDAV in settings. Disconnecting WebDAV removes the local connection details; it does not delete files already stored on the server. Manage remote files and accounts with the relevant provider. Removing local settings or uninstalling the extension or userscript is separate from deleting downloaded backups.
Questions about privacy or this implementation can be sent to rixixi@gmail.com or raised in the project discussions.