docs(search): describe the search and fetch pipeline

Explain the two stages: SearXNG queries DuckDuckGo and Brave, then Keenable fetches the top result pages. Name the SearXNG instance URL and disclose Keenable's logging, retention, processing location, and training use. Correct the claim that web search has no external dependency.
This commit is contained in:
ed committed 2026-11-19 14:29:13 -05:00
1 parent 0896699581
commit b0edbf2c33
3 files changed
+55 -8

No files matched your search

+7 -1
View File
@@ -73,8 +73,10 @@ The co-op's software behind all of these is open source — see [The
code](#the-code) below for where each piece lives.
Open Collective (billing and fiscal sponsorship) is the one external service in
the flow — see
the membership flow. See
[opencollective.com/inference-cooperative](https://opencollective.com/inference-cooperative).
Web search uses external services too; see
[Chat retention and web search](#chat-retention-and-web-search).
## Mail
@@ -199,6 +201,10 @@ contain query text when an upstream engine request fails; those log lines carry
no member identity or IP, and are retained only briefly. The reverse proxy does
not log search queries.
LibreChat reads the pages behind the results through **Keenable**, a third-party
page-fetch service. Keenable's logging and retention are described in the
[privacy policy](../governance/privacy-policy.md#5-search).
## Security posture (plain language)
- **Member isolation.** Each API key is scoped to its owner's team and budget; a