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

+28 -5
View File
@@ -83,13 +83,33 @@ Our server software keeps standard operational logs (dates, error messages, and
## 5. Search
Web search runs through our self-hosted search instance. For chat searches we use DuckDuckGo and Brave; those services receive your query from our server, and may see it. This is inherent to how web search works. Search queries and results are part of the conversation record, so they follow that conversation's retention: deleted when you delete a saved chat, or about an hour after a Temporary Chat is created. Operational details are in [Infrastructure](../operations/infrastructure.md#chat-retention-and-web-search).
Our self-hosted **SearXNG** instance at
[search.inference.coop](https://search.inference.coop) handles web search. For
chat searches it forwards queries to **DuckDuckGo** and **Brave**; those
services receive the query from our server and may see it. Search queries and
results are part of the conversation record, so they follow that conversation's
retention: deleted when you delete a saved chat, or about an hour after a
Temporary Chat is created. Operational details are in
[Infrastructure](../operations/infrastructure.md#chat-retention-and-web-search).
To read the pages behind the results, LibreChat sends the top result URLs to
**Keenable**, a third-party page-fetch service. We use Keenable's keyless public
endpoint, so its default data policy applies. Keenable logs and stores the
fetched URL, the page content, the returned results, and our server's IP address
and user agent. Keenable's policy sets no fixed retention period. Keenable
processes data in the United States and in the countries where its service
providers operate. Keenable may use content and usage data to improve and train
its products. Your chat messages and account identity stay with us.
Web search is optional. Leave the globe off for sensitive topics. If you need
search without a third-party page fetch, contact us about alternatives.
## 6. What we do NOT do
- We do **not** train models on your data.
- We do **not** sell, rent, or share your data.
- We do **not** use your data for advertising or profiling.
- We do **not** sell or rent your data.
- We do **not** share data for advertising or profiling. The service providers
in §5 and §7 process data to run the service.
## 7. Third parties
@@ -97,7 +117,9 @@ The models we serve are provided by third parties that change over time, each wi
- **Open Collective** — handles billing and membership (their own privacy policy applies).
- **Cloudron** — our self-hosted platform; no third-party cloud provider.
- **Search engines** — receive your search queries (see §5).
- **Search engines.** DuckDuckGo and Brave receive your search queries (see §5).
- **Keenable.** This page-fetch service receives result URLs and page content
(see §5).
## 8. Retention and deletion
@@ -110,7 +132,8 @@ The models we serve are provided by third parties that change over time, each wi
- Self-hosted on Cloudron (sandboxed apps, SSL, backups).
- Per-member API keys; access gated on live membership.
- No external dependencies for core infrastructure.
- Core infrastructure has no external dependencies. Web search uses the
third-party services described in §5.
## 10. Your rights