Privacy
AdminSearch is designed to minimize data collection while providing search through a private SearXNG backend.
Search requests
Search and autocomplete terms are sent to the AdminSearch server and then to its private SearXNG service. SearXNG contacts the selected external search providers and returns their results. AdminSearch does not require an account and does not include client-side analytics or advertising trackers.
Browser storage
Preferences are stored in a first-party cookie for up to one year, or for the current session if persistent storage is disabled. Language and storage choices use local or session storage. If result reuse is enabled, recent search results can be kept in session storage for up to 30 minutes. The cookie is sent only to AdminSearch; local and session storage stay on your device. All of this data can be removed through your browser's site data controls.
Rate limiting
The server may use your IP address as part of a temporary Redis/Valkey rate-limit key. The key expires after the configured rate-limit window, which is one minute by default. AdminSearch does not maintain a separate account database or server-side search history.
External content
Favicons are fetched by the AdminSearch server from Google or DuckDuckGo. Result thumbnails are loaded from their source, and optional video previews can connect your browser to providers such as YouTube, Vimeo, Dailymotion, or Odysee. Favicons and thumbnails can be disabled in settings.
Hosting
The maintained deployment is hosted on Railway in Amsterdam. Railway processes the network and technical request data needed to operate the service, and infrastructure logs may include request metadata. Self-hosted AdminSearch instances may use different providers, logging, and retention settings.
Source and questions
AdminSearch is open source. You can review the code or contact the maintainer through the GitHub repository.
Last updated: June 30, 2026