privacy/infra: document brief temporary-chat retention and DuckDuckGo + Brave search
This commit is contained in:
1 parent
1ec63c443b
commit
606bfc5660
2 files changed
+31
-4
No files matched your search
@@ -172,6 +172,33 @@ The co-op serves models from multiple providers — Tinfoil for architectural
|
||||
privacy, GreenPT and Regolo for renewable energy. See the [model list](../guides/models.md),
|
||||
the single source of truth for which models are available and how they're named.
|
||||
|
||||
## Chat retention and web search
|
||||
|
||||
**Saved chats** live in the chat database and its search index until the member
|
||||
deletes them. Web-search tool calls are part of that record: the query and the
|
||||
results returned are stored with the message.
|
||||
|
||||
**Temporary chats** are server-backed — messages must reach the server while the
|
||||
chat is running — so they are not client-only. The chat is configured to delete
|
||||
them from the database about **one hour after creation** (`interface.temporaryChatRetention: 1`
|
||||
in the chat configuration; one hour is the minimum this LibreChat version
|
||||
accepts). They are hidden from history immediately, and the database enforces the
|
||||
expiry automatically. Temporary chats created before this setting took effect
|
||||
keep their original 30-day expiry until they age out.
|
||||
|
||||
**Backups are a separate layer.** Cloudron backups are whole-app snapshots and
|
||||
cannot exclude individual chats, so a temporary chat present when a backup runs
|
||||
can remain recoverable from that backup until the backup itself expires (see
|
||||
[Backups](#backups)).
|
||||
|
||||
**Web search** in the chat uses **DuckDuckGo and Brave** through the co-op's
|
||||
self-hosted SearXNG instance. Queries are sent from the co-op server, so the
|
||||
upstream engines see the query but not the member's IP or identity. The SearXNG
|
||||
instance is also publicly reachable at search.inference.coop, and its logs can
|
||||
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.
|
||||
|
||||
## Security posture (plain language)
|
||||
|
||||
- **Member isolation.** Each API key is scoped to its owner's team and budget; a
|
||||
|
||||
Reference in new issue
Block a user